VOGONS


First post, by XJDHDR

User metadata
Rank Newbie
Rank
Newbie

I would like to use this thread to report any problems I'm having getting Need for Speed: Porsche 2000 working with dgVoodoo. I'm trying to run the game on Windows 10 x64. If needed, you can download the NFS5: Porsche 2000 demo from here: https://archive.org/details/NeedForSpeedPorscheUnleashedDemo

Currently, I am having two problems with the game. The first is a regression. dgVoodoo v2.55 and 2.55.1 caused left mouse clicks to not register in the game's menu. v2.54 did not have this problem. To try explain what is going on, after I installed v2.55, the game did not register when I clicked on items in the game's menu if I simply click the mouse button without moving the mouse. The game only registers a click if I move the mouse while holding the left mouse button down. The click will then be registered wherever the mouse is pointing when I release the mouse button. v2.54 did not have this problem; the click was registered regardless of whether or not I moved the mouse after I press the LMB. The demo linked above demonstrates this same problem if you want to test.

The second problem I'm having is random crashes during loading screens. dgVoodoo is definitely helping in this regard as I think I've noticed less crashes with dgVoodoo installed than without. I am still having crashes in some areas though. I'll try to get more info the next time I get a reproducable crash.

I've attached the Voodoo config file I'm currently using.

Attachments

  • Filename
    dgVoodoo.conf
    File size
    10.79 KiB
    Downloads
    216 downloads
    File license
    Fair use/fair dealing exception
Last edited by XJDHDR on 2020-08-20, 07:26. Edited 1 time in total.

My creations and essays:
https://xjdhdr.gitlab.io/

Reply 1 of 37, by BMickey

User metadata
Rank Newbie
Rank
Newbie

