http://bugs.winehq.org/show_bug.cgi?id=21163
Summary: NFS4: Fails to start Product: Wine Version: 1.1.27 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: lukasz.wojnilowicz@gmail.com CC: hverbeet@gmail.com
Created an attachment (id=25402) --> (http://bugs.winehq.org/attachment.cgi?id=25402) terminal output on Wine 1.1.35
Need For Speed 4 High Stakes started fine in Wine 1.1.26 and doesn't start on Wine 1.1.27. Regression test did give:
377cda97e75588afd8bc4af0a126ae9f8ea2a6a8 is the first bad commit commit 377cda97e75588afd8bc4af0a126ae9f8ea2a6a8 Author: Henri Verbeet hverbeet@codeweavers.com Date: Wed Jul 22 10:41:06 2009 +0200
wined3d: Avoid destroying contexts that are current in another thread.
:040000 040000 6612945f894e7a5dcc5f0db2b081b2c3c0de7a3f 360c318ecb8d91a982de317c6d3800c729fb47ee M dlls
Additional info: -32 bit Fedora 12 -NVIDIA 9xxx with 195.30 drivers
http://bugs.winehq.org/show_bug.cgi?id=21163
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=21163
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #1 from Wylda wylda@volny.cz 2010-01-01 15:52:10 ---
Hi Lukasz, i can't confirm this. NFS4 works for me. Tested under 1.1.27, 1.1.35 and also 1.1.35-364-g9dc584d. To be sure we are doing it the same way; my steps:
1. winecfg -> Win version: Win 98 2. wine autorun.exe -> Full install 3. winecfg -> Win version: Win XP (Bug 7115 comment #11) 4. wine 3DSetup.exe -> choose Software Renderer 5. winecfg -> Win version: Win 98 6. wine nfshs.exe
and it works. I tried unpatched CD version and also i tried to patch NFS4 to v4.5. Everything works perfectly in both versions.
Chmmm... The difference could be graphics driver. I have nVidia 8600GT, v190.53 & 32bit Debian Lenny. I'm bit lazy to try nVidia's Beta drivers :-/ OK, i will give it a try...
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #2 from Wylda wylda@volny.cz 2010-01-01 16:16:01 --- Created an attachment (id=25491) --> (http://bugs.winehq.org/attachment.cgi?id=25491) working here; log from wine-1.1.35-364-g9dc584d
So it works for me even with NVIDIA 195.30. Maybe if you compile wine yourself, could you try to disable any gcc's optimizations? I use (before ./configure):
export CC="gcc" CFLAGS="-g -O0" CXXFLAGS="-g -O0"
Do not know, what else could be the difference...
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #3 from NSLW lukasz.wojnilowicz@gmail.com 2010-01-02 10:16:47 ---
(In reply to comment #1)
Hi Lukasz, i can't confirm this. NFS4 works for me. Tested under 1.1.27, 1.1.35 and also 1.1.35-364-g9dc584d.
You tested it wrong way, but I didn't give any steps to reproduce so I'm here to blame. Anyhow I run NFS4 with hardware acceleration and not on software renderer. I admit it works with software renderer as you've said. But try this steps and you won't run NFS4 on Wine higher than 1.1.26:
1. winecfg -> Win version: Win 98 2. wine setup.exe -> Full install 3. winecfg -> Win version: Win XP 4. download unofficial patch from http://www.hsscoring.com/download/NFS_HS_SP_Setup_(V3.0_beta_1.63) 5. run it and select only "EA's 4.50 Patch" and "NoCollision & NoCD" from "Patched nfshs.exe file" 6. wine 3DSetup.exe -> choose Software Renderer 7. regedit -> HKEY_LOCAL_MACHINE\Software\Electronic Arts\Need For Speed High Stakes -> set "Thrash Driver" to "d3d" 8. Copy d3da.dll (92.0KB) from "C:/Program Files/Electronic Arts/Need For Speed High Stakes/3dSetup" to "C:/Program Files/Electronic Arts/Need For Speed High Stakes" 9. wine nfshs.exe
It works on Wine 1.1.26 and not in 1.1.35
http://bugs.winehq.org/show_bug.cgi?id=21163
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|NFS4: Fails to start |NFS4: Fails to start if | |Hardware Acceleration is | |enabled
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #4 from Wylda wylda@volny.cz 2010-01-02 17:17:41 ---
Based on Lukasz's steps to reproduce - confirming. Revert of 377cda97e75588afd8bc4af0a126ae9f8ea2a6a8 after git checkout makes that problem go away.
It seems to me overcomplicated and based on old/unavailable game. So if we want to gain some of Henri's time we need to simplify this bug report. We are lucky, because demo has the same problem.
1. Install under Win 98
2. Under WinXP run 3DSetup.exe -> choose Software Renderer (needs run 2x ??)
3. regedit -> HKEY_LOCAL_MACHINE\Software\Electronic Arts\Need For Speed High Stakes -> set "Thrash Driver" to "d3d"
4. Run NFS 4 Demo either under Win98 or WinXP
--private keyword: bisected
Consider UNCONFIRMED->NEW, and KEYWORDS: +DOWNLOAD. Download link: http://www.gamershell.com/download_4365.shtml
http://bugs.winehq.org/show_bug.cgi?id=21163
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.gamershell.com/d | |ownload_4365.shtml
http://bugs.winehq.org/show_bug.cgi?id=21163
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #5 from Austin English austinenglish@gmail.com 2010-01-02 20:15:41 --- Confirming.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #6 from Wylda wylda@volny.cz 2010-01-05 16:26:44 ---
Still not fixed in wine-1.1.35-439-g2f529c3.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #7 from NSLW lukasz.wojnilowicz@gmail.com 2010-01-06 03:01:38 --- (In reply to comment #6)
Still not fixed in wine-1.1.35-439-g2f529c3.
Confirming.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #8 from NSLW lukasz.wojnilowicz@gmail.com 2010-01-10 04:52:46 --- Still not fixed in wine-1.1.36.
http://bugs.winehq.org/show_bug.cgi?id=21163
Alexey Loukianov mooroon2@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mooroon2@mail.ru
--- Comment #9 from Alexey Loukianov mooroon2@mail.ru 2010-03-22 06:02:47 --- Confirming: still not fixed in 1.1.39, going to test with 1.1.40 as soon as there would be some spare time to compile it.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #10 from Alexey Loukianov mooroon2@mail.ru 2010-03-28 05:18:28 --- Tested with Wine 1.1.40 & 1.1.41: a) In case I run the game using "wine nfshs.exe", I've got "Locked by thread XX (delaying by 60s)" like messages. b) In case I set the cpu affinity for the process using for ex. "taskset -c 1 wine nfshs.exe" the game runs using Direct 3D, but there are a lot of following lines appear at console:
err:d3d_surface:surface_prepare_system_memory Surface without memory or pbo has SFLAG_INSYSMEM set! err:d3d_surface:surface_prepare_system_memory Surface without memory or pbo has SFLAG_INSYSMEM set! err:d3d_surface:surface_prepare_system_memory Surface without memory or pbo has SFLAG_INSYSMEM set!
c) There are a lot of render errors in the game menus. Need to say that the glitches are just the same as they were with older versions of wine (back on to 1.1.19 times).
So, generally speaking, with 1.1.40 the situation got better than it was with versions from 1.1.27 till 1.1.39, but the render glitches at the game menus and overall slow ingame performance with d3d render still make NFS4:HS unplayable with Direct3D hardware rendering under Wine.
P.S. There are some other versions of the direct3d game driver supplied with an unofficial patch (NFS_HS_SP_Setup_V3.0_beta_1.63), but none of them works correctly with Wine. Most close to success is the so-called "Direct3D 8" d3da.dll: the game starts normally with this driver, but the rendered picture gets almost totally messed up.
http://bugs.winehq.org/show_bug.cgi?id=21163
NSLW lukasz.wojnilowicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #11 from NSLW lukasz.wojnilowicz@gmail.com 2010-11-11 11:46:17 CST --- Fixed in wine-1.3.6-379-g1309731
http://bugs.winehq.org/show_bug.cgi?id=21163
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Alexandre Julliard julliard@winehq.org 2010-11-12 13:33:43 CST --- Closing bugs fixed in 1.3.7.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #13 from Alexey Loukianov mooroon2@mail.ru 2010-11-12 18:58:07 CST --- (In reply to comment #12)
Closing bugs fixed in 1.3.7.
Isn't working on my workstation with wine freshly built wine 1.3.7.
Logs get populated with:
err:ntdll:RtlpWaitForCriticalSection section 0x68cd8580 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 001b, blocked by 0009, retrying (60 sec) err:mmtime:TIME_MMTimeStop Timer still active?! err:ntdll:RtlpWaitForCriticalSection section 0x68ac6c70 "winmm.c: WINMM_cs" wait timed out in thread 001d, blocked by 0000, retrying (60 sec ) err:ntdll:RtlpWaitForCriticalSection section 0x688c5e4c "main.c: ddraw_cs" wait timed out in thread 001e, blocked by 0009, retrying (60 sec)
in case original d3da.dll is used. Trying to use newer d3da.dll shipped with unofficial patch allows game to start but without any graphical output (i.e. screen remains black, while I can hear sounds coming from GUI - music, ticks-n-clicks when navigating menus, e.t.c.). Wylda, are there any steps you took in order to made the game work with D3d?
P.S. Tried set CPU affinity to use only one core of my Phenom II x4, but the problem persisted.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #14 from NSLW lukasz.wojnilowicz@gmail.com 2010-11-13 04:40:16 CST --- (In reply to comment #13)
(In reply to comment #12)
Closing bugs fixed in 1.3.7.
Isn't working on my workstation with wine freshly built wine 1.3.7.
There is a new regression somewhere between wine-1.3.6-379-g1309731 and wine-1.3.6-421-gc138970 which causes the crash.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #15 from NSLW lukasz.wojnilowicz@gmail.com 2010-11-13 05:31:03 CST --- The regression is reported as Bug #25144.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #16 from Alexey Loukianov mooroon2@mail.ru 2010-11-13 09:21:16 CST ---
There is a new regression somewhere between wine-1.3.6-379-g1309731 and wine-1.3.6-421-gc138970 which causes the crash. The regression is reported as Bug #25144.
Is the regression expected to be a crash? I don't have a crash here, the game locks up waiting for something just like it was with earlier versions of wine (i.e., "err:ntdll:RtlpWaitForCriticalSection section ... (60 sec)" appears in logs and nothing else happens) so it looks like nothing had changed in wine-1.3.7 in regard to this bug (at least on my workstation).
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #17 from NSLW lukasz.wojnilowicz@gmail.com 2010-11-13 11:10:23 CST --- (In reply to comment #16)
Is the regression expected to be a crash? I don't have a crash here, the game locks up waiting for something just like it was with earlier versions of wine
I get Wine error window and then the game locks up. I assure you that between 1.3.6 and 1.3.7 the game worked. I use wine-1.3.6-404-g78abb8a to play the game.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #18 from Alexey Loukianov mooroon2@mail.ru 2010-11-13 15:06:49 CST --- (In reply to comment #17)
I get Wine error window and then the game locks up. I assure you that between 1.3.6 and 1.3.7 the game worked. I use wine-1.3.6-404-g78abb8a to play the game.
Would you be so kind and provide me a link to download source tar.bz2 (tar.lzma/tar.gz) snapshot with wine-1.3.6-404-g78abb8a? I'm in process of migrating from Fedora 8 i686 to Fedora 13 x86-64 and messing with installing git in Fedora 8 would be a useless waste of time :-(.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #19 from Alexey Loukianov mooroon2@mail.ru 2010-11-28 16:26:22 CST --- I had finally managed to track down the issue I've been having with NFS4+Direct3D and latest development releases of Wine. I can confirm that with the "stock" wine settings NFS4 runs successfully most of the times when using original DirectX6 d3da.dll renderer (94208 bytes in size). At lest this works with wine version 1.3.8.
The game still refuses to work correctly using newer d3da.dll: freshen version of DirectX6 d3da.dll and High Poly mod of DirectX7 d3da.dll results in game hanging at ntdll:RtlpWaitForCriticalSection; with non "high poly" DirectX7 and DirectX9.0b d3da.dll renderers the game starts but gives no graphics output (black screen), while I can hear music, navigate menus and so on; DirectX8 d3da.dll renderer gives highly-corrupted graphics display.
Now, back to the issue. NFS4 behaviour varies drastically depending on the state of DirectDrawRenderer registry key. In case there's no such key in registry the games starts up fine most of the times and works pretty well (still there are a lot of graphics glitches at the main menu but that's not fatal). In case this registry key exists and is set to "gdi" (this value is mentioned in wine wiki as the default for this key in case it does not exists) then the game refuses to start displaying the messagebox about problems creating d3d surface. In case DirectDrawRenderer key is set to "opengl" the game starts up but stalls just after the start on ntdll:RtlpWaitForCriticalSection.
To the bottom line: the game refuses to work in case the DirectDrawRenderer key exists in the registry with the value set to either "gdi" or "opengl", but start up OK in case there's no such key or the value of the key is invalid (i.e. is not "gdi" nor "opengl").
Should I open another bug report for this? Wylda, NSLW, would you be so kind to try to reproduce this behavior on yours PCs?
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #20 from NSLW lukasz.wojnilowicz@gmail.com 2010-11-29 00:23:05 CST --- (In reply to comment #19)
The game still refuses to work correctly using newer d3da.dll: freshen version of DirectX6 d3da.dll and High Poly mod of DirectX7 d3da.dll results in game hanging at ntdll:RtlpWaitForCriticalSection; with non "high poly" DirectX7 and DirectX9.0b d3da.dll renderers the game starts but gives no graphics output (black screen), while I can hear music, navigate menus and so on;
No. It works fine for me. In fact I use DirectX9.0b renderer. Maybe it's up to graphic card. Mine is NVIDIA 9xxx and driver is 260.19.21
DirectX8 d3da.dll renderer gives highly-corrupted graphics display.
Yes.
Now, back to the issue. NFS4 behaviour varies drastically depending on the state of DirectDrawRenderer registry key. In case there's no such key in registry the games starts up fine most of the times and works pretty well (still there are a lot of graphics glitches at the main menu but that's not fatal). In case this registry key exists and is set to "gdi" (this value is mentioned in wine wiki as the default for this key in case it does not exists) then the game refuses to start displaying the messagebox about problems creating d3d surface. In case DirectDrawRenderer key is set to "opengl" the game starts up but stalls just after the start on ntdll:RtlpWaitForCriticalSection.
To the bottom line: the game refuses to work in case the DirectDrawRenderer key exists in the registry with the value set to either "gdi" or "opengl", but start up OK in case there's no such key or the value of the key is invalid (i.e. is not "gdi" nor "opengl").
I didn't play with these settings because everything was fine.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #21 from Alexey Loukianov mooroon2@mail.ru 2010-11-29 02:16:52 CST --- (In reply to comment #20)
It works fine for me. In fact I use DirectX9.0b renderer. Maybe it's up to graphic card. Mine is NVIDIA 9xxx and driver is 260.19.21
Got pretty the same GPU hardware - nVIDIA GTS250 (which is essentially same as 9800), but an older version of driver - 256.29. Would try to update and check if that helps.
To the bottom line: the game refuses to work in case the DirectDrawRenderer key exists in the registry with the value set to either "gdi" or "opengl", but start up OK in case there's no such key or the value of the key is invalid (i.e. is not "gdi" nor "opengl").
I didn't play with these settings because everything was fine.
Sure. Still it'd be good if you find a minute and test this registry key to cause problems on your PC too. My intention is that if the docs (official wiki) say that the default in case of absence of this key is "gdi" then the game (and wine) should work the same with this key present and set to "gdi" and with this key absent. As this is not true as my test shown then it might be a wrong docs or a bug in wine.
http://bugs.winehq.org/show_bug.cgi?id=21163
--- Comment #22 from NSLW lukasz.wojnilowicz@gmail.com 2010-11-29 02:38:33 CST --- renderer: DirectX7
a) DirectDrawRenderer=gdi game doesn't start
b) DirectDrawRenderer=opengl game starts but is very slooow
c) no DirectDrawRenderer string value no problem
This is very strange behaviour.
http://bugs.winehq.org/show_bug.cgi?id=21163
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |377cda97e75588afd8bc4af0a12 | |6ae9f8ea2a6a8
-
wine-bugs＠winehq.org