http://bugs.winehq.org/show_bug.cgi?id=28035
Summary: Fallout 3 crashes when hitting play on launcher. Product: Wine Version: 1.3.26 Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: mister_a@aol.com
Created an attachment (id=35896) --> (http://bugs.winehq.org/attachment.cgi?id=35896) Backtrace of application
After clicking the play option on the launcher for Fallout 3, the game will give a not responding error and crash.
http://bugs.winehq.org/show_bug.cgi?id=28035
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|All |x86 Severity|major |normal
http://bugs.winehq.org/show_bug.cgi?id=28035
Erich Hoover ehoover@mines.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoover@mines.edu
--- Comment #1 from Erich Hoover ehoover@mines.edu 2011-09-15 10:47:03 CDT --- Does it work if you launch the game directly (skipping the launcher)?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #2 from mister_a@aol.com 2011-09-15 19:45:38 CDT --- (In reply to comment #1)
Does it work if you launch the game directly (skipping the launcher)?
Nein, mein freund.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #3 from Erich Hoover ehoover@mines.edu 2011-09-15 20:54:15 CDT --- Hmm, what distro are you using? Have you tried creating a fresh wine prefix and then installing and running the game from there?
I just tried installing the game fresh in Wine 1.3.28 and it worked great, I even skipped all the DLL instructions except for GfWLive.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #4 from mister_a@aol.com 2011-09-25 11:20:14 CDT --- Created attachment 36550 --> http://bugs.winehq.org/attachment.cgi?id=36550 Screenshot indicating the problem.
This is a screenshot of the problem once you hit Play on the launcher.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #5 from Erich Hoover ehoover@mines.edu 2011-09-25 14:46:21 CDT --- Well, if you've tried those other suggestions.... What patch of Fallout 3 are you using (the version I have is 1.7)?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #6 from mister_a@aol.com 2011-09-25 16:38:50 CDT --- (In reply to comment #5)
Well, if you've tried those other suggestions.... What patch of Fallout 3 are you using (the version I have is 1.7)?
I just installed that patch hours ago, no luck.
http://bugs.winehq.org/show_bug.cgi?id=28035
mister_a@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mister_a@aol.com
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #7 from Erich Hoover ehoover@mines.edu 2011-10-04 14:14:16 CDT --- (In reply to comment #4)
Created attachment 36550 [details] Screenshot indicating the problem.
This is a screenshot of the problem once you hit Play on the launcher.
It looks like you're running the game in windowed mode, have you tried running it full-screen?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #8 from mister_a@aol.com 2011-10-08 09:48:19 CDT --- (In reply to comment #7)
(In reply to comment #4)
Created attachment 36550 [details] Screenshot indicating the problem.
This is a screenshot of the problem once you hit Play on the launcher.
It looks like you're running the game in windowed mode, have you tried running it full-screen?
I've tried both modes, that SOB won't run.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #9 from Erich Hoover ehoover@mines.edu 2011-10-08 09:55:13 CDT --- (In reply to comment #8)
... I've tried both modes, that SOB won't run.
Well, I noticed someone on the New Vegas page mentioning that it was detecting their graphics card wrong in the launcher and when they launch it that it reports a similar error. Could you report back with your graphics card information and what the game thinks it is?
http://bugs.winehq.org/show_bug.cgi?id=28035
GMan wine@gman.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@gman.me.uk
--- Comment #10 from GMan wine@gman.me.uk 2011-12-05 14:37:27 CST --- I see the same error on my box too Lubuntu 11.10 w/NVidia 7900GT Wine 1.3.34 (from wine ppa) Steam version of Fallout:NV Game detects my graphics card as a 7800GT
Crashes immediately after I press play. Log attached. (mostly seems the same as the original log, but I don't see a backtrace after the "starting debugger" line)
Note that stem was installed using winetricks, but I get the same error if steam is installed directly in default prefix; -- and also if using wine from default lubuntu install. Also tried a bunch of different settings as per the appDB for Fallout:NV (with/without d3dx9, quartz, vcrun2008 etc -- all gives the same error)
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #11 from GMan wine@gman.me.uk 2011-12-05 14:38:13 CST --- Created attachment 37813 --> http://bugs.winehq.org/attachment.cgi?id=37813 Wine output from launching F:NV through Steam until crash
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #12 from Erich Hoover ehoover@mines.edu 2011-12-05 14:45:31 CST --- Hmm. Have you guys tried disabling "gameoverlayrenderer" in the winecfg "Libaries" tab?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #13 from GMan wine@gman.me.uk 2011-12-05 14:49:23 CST --- Yup, tried that. Also force disabled all in-game overlay related settings in Steam too (btw, I don't think the original error posted by mister_a was using Steam -- so, I don't *think* this is a Steam overlay issue)
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #14 from Erich Hoover ehoover@mines.edu 2011-12-05 14:54:27 CST --- (In reply to comment #13)
Yup, tried that. Also force disabled all in-game overlay related settings in Steam too (btw, I don't think the original error posted by mister_a was using Steam -- so, I don't *think* this is a Steam overlay issue)
I bought the disk version and it still uses Steam. Have you tried validating your game files?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #15 from GMan wine@gman.me.uk 2011-12-05 14:58:47 CST --- Sorry, didn't realise the disk version also uses Steam. But yes, I've tried validating the game files, deleting a few files, and forcing a redownload/reverification, wiping the wineprefix and reinstalling Steam/Fallout a bunch of times (mostly to try out different combinations of winetricks) -- all gives me the same error.
I also tried a no-cd version of FalloutNVLauncher.exe and got the exact same trace as mister_a (same backtrace)
Anything else I can try? Any reason the game detects my graphics card incorrectly? Is it related?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #16 from Erich Hoover ehoover@mines.edu 2011-12-05 15:11:46 CST --- (In reply to comment #15)
... Anything else I can try? Any reason the game detects my graphics card incorrectly? Is it related?
Interesting, yes - you should try overriding the video card detection by following the instructions on the Wiki for VideoPciDeviceID/VideoPciVendorID: http://wiki.winehq.org/UsefulRegistryKeys
I'm going to guess that since the graphics card is detected incorrectly that the game or Wine tries to attempt something invalid.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #17 from GMan wine@gman.me.uk 2011-12-05 15:21:26 CST --- And wow! It works! Thanks a lot.
The video card is now detected as just "Direct3D HAL" instead of NVidia 7800 GT -- but the game does start.
Do you need any further logs to figure out why the detection fails (I'm happy to get my Fallout fix now! :)
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #18 from Erich Hoover ehoover@mines.edu 2011-12-05 15:42:42 CST --- (In reply to comment #17)
And wow! It works! Thanks a lot.
The video card is now detected as just "Direct3D HAL" instead of NVidia 7800 GT -- but the game does start.
Do you need any further logs to figure out why the detection fails (I'm happy to get my Fallout fix now! :)
What does running "glxinfo | grep renderer" in a terminal tell you and what are your Vendor and Device ID codes?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #19 from GMan wine@gman.me.uk 2011-12-05 15:51:52 CST ---
What does running "glxinfo | grep renderer" in a terminal tell you and what are your Vendor and Device ID codes?
$ glxinfo | grep renderer OpenGL renderer string: GeForce 7900 GT/GTO/PCI/SSE2
$ lspci -n | grep 0300 01:00.0 0300: 10de:0291 (rev a1)
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #20 from Erich Hoover ehoover@mines.edu 2011-12-05 16:57:43 CST --- (In reply to comment #19)
What does running "glxinfo | grep renderer" in a terminal tell you and what are your Vendor and Device ID codes?
$ glxinfo | grep renderer OpenGL renderer string: GeForce 7900 GT/GTO/PCI/SSE2
$ lspci -n | grep 0300 01:00.0 0300: 10de:0291 (rev a1)
Well, judging on these lines of code I believe we can solve your problem: ---- {"7900", CARD_NVIDIA_GEFORCE_7800GT}, /* Geforce 7 - highend */ {"7800", CARD_NVIDIA_GEFORCE_7800GT}, /* Geforce 7 - highend */ ----
I'll look into it tonight and then send you a patch to try.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #21 from GMan wine@gman.me.uk 2011-12-06 12:35:10 CST --- Created attachment 37832 --> http://bugs.winehq.org/attachment.cgi?id=37832 NV crash on starting a new game after manually setting PID & VID in registry
So, I didn't actually get around to starting a new game yesterday (was waiting to transfer my saves from a windows PC). Upon starting a new game, I get another crash Full log attached...
The final GLXBadDrawable error in the log only pops up after I do an xkill of the now crashed Fallout window
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #22 from Erich Hoover ehoover@mines.edu 2011-12-06 13:11:32 CST --- Created attachment 37833 --> http://bugs.winehq.org/attachment.cgi?id=37833 wined3d: Add support for Nvidia 7900 series.
(In reply to comment #21)
... So, I didn't actually get around to starting a new game yesterday (was waiting to transfer my saves from a windows PC). Upon starting a new game, I get another crash ...
Please try the attached patch, it's probably freaking out because it's using the generic renderer rather than the Nvidia-specific code.
http://bugs.winehq.org/show_bug.cgi?id=28035
GMan wine@gman.me.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #37813|0 |1 is obsolete| | Attachment #37832|0 |1 is obsolete| |
--- Comment #23 from GMan wine@gman.me.uk 2011-12-06 15:30:59 CST --- Created attachment 37836 --> http://bugs.winehq.org/attachment.cgi?id=37836 Crash on game start
Now my graphics card is correctly detected by the launcher. But it crashes when I press Play (superficially like the original error). I assume with the new patch, I no longer need the VideoPciDeviceID/VideoPciVendorID overrides in the registry (the trace is with the Direct3D key removed)
I did not use a clean wineprefix, just did a "make install" and ran my existing install of Steam/Fallout:NV. If you think it's worth me running this from a clean prefix, let me know
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #24 from Erich Hoover ehoover@mines.edu 2011-12-06 15:53:16 CST --- (In reply to comment #23)
... Now my graphics card is correctly detected by the launcher. But it crashes when I press Play (superficially like the original error). I assume with the new patch, I no longer need the VideoPciDeviceID/VideoPciVendorID overrides in the registry (the trace is with the Direct3D key removed) ...
Yeah, that was the idea. Apparently the 7900 and 7800 are really the same hardware - so the game detecting the "wrong" card should be fine (the patch shouldn't really be necessary). I'm going to guess that this is a driver or X11 problem, could you run "nvidia-settings --version" and "Xorg -version" in a terminal and give me the results?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #25 from GMan wine@gman.me.uk 2011-12-06 16:03:05 CST ---
could you run "nvidia-settings --version" and "Xorg -version" in a terminal and give me the results?
$ nvidia-settings --version
nvidia-settings: version 290.10 (buildd@radium) Wed Nov 23 11:46:40 UTC 2011 The NVIDIA X Server Settings tool.
This program is used to configure the NVIDIA Linux graphics driver. For more detail, please see the nvidia-settings(1) man page.
Copyright (C) 2004 - 2010 NVIDIA Corporation.
------------------------------------------------
$ Xorg -version
X.Org X Server 1.10.4 Release Date: 2011-08-19 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-29-server i686 Ubuntu Current Operating System: Linux desktop 3.0.0-13-generic-pae #22-Ubuntu SMP Wed Nov 2 15:17:35 UTC 2011 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic-pae root=UUID=16a6d65b-36b9-4a23-a0f7-75d3922d19d0 ro quiet splash vt.handoff=7 Build Date: 19 October 2011 05:09:41AM xorg-server 2:1.10.4-1ubuntu4.2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.22.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #26 from Erich Hoover ehoover@mines.edu 2011-12-06 21:02:53 CST --- (In reply to comment #25)
... Current Operating System: Linux desktop 3.0.0-13-generic-pae #22-Ubuntu SMP Wed ...
Hmm, it might be the PAE kernel - but I doubt it. Have you tried setting bUseThreadedAI=1 and iNumHWThreads=2 like is suggested on the AppDB page?
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #27 from GMan wine@gman.me.uk 2011-12-07 12:02:24 CST --- (In reply to comment #26)
Have you tried setting bUseThreadedAI=1 and iNumHWThreads=2 like is suggested on the AppDB page?
Hmm... isn't that on the Fallout AppDB page and not Fallout:New Vegas (atleast I didn't find it on the F:NV page)?
I opened up Fallout_default.ini and inserted/changed it to bUseThreadedAI=1 and iNumHWThreads=2 with no apparent change (can upload log if required)
so the game detecting the "wrong" card should be fine (the patch shouldn't really be necessary)
Well, without the patch (and the associated VID overrides in the registry), the game detects the graphics card as DIrect3D HAL and actually loads the game. It crashes when I hit New Game (the intro movie plays and it crashes attempts to load the game proper -- i.e, just before the scene when you wake up in bed)
With the patch (and without the registry overrides) the game crashes when I hit play in the launcher
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #28 from Erich Hoover ehoover@mines.edu 2011-12-07 12:23:08 CST --- (In reply to comment #27)
(In reply to comment #26)
Have you tried setting bUseThreadedAI=1 and iNumHWThreads=2 like is suggested on the AppDB page?
Hmm... isn't that on the Fallout AppDB page and not Fallout:New Vegas (atleast I didn't find it on the F:NV page)?
Yes, sorry - both games use essentially the same engine.
... With the patch (and without the registry overrides) the game crashes when I hit play in the launcher
Go ahead and ignore the patch. Have you tried running the game (without registry overrides) with different graphics settings configured in the launcher? I'm wondering if this problem is specific to a particular graphics feature.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #29 from GMan wine@gman.me.uk 2011-12-07 12:34:02 CST --- (In reply to comment #28)
Go ahead and ignore the patch. Have you tried running the game (without registry overrides) with different graphics settings configured in the launcher? I'm wondering if this problem is specific to a particular graphics feature.
Just tried it again. Options->Low Hit advanced and turned everything to Off or Low 4:3, 800x600 (the lowest resolution it would go to)
Same crash on hitting "Play"
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #30 from Erich Hoover ehoover@mines.edu 2012-06-19 08:28:32 CDT --- (In reply to comment #29)
... Same crash on hitting "Play"
Clearly I ran out of ideas on this, I'm sorry I didn't say so at the time though. However, I recently ran into the same problem and I was curious if you have any custom mods loaded. Even though I just had the FO3FPS.esm mod in the game folder, even though the mod was disabled in the menu, I found that I was unable to launch F3 at all. I really hope that helps.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #31 from GMan wine@gman.me.uk 2012-06-19 10:41:15 CDT --- No mods, I'm afraid. Just Fallout:NV installed at the time
I must admit I switched to running it under windows for the last 6 months, and now my linux PC is different (both HW & SW) to the one I reported the bug on -- so I'm not sure if I can even reproduce this bug anymore (I haven't tried recently though)
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #32 from Erich Hoover ehoover@mines.edu 2012-06-20 15:15:46 CDT --- (In reply to comment #31)
No mods, I'm afraid. Just Fallout:NV installed at the time
I must admit I switched to running it under windows for the last 6 months, and now my linux PC is different (both HW & SW) to the one I reported the bug on -- so I'm not sure if I can even reproduce this bug anymore (I haven't tried recently though)
Alright, well let me know if you give it a try. It could also be that your Wine was compiled with a gcc other than 4.5, I noticed recently that that can cause problems with F:NV. It's possible that really recent versions work, but the version of 4.6 that I have won't.
http://bugs.winehq.org/show_bug.cgi?id=28035
Daniel Cantarín omega_canta@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |omega_canta@yahoo.com
--- Comment #33 from Daniel Cantarín omega_canta@yahoo.com --- I had this problem today. This bug discussion didn't helped me.
Fallout 3 GOTY Steam.
I have a "steam" wineprefix created by winetricks on an Ubuntu 12.04 x64. So, i debugged this problem by running the game via console command:
env WINEPREFIX="/home/username/.local/share/wineprefixes/steam" wine C:\windows\command\start.exe steam://rungameid/22370
That way, i could saw that the game launcher said there was no xlive.dll on this wineprefix: even then the xlive installer was executed by steam and it was installed successfuly.
So, i tried to install GFW using winetricks, and the installation returned an error.
Then, i just used another wineprefix for rogue installers like this one, installed OK there, and then copied the generated files: a directory inside "Program Files", and some loose files inside "system32". The files where "xlive.dll", "msasn1.dll", "msrepl40.dll", and don't remember the others: they were just asked for in the console output running the command stated before (that is: every time i was trying to run it, it crashed tellimg me of missing files that were present in the alternate wineprefix).
Once all the files needed were copied to the correct wineprefix, the game worked.
http://bugs.winehq.org/show_bug.cgi?id=28035
--- Comment #34 from Erich Hoover erich.e.hoover@gmail.com --- (In reply to comment #33)
I had this problem today. This bug discussion didn't helped me.
Fallout 3 GOTY Steam. ... Once all the files needed were copied to the correct wineprefix, the game worked.
That's an interesting component to this, did anyone else who is having this problem get the game through Steam?
http://bugs.winehq.org/show_bug.cgi?id=28035
spamatica@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spamatica@gmail.com
--- Comment #35 from spamatica@gmail.com --- I think I had the same bug and yes, with Steam. I installed Steam through Play on Linux, what was needed after installing Fallout 3 was copying the "msasn1.dll" file referenced in the instructions and (I think) removing the DotNetFX dir from the "Program Files/Steam/SteamApps/common/Fallout 3" folder, after that it's been running fine for several hours now.
http://bugs.winehq.org/show_bug.cgi?id=28035
Jonas Jelten jonas.jelten@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonas.jelten@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=28035
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://store.steampowered.c | |om/app/22370/ CC| |focht@gmx.net
--- Comment #36 from Anastasius Focht focht@gmx.net --- Hello folks,
the game works out of the box for me (Steam GotY edition).
Since the bug has been recycled for multiple issues over time, I'd suggest to close this. I doubt that recent comments have same issue as OP. You most likely have a broken Steam prefix if you require native components or other workaround. This is a common cause for many Steam related bug reports, making them invalid.
Regards
https://bugs.winehq.org/show_bug.cgi?id=28035
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |obfuscation Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Summary|Fallout 3 crashes when |Fallout 3 crashes when |hitting play on launcher. |hitting play on launcher | |(Games For Windows Live | |2.x)
--- Comment #37 from Anastasius Focht focht@gmx.net --- Hello folks,
unfortunately after OP's initial report the bug became a bit messy with completely unrelated issues mixed in.
--- snip --- ... fixme:advapi:RegisterEventSourceW ((null),L"XLive"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0002,0x0000,0x80000002,(nil),0x0004,0x00000000,0x32e4c8,(nil)): stub fixme:advapi:DeregisterEventSource (0xcafe4242) stub wine: Unhandled page fault on read access to 0x00000028 at address 0xbe9165 (thread 0009), starting debugger... Unhandled exception: page fault on read access to 0x00000028 in 32-bit code (0x00be9165). --- snip ---
OP's backtrace is clearly a GFWL related crash.
Game folder 'installscript.vdf', GFWL part:
--- snip --- "GFWLive" { "HasRunKey" "HKEY_lOCAL_MACHINE\Software\Valve\Steam\Apps\22300" "process 1" "%windir%\system32\msiexec.exe" "command 1" "/i "%INSTALLDIR%\GFWLive\xliveredist.msi" /passive" "NoCleanUp" "2" "MinimumHasRunValue" "2" } --- snip ---
The GFWL redist installer itself: 'xliveredist.msi'
'xlive.dll' metadata, indicating a 2.x version (pre .NET)
--- snip --- Microsoft Corporation Games for Windows - LIVE DLL 2.0.0672.0 (PANORAMA_V2.00_RTM.081022-0447) Wednesday 22 October 2008, 05.29.02 --- snip ---
So what happens if one runs the game with clean prefix (no overrides/native garbage)?
--- snip --- $ WINEDEBUG=+tid,+seh,+relay,+snoop,+msvcrt wine ./steam.exe -applaunch 22370 -no-dwrite -allowdebug -nominidumps -windowed -nobreakpad >>log.txt 2>&1 ... 0009:trace:relay:load_list L"SnoopExclude" = L"tier0_s.*;vstdlib_s.*" ... 000d:Call KERNEL32.SetEnvironmentVariableA(386a3b18 "VR_PLATFORM_INSTALL_PATH",0aa03a20 "C:\Program Files\Steam\vr\runtime") ret=38303b0c 000d:Ret KERNEL32.SetEnvironmentVariableA() retval=00000001 ret=38303b0c 000d:Call KERNEL32.CreateProcessW(0a889380 L"C:\Program Files\Steam\steamapps\common\Fallout 3 goty\FalloutLauncher.exe",09cf9000 L""C:\Program Files\Steam\steamapps\common\Fallout 3 goty\FalloutLauncher.exe" -no-dwrite -allowdebug -nominidumps -windowed -nobreakpad",00000000,00000000,00000000,00000004,00000000,0a9d71c0 L"C:\Program Files\Steam\steamapps\common\Fallout 3 goty",0e6fb6e4,0e6fb7c0) ret=38303cae ... 005a:Call KERNEL32.__wine_kernel_init() ret=7bc5b286 ... 000d:Ret KERNEL32.CreateProcessW() retval=00000001 ret=38303cae ... 005a:Call KERNEL32.CreateProcessW(00000000,0033e558 L"C:\Program Files\Steam\steamapps\common\Fallout 3 goty\Fallout3.exe",00000000,00000000,00000000,00000410,00000000,00000000,0033dc10,0033dc00) ret=7e62f5d2 ... 0061:Call KERNEL32.__wine_kernel_init() ret=7bc5b286 ... 005a:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7e62f5d2 ... 0061:Ret PE DLL (proc=0x1791b27,module=0x1340000 L"xlive.dll",reason=PROCESS_ATTACH,res=0x1) retval=1 ... 0061:CALL xlive.5000(<unknown, check return>) ret=006efefe 0061:Call advapi32.RegisterTraceGuidsA(01410faa,00000000,01345864,00000003,0196673c,00000000,00000000,019747d8) ret=0141102f 0061:fixme:advapi:RegisterTraceGuidsA (0x1410faa, (nil), {d5b9ac76-d546-4891-bb8c-bfd865e5c7d5}, 3, 0x196673c, (null), (null), 0x19747d8): stub 0061:Ret advapi32.RegisterTraceGuidsA() retval=00000000 ret=0141102f ... 0061:Call KERNEL32.CreateFileW(0033f2a4 L"C:\windows\system32\xlive.dll.CAT",80000000,00000001,00000000,00000003,00000080,00000000) ret=013e6475 0061:Ret KERNEL32.CreateFileW() retval=0000017c ret=013e6475 ... 0061:Call KERNEL32.CreateFileW(0033f09c L"C:\windows\system32\xlive.dll",80000000,00000001,00000000,00000003,00000080,00000000) ret=013e5f07 0061:Ret KERNEL32.CreateFileW() retval=0000017c ret=013e5f07 ... 0061:Call KERNEL32.K32EnumProcessModules(ffffffff,0033ec80,000003fc,0033f08c) ret=01956c0d 0061:Ret KERNEL32.K32EnumProcessModules() retval=00000001 ret=01956c0d ... 0061:Call KERNEL32.CreateFileW(0033f0a0 L"C:\Program Files\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe.CAT",80000000,00000001,00000000,00000003,00000080,00000000) ret=013e6475 0061:Ret KERNEL32.CreateFileW() retval=0000017c ret=013e6475 ... 0061:Call KERNEL32.CreateFileW(0033f2a8 L"C:\Program Files\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe.CFG",80000000,00000001,00000000,00000003,00000080,00000000) ret=0140929e 0061:Ret KERNEL32.CreateFileW() retval=0000017c ret=0140929e ... 0061:Call oleaut32.SysAllocString(16b76e08 L"<Liveconfig>\r\n <titleid>425307D6</titleid>\r\n <titleversion>10000184</titleversion>\r\n <lankey>xxxxx</lankey>\r\n <enableCrossPlatformSystemLink>false</enableCrossPlatformSystemLink>\r\n <OriginalXliveTarget>1.2.0241.0</OriginalXliveTarget>\r\n </L"...) ret=0140fec6 ... 0061:Call KERNEL32.CreateFileW(0033f2a8 L"C:\Program Files\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe",80000000,00000001,00000000,00000003,00000080,00000000) ret=013e5f07 0061:Ret KERNEL32.CreateFileW() retval=0000017c ret=013e5f07 ... 0061:Call KERNEL32.LoadLibraryW(0033e9dc L"C:\Program Files\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe") ret=013e842e 0061:Ret KERNEL32.LoadLibraryW() retval=00400000 ret=013e842e ... 0061:Call KERNEL32.K32GetModuleInformation(ffffffff,00400000,0033e9c4,0000000c) ret=013e6178 0061:Ret KERNEL32.K32GetModuleInformation() retval=00000001 ret=013e6178 ... 0061:Call advapi32.RegisterEventSourceW(00000000,0134561c) ret=0141a296 0061:fixme:advapi:RegisterEventSourceW ((null),L"XLive"): stub 0061:Ret advapi32.RegisterEventSourceW() retval=cafe4242 ret=0141a296 0061:Call advapi32.ReportEventW(cafe4242,00000002,00000000,80000002,00000000,00000004,00000000,0033e438,00000000) ret=0141a2d6 0061:fixme:advapi:ReportEventW (0xcafe4242,0x0002,0x0000,0x80000002,(nil),0x0004,0x00000000,0x33e438,(nil)): stub 0061:Ret advapi32.ReportEventW() retval=00000001 ret=0141a2d6 0061:Call advapi32.DeregisterEventSource(cafe4242) ret=0141a2f6 0061:fixme:advapi:DeregisterEventSource (0xcafe4242) stub 0061:Ret advapi32.DeregisterEventSource() retval=00000001 ret=0141a2f6 ... 0061:Call advapi32.UnregisterTraceGuids(00000000,00000000) ret=01411042 0061:fixme:advapi:UnregisterTraceGuids 0: stub 0061:Ret advapi32.UnregisterTraceGuids() retval=00000078 ret=01411042 0061:RET xlive.5000(0033f9c8) retval=80004005 ret=006efefe ... --- snip ---
xlive.5000 = XLiveInitialize()
The game still continues despite XLive being unable to initialize. There are no further API calls to 'xlive.dll' in the error case, suggesting the vendor changed the hard requirement and not made it crash/exit anymore.
--- snip --- Bethesda Softworks Fallout3.exe 1.0.0.15 Wednesday 21 May 2014, 22.39.30' --- snip ---
Whatever "tricks" are suggested here ("copy <dit and dat> fixes this") - it has no effect (click "LIVE" in the game menu and see what happens).
Here are some infos/discussions regarding the Steam version of Fallout3:
http://www.escapistmagazine.com/news/view/131031-Fallout-3-Set-to-Remove-Gam...
http://www.neogaf.com/forum/showthread.php?t=745237
Anyway, I applied my fix for bug 33034 and got GFWL 2.x working:
--- snip --- 0062:CALL xlive.5000(<unknown, check return>) ret=006efefe ... 0062:RET xlive.5000(0033f9c8) retval=00000000 ret=006efefe ... 0062:CALL xlive.5310(<unknown, check return>) ret=006eff17 ... 0062:RET xlive.5310() retval=00000000 ret=006eff17 0062:CALL xlive.652(<unknown, check return>) ret=006eff2a ... 0062:RET xlive.652(00000001) retval=00000002 ret=006eff2a 0062:CALL xlive.5270(<unknown, check return>) ret=006eff52 ... 0062:RET xlive.5270(0000002f,00000000) retval=000002c8 ret=006eff52 ... 0062:CALL xlive.5002(<unknown, check return>) ret=00624aad ... 0062:RET xlive.5002() retval=00000000 ret=00624aad ... --- snip ---
xlive.5310 -> XOnlineStartup xlive.5002 -> XLiveRender
Within game menu, clicking 'LIVE' will then get you a nice GFWL overlay/menu with options to create online profile, login etc.
Resolving as dupe of bug 33034 since the fix works here too.
Regards
*** This bug has been marked as a duplicate of bug 33034 ***
https://bugs.winehq.org/show_bug.cgi?id=28035
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #38 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=28035
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Component|-unknown |ntdll URL|http://store.steampowered.c |https://web.archive.org/web |om/app/22370/ |/20111121101950/http://down | |load.microsoft.com/download | |/E/6/1/E61EE391-8B89-425D-A | |80A-614A44FD3345/gfwliveset | |up.exe
-
wine-bugs＠winehq.org -
WineHQ Bugzilla