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.