I've gotten Fallout3 to load to the main menu, by following the Tips & Tricks posted, and I have a couple more tricks.
"No Sound Device Detected" from FalloutLauncher.exe:
This error seems only to happen while the intro audio track is playing. If you wait for the sound track to stop playing, clicking "Play" succeeds without the "No Sound Device Detected" error. If you rename/remove the intro audio track file (sorry I don't remember the exact filename at the moment) in the Fallout 3 directory, this error doesn't happen at all.
"No Disk Inserted"
***snip
The Digital Rights Management (DRM) software in this program
prevents it from running in CrossOver. If you are in a legal jurisdiction
which allows removal of such software, you may have luck running this
program. Unfortunately, CodeWeavers, because they are subject to the
Digital Millennium Copyright Act, will be unable to support you.
***snip
I found I had to run the GLSL regedit change a couple times before it stuck. But with that in place, and the xinput1_3.dll, and the above changes, Fallout loads to the main menu from the FalloutLauncher.exe for me.
From here on though, what's the point? I haven't heard anyone successfully get a new game to actually start. It's pretty cool to see the menu screen and all, but I think more of a tease than anything. I have played this a bit on a windows box, so I tried copying some savegames to my bottle and loading those instead of starting a new game. But no dice. Also tried removing the video/music files in case one of those were the issue. No change.
I can try to grab some backtraces of the crashing process, but is there anyone here (besides the CodeWeavers folks) who can make anything of that data?
Anyone got further than the Main Menu screen?
Cosmo
Caron Wills