http://bugs.winehq.org/show_bug.cgi?id=21267
Summary: Fallout 3 GOTY: Crashes Randomly Product: Wine Version: 1.1.35 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: [email protected] ReportedBy: [email protected]
Created an attachment (id=25570) --> (http://bugs.winehq.org/attachment.cgi?id=25570) The Console log after a crash during the black screen after the opening video.
Fallout 3 Game of the Year Edition will crash in semi-random places when starting a New game. Some of these places include the black screen right after the opening video, after inputting the player's name, after customizing the character, During the Birthday scene when you are shooting the radroach with your BB Gun, etc. It seams to be a script executing error as the game is usually supposed to be doing something (ie. controlling the radroach so it doesn't attack the player, moving an NPC somewhere, setting game values(player name, how the player looks) when it stops. The Game has two different crashes for these events, but only one shows at anytime. The first one is obvious and the rarest a Message box pops up saying the Program encountered an error an needs to close. A stacktrace is able to be retrieved in this case. The second one is a freeze, ie the game is no longer controllable by the user, and the render has stopped. Music and sound effects (such as talking) still work until the program is killed, but the player cannot make any sound effects such as walking or shooting a gun. The game's menus are also disabled.
I've followed the hq's guides on getting the program to run, with the small exception of manually installing the Games for Windows Live client and .Net Framework. As the game's installer hangs when the installer for those components have crashed, and thus must be killed to allow the installer to continue.
It must be noted that a save game made after Vault 101 will work normally. It's unknown if it's the result of the save being from another computer with the game running normally or just after Vault 101 because i can't get the game past Vault 101 when starting a new game.
System Specs: Mandriva Linux 2010.0 X86_64 Intel Core 2 Quadcore Latest Nvidia Drivers as of 1/5/2010 Wine 1.1.35 Mandriva Linux Repo (If anyone needs more just ask.)
http://bugs.winehq.org/show_bug.cgi?id=21267
Vitaliy Margolen [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias|codebase |
http://bugs.winehq.org/show_bug.cgi?id=21267
blaise [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
--- Comment #1 from blaise [email protected] 2010-03-12 13:39:41 ---
The second one is a freeze, ie the game is no longer controllable by the user, and the render has stopped. Music and sound effects (such as talking) still work until the program is killed, but the player cannot make any sound effects such as walking or shooting a gun. The game's menus are also disabled.
I've been expereincing this myself due to a memory leak somewhere eating all the ram. Take a look at 'top' while running FO3 and see if that's the case with yours also.
http://bugs.winehq.org/show_bug.cgi?id=21267
Minyie Diaz [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
--- Comment #2 from Minyie Diaz [email protected] 2010-07-07 12:14:23 --- Hi, This happens to me aswell.
The game runs fine until the intro video after it, it hangs in a black screen.
Only option is to hard reset.
Only difference is that i am using a macosx 10.6.4 Ati 4870 E8400 3ghz 4gb RAM
http://bugs.winehq.org/show_bug.cgi?id=21267
--- Comment #3 from Austin English [email protected] 2010-07-10 14:38:04 --- This should be fixed, though you'll probably get bug 21973.
http://bugs.winehq.org/show_bug.cgi?id=21267
Dan Kegel [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |[email protected] Ever Confirmed|0 |1
--- Comment #4 from Dan Kegel [email protected] 2010-11-17 12:12:56 CST --- I think I saw this; on my first run, it hung as you described just after I got out of the playpen. Second run was fine (I got all the way through the birthday party sequence and killing the radroach, then quit normally). This was on 1.3.7, gentoo, nvidia gt 240.
http://bugs.winehq.org/show_bug.cgi?id=21267
Brandon Corujo [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
http://bugs.winehq.org/show_bug.cgi?id=21267
Jonas Jelten [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
https://bugs.winehq.org/show_bug.cgi?id=21267
[email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
--- Comment #5 from [email protected] --- Seriously.
Last post year 2010.
Is this still an issue with 1.7 series of wine?
https://bugs.winehq.org/show_bug.cgi?id=21267
[email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
--- Comment #6 from [email protected] --- Yes the game crashes randomly, but then again, it does so in windows, and so does every Bethesda game ive ever played to be honest.
For the record fallout 3 (and skyrim) both crash LESS on wine than they do on windows.
Its mainly memory related, mods can aggravate the issue to extreme levels if you are not using a 64-bit OS with a 4GB hack/patch enabled on the fallout/skyrim/whatever .exe
https://bugs.winehq.org/show_bug.cgi?id=21267
mirh [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
--- Comment #7 from mirh [email protected] --- You sure these random crashes aren't the "usual" ones (also frequent under Windows)? http://pcgamingwiki.com/wiki/Fallout_3#Game_crashes_randomly
https://bugs.winehq.org/show_bug.cgi?id=21267
[email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected], | |[email protected], | |[email protected]
--- Comment #8 from [email protected] --- (In reply to Dan Kegel from comment #4)
I think I saw this; on my first run, it hung as you described just after I got out of the playpen. Second run was fine (I got all the way through the birthday party sequence and killing the radroach, then quit normally). This was on 1.3.7, gentoo, nvidia gt 240.
Last test 2010.
Last 2 comments say that this is expected behaviour of the game.
I would say abandoned bug. You can't even improve this without testing against newer wine.
https://bugs.winehq.org/show_bug.cgi?id=21267
--- Comment #9 from mirh [email protected] --- (In reply to winetest from comment #8)
Last 2 comments say that this is expected behaviour of the game.
I would say abandoned bug. You can't even improve this without testing against newer wine.
Just found this https://appdb.winehq.org/objectManager.php?sClass=version&iId=14322#Comm...
Which quite likely means this was never a bug in the first place (aside of what's mentioned in comment 3 at most)
https://bugs.winehq.org/show_bug.cgi?id=21267
tokktokk [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
https://bugs.winehq.org/show_bug.cgi?id=21267
[email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
https://bugs.winehq.org/show_bug.cgi?id=21267
pattietreutel [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
https://bugs.winehq.org/show_bug.cgi?id=21267
Neko-san [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
https://bugs.winehq.org/show_bug.cgi?id=21267
m1m1k4tz [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected]
--- Comment #10 from m1m1k4tz [email protected] --- Sometimes this happens to me as well but I think it also happens on the native version also capping the monitor at 60 fps and using vsync with dxvk fixes most crashes for me I think dxvk has some magic where you can use more ram on 32 bit program that helps
https://bugs.winehq.org/show_bug.cgi?id=21267
Ken Sharp [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED
--- Comment #11 from Ken Sharp [email protected] --- (In reply to nerdistmonk from comment #6)
Yes the game crashes randomly, but then again, it does so in windows, and so does every Bethesda game ive ever played to be honest.
(In reply to mirh from comment #7)
You sure these random crashes aren't the "usual" ones (also frequent under Windows)? http://pcgamingwiki.com/wiki/Fallout_3#Game_crashes_randomly
(In reply to winetest from comment #8)
Last test 2010.
Last 2 comments say that this is expected behaviour of the game.
(In reply to mirh from comment #9)
Just found this https://appdb.winehq.org/objectManager.php?sClass=version&iId=14322#Comm... 95588
Which quite likely means this was never a bug in the first place
14 years for a bug that exists in Windows is probably long enough. --> Invalid.
https://bugs.winehq.org/show_bug.cgi?id=21267
--- Comment #12 from Austin English [email protected] --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=21267
Austin English [email protected] changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Austin English [email protected] --- Actually closing.