I'm confirming your click-problem issue on Win7 x64, it's just the same. I remember 2.54 behaved identically, but I will try again later.
I also have another problems here, e.g. do you have any problems with game menu? I have major slowdown in the menu, not usable at all. And I remember entering gameplay also resulted in some crashes (info for those not familiar with the game - it has 2 modes: menu 640x480 16bit and normal racing mode with resolution/color depth set by user).
In general I'm not using dgVoodoo2 for NFS5 (I tried many times) due to too many issues - for NFS5 I'm using another amazing tool DxWnd (https://sourceforge.net/projects/dxwnd/), thanks to ghotik.

Reply 2 of 37, by XJDHDR

User metadata
Rank Newbie
Rank
Newbie

I somehow missed the release of dgVoodoo v2.55.2. Unfortunately, that version still has the same left click bug I mentioned in my first post.

Also, I can confirm that dgVoodoo is definitely helping with crashes. Without dgVoodoo installed, the game locks up at the start of the loading screen as soon as I try to enter a race. With dgVoodoo, the race loads up. I haven't managed to find a reproducible crash yet with dgVoodoo installed but I'll report back once I do.

Edit: I keep forgetting to mention my system's specs. Here they are:
Windows 10 Pro 1703 x64
AMD Ryzen 5 1600
Nvidia GeForce 1080 Ti
32GB DDR4

BMickey wrote:

I'm confirming your click-problem issue on Win7 x64, it's just the same. I remember 2.54 behaved identically, but I will try again later.
I also have another problems here, e.g. do you have any problems with game menu? I have major slowdown in the menu, not usable at all.

Now that you mention it, I do have performance issues in the game menu. It's not unusable though but then again, I do have a powerful PC so that may be helping. I think it's mainly when I'm pointing at buttons or things that I can click on. The worst offender is the volume sliders; the menu slows to a crawl while I'm dragging one of them.

Also, did you manage to re-test with 2.54? I just re-tested to make sure and 2.54 is definitely the last version that doesn't have that left click problem I mentioned.

BMickey wrote:

And I remember entering gameplay also resulted in some crashes (info for those not familiar with the game - it has 2 modes: menu 640x480 16bit and normal racing mode with resolution/color depth set by user).

Thanks for providing that extra info. I have been having those same crashes. As I mentioned in my first post, they occur constantly without dgVoodoo whereas they don't without it. I'm currently playing through the Test Driver storyline to try get a reproducible crash with dgVoodoo installed. I remember that the first mission that takes place on Zone Industriale crashes during the loading screen even with dgVoodoo installed with my last save.

BMickey wrote:

In general I'm not using dgVoodoo2 for NFS5 (I tried many times) due to too many issues - for NFS5 I'm using another amazing tool DxWnd (https://sourceforge.net/projects/dxwnd/), thanks to ghotik.

Would you be able to tell me what settings you are using? I tried using DxWnd's default profile for NFS5 but it did not work at all. It would not even put the game in Windowed mode, even when running DxWnd with Admin privileges.

My creations and essays:
https://xjdhdr.gitlab.io/

Reply 3 of 37, by BMickey

User metadata
Rank Newbie
Rank
Newbie
XJDHDR wrote:

Would you be able to tell me what settings you are using? I tried using DxWnd's default profile for NFS5 but it did not work at all. It would not even put the game in Windowed mode, even when running DxWnd with Admin privileges.

I use DxWnd for compatibility, not window mode. (Some old games won't run on 4GB VRAM cards, because old DirectX thinks 0MB VRAM is installed).
Here is my DXW file (change txt file extension to dxw and import into DxWnd, then adjust paths):

Filename
Need for Speed™ Porsche® 2000.txt
File size
8.99 KiB
Downloads
190 downloads
File license
Fair use/fair dealing exception

Reply 4 of 37, by ggms

User metadata
Rank Newbie
Rank
Newbie

I can confirm unresponsive menu problem in this game also... Just to mention that you can solve this game not reporting all resolutions (or not reporting resolutions at all) with ExtraEnumeratedResolutions and DefaultEnumeratedResolutions=classics combination...

Edit: also to confirm that unresponsive menu problem is NOT present with 2.54 and before (but ALL 2.55+ versions have this serious problem, makes menu unusable)

Reply 5 of 37, by XJDHDR

User metadata
Rank Newbie
Rank
Newbie

There is one detail I keep forgetting to mention: the rendering API the game uses.
The game can use either Direct3D 7 or Glide 2 to render the game. From what I've read, other Need for Speed titles released around that time period have the same feature.
Edit: As I noted in a later post, NFS5 seems to be using the Glide 3 API rather than Glide 2.

BMickey wrote:

I use DxWnd for compatibility, not window mode. (Some old games won't run on 4GB VRAM cards, because old DirectX thinks 0MB VRAM is installed).

I see. Unfortunately, I could not get your DxWnd config to work. My game still crashes when I try to start a race even with DxWnd running in the background and I get an error when I try to run the game through DxWnd. Maybe I'm doing something wrong but it just doesn't want to work for me. That said, one of the reasons I'm using dgVoodoo is to get a windowed mode so if DxWnd can't do this for me, it's a dealbreaker.

ggms wrote:

I can confirm unresponsive menu problem in this game also... Just to mention that you can solve this game not reporting all resolutions (or not reporting resolutions at all) with ExtraEnumeratedResolutions and DefaultEnumeratedResolutions=classics combination...

I solved this problem by adding the line EnumeratedResolutionBitdepths = 32 to my config. Limiting the reported resolutions to those that support 32-bit colours was enough to make my game report all resolutions.

Last edited by XJDHDR on 2018-08-18, 17:32. Edited 1 time in total.

My creations and essays:
https://xjdhdr.gitlab.io/

Reply 6 of 37, by ggms

User metadata
Rank Newbie
Rank
Newbie

Just to mention that nothing is changed with dgVoodoo 2.55.3 regarding this - game is UNPLAYABLE with 2.55.x version because you can't click anywhere on menu. Mouse jumps from one side of screen to another, skips, shutters, clicking is not registered. Switching to 2.54 works like charm but that version lacks. INI support so I can't use any ExtraEnumeratedResolutions or something like that trick to enable all resolutions (without that game will stop enumerating resolutions at one point). Can we get 2.54 version with .ini config support 😊 ?

P.S. Tried changing nVidia drivers, pulling out controllers, switching monitor to 60Hz one (my current monitor is Eizo with 120MHz support)..nothing works for 2.55.x...I can post video if needed but I think "massive mouse shutter and unable to click anywhere in menu" is good enough...

Reply 7 of 37, by kjliew

User metadata
Rank Oldbie
Rank
Oldbie

I downloaded the demo to give it shot with QEMU 3Dfx glide pass-though. It worked out pretty OK with dgVoodoo2 on Windows 10 Pro x64, I would say, after keeping the graphics details low. I am typically not a racing games fan, so I don't have special car wheel and pedals type controls to make it more realistic. No sure if QEMU USB pass-through would handle such device well. It's a glide3x game in year 2000, so the game level of details would typically target CPU in the class of Pentium3 or Athlon that is out of reach from QEMU or any x86 emulation known today.

Reply 8 of 37, by Dege

User metadata
Rank l33t
Rank
l33t

The Glide version works fine.

I could reproduce the jerky mouse with the D3D version and found a minor bug in the mouse emulation. Plz try the attached version. It works really smooth for me now. If it's ok then I'll re-release 2.55.3.
http://dege.fw.hu/temp/dgVoodoo2_55_3_mousefix.zip

I think it cures other games absorbing mouse clicks. The only thing I don't understand why it was not (so sensible) problem with 2.54.

Reply 9 of 37, by XJDHDR

User metadata
Rank Newbie
Rank
Newbie
Dege wrote:
The Glide version works fine. […]
Show full quote

The Glide version works fine.

I could reproduce the jerky mouse with the D3D version and found a minor bug in the mouse emulation. Plz try the attached version. It works really smooth for me now. If it's ok then I'll re-release 2.55.3.
http://dege.fw.hu/temp/dgVoodoo2_55_3_mousefix.zip

I think it cures other games absorbing mouse clicks. The only thing I don't understand why it was not (so sensible) problem with 2.54.

I forgot to mention that most of my testing has been with the D3D API rather than Glide.

I just tested your mousefix version and that has fixed the mouse problems I was having. I think the performance problems in the main menu that I mentioned in my second post also seem to have been solved. Especially the volume sliders problem I mentioned is now fixed and I can drag those sliders without performance issues.

Edit: The mouse problem may have been (more?) situational before v2.55 as BMickey mentioned having this mouse problem in v2.54 as well as 2.55.

Edit 2: Thank you for fixing this problem.

Last edited by XJDHDR on 2018-08-08, 06:30. Edited 1 time in total.

My creations and essays:
https://xjdhdr.gitlab.io/

Reply 10 of 37, by ggms

User metadata
Rank Newbie
Rank
Newbie
Dege wrote:
The Glide version works fine. […]
Show full quote

The Glide version works fine.

I could reproduce the jerky mouse with the D3D version and found a minor bug in the mouse emulation. Plz try the attached version. It works really smooth for me now. If it's ok then I'll re-release 2.55.3.
http://dege.fw.hu/temp/dgVoodoo2_55_3_mousefix.zip

I think it cures other games absorbing mouse clicks. The only thing I don't understand why it was not (so sensible) problem with 2.54.

Works like a charm now, problem fixed, thank you Dege!

Reply 12 of 37, by BMickey

User metadata
Rank Newbie
Rank
Newbie

Works for me too, finally NFS 5 main menu in 1920x1440x32 glory, not original 640x480x16 instead, thanks Dege.

XJDHDR wrote:

Edit: The mouse problem may have been (more?) situational before v2.55 as BMickey mentioned having this mouse problem in v2.54 as well as 2.55.

I've tried to run NFS 5 even with earlier than 2.54 versions, and menu was always unresponsive, just like described in this topic. It was main problem to run NFS 5 with dg for me, now it's over 😀

Reply 16 of 37, by XJDHDR

User metadata
Rank Newbie
Rank
Newbie
pjblew wrote:
pjblew wrote:

Looking forward to trying this with Settlers IV - been missing occasion clicks and releases since shortly after 2.53. Seemed to mainly happen if the mouse was also being moved at the time.

Mouse is now working great in Settlers IV with 2.55.3.

However, I can't get 2.55.3 to pick up any settings from dgVoodoo.conf. I've removed the %APPDATA%\dgVoodoo directory (and all other dgVoodoo.conf files on my system) and recreated it using the control panel, but still no joy. I'm running Settlers IV without any compatibility settings - the same as the control panel. Am I missing something, or is there a bug here?

I don't mean to be rude but I set up this thread to discuss using dgVoodoo with "Need for Speed: Porsche 2000" specifically. If you want to discuss other games or dgVoodoo in general, please can you create your own thread.

My creations and essays:
https://xjdhdr.gitlab.io/

Reply 18 of 37, by XJDHDR

User metadata
Rank Newbie
Rank
Newbie
BMickey wrote:

I've submitted the report in 'dgVoodoo2 for DirectX11' thread. Unfortunately, there is some heavy flickering of headlights rendering.

I just played around with this myself and I'm having the same problem. I've determined that it is caused by this graphics setting:

Graphics options - Headlights.png
Filename
Graphics options - Headlights.png
File size
663.94 KiB
Views
5274 views
File comment
Graphics options - Advanced - headlights
File license
Fair use/fair dealing exception

If the Headlights setting is set to "Projected", the flickering lighting is present. If set to "Vertex", lighting is fine. I also found that whether you use the Glide or DX7 API makes a difference in how this bug shows up but neither of them makes the "Projected" setting flawless.

I captured some videos of this in action.
This is me running the game with "Projected" headlights using the Glide API: https://www.youtube.com/watch?v=PXVlZXZwZlQ
This is me running the game with "Projected" headlights using the DX7 API: https://www.youtube.com/watch?v=_5LwsPLWsbM

When I set the headlights to "Vertex", the problem goes away, as you can see in these two videos:
Glide API: https://www.youtube.com/watch?v=aipH-kiqZIQ
DX7 API: https://www.youtube.com/watch?v=85-vnsw2W7M

I have attached the logs I got from the four runs I did in those videos using DebugView++ and dgVoodoo 2.55.3 Debug layer (the re-released version):

Filename
Porsche Logs.zip
File size
217.61 KiB
Downloads
88 downloads
File license
Fair use/fair dealing exception

Edit: As I noted in a later post, the white textures/overlay on the environment in Glide mode does not appear to be a bug in dgVoodoo but a bug in the original 3DFX hardware. Thus, it seems that the flickering lighting in both Glide and D3D is the dgVoodoo bug.

Last edited by XJDHDR on 2018-08-18, 03:06. Edited 2 times in total.

My creations and essays:
https://xjdhdr.gitlab.io/