Need for Speed Hot Pursuit 2 (2002) broken rendering and worse fps since 2.5.2

[De-M-oN]

I use d3d8to9 https://github.com/crosire/d3d8to9/releases
otherwise there is no fog in the game.
And the dxvk d3d9.dll

2.5.1 is a bless. The game runs 3-times better fps than dgvoodoo2 DX11 (DX12 a bit faster but crashes at 4k)
Thats some insane magic by dxvk holy moly!
Thanks to this I can finally enjoy custom high poly car models with actual playable fps. Thank you so much!

I'm on Windows 10.

But now its broken with 2.5.2 as you can see at the attached screenshots.
Also the fps got a big impact now.
main menu was before above 1000 fps, now just 450 fps
ingame was before 675 fps, dropped down to 520-ish.

Not sure if the fps drop is due to the broken rendering too, or because of the forced borderless mode now.
It was exclusive before and alt+tab worked perfectly fine. Not sure if it is, but whether exclusive or borderless should be a config option.
The changelog did sound like it is now borderless with no possibility to get exclusive again?

I'm not alone with this broken rendering.
Also people in the Retro Racing Point Discord report the same issue for this game.

Software information

Need for Speed Hot Pursuit 2 (2002)

System information

• GPU: RTX 2080 Ti
• Driver: 561.09 Studio
• Wine version:
• DXVK version: 2.5.2 D3D9

[doitsujin]

Probably the fixed function issue that's already fixed in master. We have 20 issues about that already.

[Blisto91]

Try using this build https://github.com/doitsujin/dxvk/actions/runs/12435734651

[De-M-oN]

fixed the rendering. FPS still that much worse.

Probably Borderless was not the best idea. Or its another problem of the update.
I'd like the borderless thing to be optional tbh

[Blisto91]

Does the FPS improve with this build? https://github.com/doitsujin/dxvk/actions/runs/12453032682

[De-M-oN]

No difference at all.

[K0bin]

At those frame rates and on Windows it might be the exclusive fullscreen change.

[WinterSnowfall]

I use d3d8to9 https://github.com/crosire/d3d8to9/releases otherwise there is no fog in the game.

Just for everyone to be on the same page, we already have an issue open for that: #4113.

As for the performance, I'm not getting any less fps with master than with 2.5.1 on Linux, so it is indeed probably related to the dialog mode change and only affects Windows.

[qinlili23333]

The game runs 3-times better fps than dgvoodoo2 DX11 (DX12 a bit faster but crashes at 4k)

Just a reminder, if in some fixed condition the game works on lower resolution but crash at 4k on Windows or vanilla wine (proton should have LAA force enabled by default since 5.0), there might be a LAA issue.
Check game executable about LAA, and enable it if it's not enabled. Read more about this: https://www.pcgamingwiki.com/wiki/Windows#Set_older_32-bit_games_to_use_4_GB_RAM_instead_of_2

[De-M-oN]

The game works at DGVoodoo's DX11 Output also at 4k. And dxvk is also no problem. Its just dgvoodoo's DX12 Output crashing it. As higher the framerate as earlier it does.
So I think this is rather a dgvoodoo bug.

[qinlili23333]

dgvoodoo requires more memory under DX12. You can trace the commit size of the process before crash with Process Explorer. If commit size keeps increasing and reaches near 2g or 4g before crash, that's 99% due to memory address used up.
If the commit size is very low, this may be a dgvoodoo bug.

[K0bin]

Please keep it on topic, this is the DXVK issue tracker, not the dgvoodoo one.