http://bugs.winehq.org/show_bug.cgi?id=32973
Bug #: 32973 Summary: Fallout 3: Game crashes after hitting "New game" Product: WineHQ Apps Database Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: raddyroro@gmail.com Classification: Unclassified
I do not have a backlog. Wine just tells me the game has crashed and I need to force quit it to get rid of it. The game just hangs after the crash window at the loading screen after hitting "New game"
I used PlayonLinux to install it because that got me farther than manually installing it
Specs: Ubuntu 12.10 Intel i7 Nvidia Geforce GT 520M 1 GB on video card 8 Gb Ram
http://bugs.winehq.org/show_bug.cgi?id=32973
raddyroro@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |raddyroro@gmail.com Severity|normal |major
http://bugs.winehq.org/show_bug.cgi?id=32973
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|appdb-unknown |-unknown Product|WineHQ Apps Database |Wine Severity|major |normal
--- Comment #1 from Austin English austinenglish@gmail.com 2013-02-13 22:15:27 CST --- Not an appdb bug. Please see http://wiki.winehq.org/Bugs for how to file a bug. We need terminal output/wine version/etc. (and PlayOnLinux isn't supported).
Use the forum for general help.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #2 from Austin English austinenglish@gmail.com 2013-02-14 11:01:03 CST --- *** Bug 32975 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #3 from raddyroro@gmail.com 2013-02-14 14:46:56 CST --- How do i label it for Fallout 3 then. I really want help and the FAQ is not helping
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #4 from Austin English austinenglish@gmail.com 2013-02-14 18:23:01 CST --- (In reply to comment #3)
How do i label it for Fallout 3 then. I really want help and the FAQ is not helping
You need to submit it through the appdb interface.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #5 from raddyroro@gmail.com 2013-02-14 19:02:32 CST --- finally
http://bugs.winehq.org/show_bug.cgi?id=32973
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #6 from Austin English austinenglish@gmail.com 2013-02-14 19:29:24 CST --- Dupe.
*** This bug has been marked as a duplicate of bug 29420 ***
http://bugs.winehq.org/show_bug.cgi?id=32973
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|DUPLICATE |
--- Comment #7 from Austin English austinenglish@gmail.com 2013-02-14 19:30:23 CST --- Oops, sorry, this was 3, not New Vegas.
http://bugs.winehq.org/show_bug.cgi?id=32973
Jonas Jelten jonas.jelten@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonas.jelten@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32973
Erich Hoover ehoover@mines.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoover@mines.edu
--- Comment #8 from Erich Hoover ehoover@mines.edu 2013-02-15 06:34:55 CST --- Did you compile Wine yourself or use a pre-compiled package? I've had this problem when Wine is compiled with gcc 4.6 and I've not seen this issue in any other case, but I haven't tested it really recently.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #9 from moritz-wine@twoticketsplease.de 2013-04-06 12:55:06 CDT --- Created attachment 44102 --> http://bugs.winehq.org/attachment.cgi?id=44102 Backtrace of crash
I think I am experiencing the same issue: The game crashes when starting a new game. I'm attaching the corresponding backtrace.
http://bugs.winehq.org/show_bug.cgi?id=32973
moritz-wine@twoticketsplease.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |moritz-wine@twoticketspleas | |e.de
--- Comment #10 from moritz-wine@twoticketsplease.de 2013-04-06 12:57:49 CDT --- Note that this is not the launcher that's crashing but the game itself when hitting the "New Game" option in the game menu. Thus I think the "Dupe" marking is wrong.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #11 from Erich Hoover ehoover@mines.edu 2013-04-09 17:14:54 CDT --- (In reply to comment #10)
Note that this is not the launcher that's crashing but the game itself when hitting the "New Game" option in the game menu. Thus I think the "Dupe" marking is wrong.
Could you please try compiling Wine with GCC 4.5? Last time I tested things that was the only version of GCC where Fallout 3 would launch without crashing.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #12 from moritz-wine@twoticketsplease.de 2013-04-10 08:05:43 CDT --- (In reply to comment #11)
Could you please try compiling Wine with GCC 4.5? Last time I tested things that was the only version of GCC where Fallout 3 would launch without crashing.
Thanks for responding! I'll see what I can do. I'm on GCC 4.8 here, not sure how easy it is to downgrade or how to use a local version. Any indicators as to what might be the cause for this possible degradation?
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #13 from Oz oz.tamari@gmail.com 2013-06-10 10:29:17 CDT --- Created attachment 44732 --> http://bugs.winehq.org/attachment.cgi?id=44732 Debug when using wine 1.5.31 compiled with gcc-4.5.4 debug
I think I have the same error as described above.
I tried both when compiling wine with gcc-4.6.3 and gcc-4.5.4, and got same result: After installing FO3 and 1.0.7 patch, when starting a new game by executing "falloutLauncher.exe" -> Choosing "Play" -> "New" game crushes.
http://bugs.winehq.org/show_bug.cgi?id=32973
zirconites-plus@yahoo.com.br changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zirconites-plus@yahoo.com.b | |r
--- Comment #14 from zirconites-plus@yahoo.com.br 2013-07-05 17:32:04 CDT --- When the card info is something like an old Nvidia device:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Wine\Direct3D] "AlwaysOffscreen"="disabled" "DirectDrawRenderer"="opengl" "Multisampling"="disabled" "OffscreenRenderingMode"="fbo" "PixelShaderMode"="enabled" "VertexShaders"="hardware" "VideoMemorySize"="512" "VideoPciDeviceID"=dword:00000402 "VideoPciVendorID"=dword:000010de
The game will work fine on Wine 1.6-rc4, Ivy Bridge 4000, with a fake device name.
Original concept extracted from: https://appdb.winehq.org/commentview.php?iAppId=8559&iVersionId=14322&am...
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #15 from Henri Verbeet hverbeet@gmail.com 2013-07-08 07:52:32 CDT --- (In reply to comment #14)
Original concept extracted from: https://appdb.winehq.org/commentview.php?iAppId=8559&iVersionId=14322&am...
That sounds pretty much like bug 15839. I wonder how well this works on Windows with an Intel card.
http://bugs.winehq.org/show_bug.cgi?id=32973
babaei babaei.wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |babaei.wine@gmail.com
--- Comment #16 from babaei babaei.wine@gmail.com 2013-08-04 20:32:04 CDT --- (In reply to comment #14)
When the card info is something like an old Nvidia device:
The game will work fine on Wine 1.6-rc4, Ivy Bridge 4000, with a fake device name.
This fix worked for me. I'm using Wine 1.6 with an i7-4700MQ (HD Graphics 4600), and adding this to my registry allows Fallout 3 to run with the full settings (instead of hanging during loading).
http://bugs.winehq.org/show_bug.cgi?id=32973
Łukasz Janowski fuorviatos@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fuorviatos@gmail.com
--- Comment #17 from Łukasz Janowski fuorviatos@gmail.com --- I confirm the fix with creating fake video device does the trick with Intel HD 4000 hardware. Otherwise, the game would crash upon clicking "new game". I suggest it to be marked as confirmed.
http://bugs.winehq.org/show_bug.cgi?id=32973
mactrix b.adamski@mac.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |b.adamski@mac.com
--- Comment #18 from mactrix b.adamski@mac.com --- Same problem here on OS X 10.9. Backtrace attached.
I tried WS9Wine1.7.17 and I am on WS9Wine1.7.1D3DBoost
How can I create a fake video device?
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #19 from mactrix b.adamski@mac.com --- Created attachment 48329 --> http://bugs.winehq.org/attachment.cgi?id=48329 Backtrace, Mac, OS X 10.9
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #20 from mactrix b.adamski@mac.com --- More specific info please.
What registry file exactly (file name, path)?
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #21 from mactrix b.adamski@mac.com --- (In reply to zirconites-plus from comment #14)
More specific info please.
What registry (file name, path)?
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #22 from mactrix b.adamski@mac.com --- (In reply to zirconites-plus from comment #14)
The game will work fine on Wine 1.6-rc4, Ivy Bridge 4000, with a fake device name.
Ok, I was able to edit the registry within Wineskin exactly like you described (please ignore my previous two comments). Still doesn't work for me but I am on a MacBook Pro 13" Retina with Intel Iris. No idea what would make it work. It keeps crashing when starting a new game.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #23 from mactrix b.adamski@mac.com --- Created attachment 48345 --> http://bugs.winehq.org/attachment.cgi?id=48345 Edited Direct3D Registry
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #24 from Henri Verbeet hverbeet@gmail.com --- (In reply to mactrix from comment #22)
Ok, I was able to edit the registry within Wineskin exactly like you described
REG_BINARY is not the same as REG_DWORD. Also, note that Wineskin is not supported here, although I doubt it causes this particular issue.
http://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #25 from mactrix b.adamski@mac.com --- The new game crash should only occur on hardware with onboard Intel graphic. Systems using ATI or Nvidia graphic cards should not be affected.
I created http://bugs.winehq.org/show_bug.cgi?id=36226 for the specific bug under OS X. Everyone else should be able to fix this issue on Windows and Linux using the modified d3d9.dll file attached to http://bugs.winehq.org/show_bug.cgi?id=36226.
Hope this helps.
http://bugs.winehq.org/show_bug.cgi?id=32973
Brandon Corujo haku08879@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |haku08879@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #26 from Aldekein aldekein@myevil.info --- Created attachment 49802 --> https://bugs.winehq.org/attachment.cgi?id=49802 Wine 1.7.29 crash backtrace
Wine 1.7.29 still crashes on pressing "New game". Will try editing registry and replacing DLL...
https://bugs.winehq.org/show_bug.cgi?id=32973
Aldekein aldekein@myevil.info changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aldekein@myevil.info
--- Comment #27 from Aldekein aldekein@myevil.info --- dll workaround does not work for me.
The game does not start anymore, I see black screen and one of the last error messages in log:
fixme:d3d:debug_d3dformat Unrecognized 0x434f5441 (as fourcc: ATOC) WINED3DFORMAT! fixme:d3d:wined3d_get_format Can't find format unrecognized (0x434f5441) in the format lookup table
OS X 10.7.5, Wine 1.7.29, MacBook "Core 2 Duo" 2.1 13" (Early 2008 - MB402LL/A* - MacBook4,1 - A1181) - http://www.everymac.com/systems/apple/macbook/specs/macbook-core-2-duo-2.1-w...
https://bugs.winehq.org/show_bug.cgi?id=32973
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.5.31
https://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #28 from mactrix b.adamski@mac.com --- (In reply to Aldekein from comment #27)
dll workaround does not work for me.
Did you also add the d3d9 entry in winecfg?
Here you find the details for OS X but it should be the same for Linux:
https://www.youtube.com/watch?v=YYtX_NCDMe0
http://portingteam.com/files/file/8182-fallout-3-goty/
http://portingteam.com/files/file/8213-fallout-3-and-fallout-new-vegas-on-st...
https://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #29 from mactrix b.adamski@mac.com --- Nice workaround from user swswine, see comment 15 and following:
https://bugs.winehq.org/show_bug.cgi?id=39718#c15
https://bugs.winehq.org/show_bug.cgi?id=32973
mirh mirh@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh@protonmail.ch
--- Comment #30 from mirh mirh@protonmail.ch --- I'm fairly sure intel graphics cards (at least older ones) aren't even supposed to work under Windows http://pcgamingwiki.com/wiki/Fallout_3#Crash_when_starting_new_game_or_loadi...
https://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #31 from mactrix b.adamski@mac.com --- (In reply to mirh from comment #30)
I'm fairly sure intel graphics cards (at least older ones) aren't even supposed to work under Windows
Yes, this bug report can be closed. There are workarounds.
https://bugs.winehq.org/show_bug.cgi?id=32973
--- Comment #32 from mirh mirh@protonmail.ch --- It's not a wine bug in the first place, I'd say.
https://bugs.winehq.org/show_bug.cgi?id=32973
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #33 from Austin English austinenglish@gmail.com --- (In reply to mactrix from comment #31)
(In reply to mirh from comment #30)
I'm fairly sure intel graphics cards (at least older ones) aren't even supposed to work under Windows
Yes, this bug report can be closed. There are workarounds.
Invalid
https://bugs.winehq.org/show_bug.cgi?id=32973
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #34 from Bruno Jesus 00cpxxx@gmail.com --- Closing invalid bugs.
-
wine-bugs＠winehq.org