[Bug 21163] NFS4: Fails to start if Hardware Acceleration is enabled

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=21163

--- Comment #19 from Alexey Loukianov <mooroon2 at 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?

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.