http://bugs.winehq.org/show_bug.cgi?id=18356
Summary: fallout 3: mouselook crashes Product: Wine Version: 1.1.20 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: anarchic.teapot@gmail.com
hi there, i use wine 1.1.20 (with video patch and registry settings) the game install and start fine, no problem in menus either.
my problem is that the game freeze only in some area, for example, near some doors (but not every doors). i enter some house, i realise this is not the house i wanted to go, i decide to go back so i do a 360deg turn with mouselook to go back through the door i just came from, and the game freeze before i could do my 360deg mouselook turn-around..
as i said, this doesn't happen for every doors.. right now i'm in grayditch, and i just walked into brandices house. but i can't get out.. as soon as i get close to their door the game freeze.. i can still hear music, but nothing else seems to work.. i can't move, look around, access menu.. nothing.. my only option is to start again from another save point and completely avoid this house.. i have the same problem with waterplant's door in megaton.. probably with some other doors too, but atm, there's those two i can think of.
someone experienced same problem ? any workaround ? my system: ubuntu jaunty gfx card : geforce 9600 gt nvidia driver: 185.19 (but i have same problem mentioned above with other driver version too it seems) wine: 1.1.20 (video patch and registry setting for fallout 3) fallout: 1.5 (i had same problem with previous version too)
please see attached terminal output
thanks for your attention
http://bugs.winehq.org/show_bug.cgi?id=18356
--- Comment #1 from nyarlatothep anarchic.teapot@gmail.com 2009-05-04 17:24:27 --- Created an attachment (id=20910) --> (http://bugs.winehq.org/attachment.cgi?id=20910) term output
http://bugs.winehq.org/show_bug.cgi?id=18356
Eduard - Gabriel Munteanu eduard.munteanu@linux360.ro changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |eduard.munteanu@linux360.ro
--- Comment #2 from Eduard - Gabriel Munteanu eduard.munteanu@linux360.ro 2009-08-19 08:05:58 --- This happens here as well on wine-1.1.27 patched with the VideoDescription patch.
It triggers very easily in the first playable level, at "age 1", by simply looking rightwards 90 degs until you see that frame with cursive script. This isn't the only way to do it, in fact it will happen very often and it's hard to avoid.
I use Gentoo Linux with an x86-64 kernel. Hardware specs: NVIDIA Geforce GTS 250, AMD Phenom II x4, 6 GiB RAM (happens with 1 GiB as well). I'm using the latest Fallout 3 patch and NVIDIA driver 185.18.14.
The bug has been reported in Appdb comments as well, with no success on fixing it.
http://bugs.winehq.org/show_bug.cgi?id=18356
--- Comment #3 from Eduard - Gabriel Munteanu eduard.munteanu@linux360.ro 2009-08-19 20:07:20 --- Found a workaround, tested like 3-4 times in a row and it didn't crash (it would do so in 90% of cases): add 'maxcpus=1' to Linux's command line (press 'e' when GRUB loads and edit the 'kernel' line).
Seems like a threading issue. Not sure whether it's Wine's fault or the game's fault.
Also tried to fiddle with Fallout.ini settings like those relating to threading, background loading and tasklets, flipping probably all of them, one at a time and testing. But it won't help. If only there was a simple setting not requiring to turn off SMP support...
Can anybody share more insight on this?
http://bugs.winehq.org/show_bug.cgi?id=18356
--- Comment #4 from Henri Verbeet hverbeet@gmail.com 2009-08-20 04:12:13 --- You could try schedtool or taskset. Doesn't solve the actual bug though.
http://bugs.winehq.org/show_bug.cgi?id=18356
--- Comment #5 from Eduard - Gabriel Munteanu eduard.munteanu@linux360.ro 2009-08-20 12:12:46 --- (In reply to comment #4)
You could try schedtool or taskset. Doesn't solve the actual bug though.
Hm, I thought about setting CPU affinity. If we can find the actual thread causing the deadlock, it will make for less side effects. Will try to set all threads on a single CPU (core), then refine the result.
And yes, it's not a fix, but a workaround. For all I know it could be Fallout3's fault; native Windows users complain about stability issues a lot.
http://bugs.winehq.org/show_bug.cgi?id=18356
--- Comment #6 from Eduard - Gabriel Munteanu eduard.munteanu@linux360.ro 2009-08-27 18:43:51 --- It's not Wine's fault, Fallout 3 seems to do the exact same thing on Windows as far as users say. Bethesda broke quad core support with one of their patches. The fix is to add the option "iNumHWThreads=2" to your Fallout.ini (even if no such variable is defined there yet). You can add it in the "[General]" section.
I found it on the AppDB page; the first time I went through it the symptoms I was experiencing didn't look similar so I missed it. It's also described on other websites, unrelated to Wine and/or Linux.
I think this bug can be safely closed as WONTFIX. It's their fault after all and I don't how it could be fixed from within Wine.
http://bugs.winehq.org/show_bug.cgi?id=18356
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-28 05:33:59 --- Invalid then.
http://bugs.winehq.org/show_bug.cgi?id=18356
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-28 05:34:31 --- Closing.