Test Drive Unlimited 2 emulation issues

[jenci8888]

Quick summary

Test Drive Unlimited 2 has some problem in emulation accuracy.

Details

• Intro screen freezes and bad performance

The PPU LLVM sometimes stops at intro screen. Recommend PPU Interpreter to past intro screen further.
The intro always stuttering when appears "semaphore" with every frame.

• Start menu screen freezes & FIFO fatal error

Before or after 3D drawn that can have a FIFO fatal error in start menu screen.
And if you close game and window dialog will show up.

Both does not change if I change to try different setting in the config.

Attach a log file

RPCS3.gz

Attach capture files for visual issues

No response

System configuration

OS: Windows 10 21H2 (build number: 19044.1889)
CPU: Intel i5-4690k @ 4.4ghz
GPU: Nvidia GTX 1050Ti, driver version 516.40

Other details

TDU2 used to be ingame long ago, the between 2019-2021 in various RPCS3 builds.

[Danusco]

I currently play TDU2 on RPCS3. And the performance is really bad at least yet. if you follow the following custom emulator settings for this game, it will work better or at least "playable".

*Important: This particular game runs much more stably on the OpenGL Rendering API, although there is FPS loss compared to Vulkan, Vulkan it crashes the game completely at the game's loading screens and CutScenes transitions.

-> But it's really hard, even with OpenGL I'm getting an average of 20-25FPS, with Vulkan I can beat at least 30FPS, despite the game's total crashes. That's considering I'm using an NVIDiA Geforce RTX 3050TI.

my specifications:
CPU: AMD Ryzen 7 5800H Octa-Core 3.2 - 4.4 GHz
GPU: NVIDIA GeForce RTX 3050TI 4GB GDDR6
RAM: 16GB DDR4
Storage: 512GB M.2 NVMe SSD

-> Maybe some game update from the emulator Staff. be able to save this game again in the future. I think we would be very grateful for that.

RPCS3 Settings:
[CPU]
PPU Decoder: LLVM Recompiler
SPU Decoder: Recompiler LLVM
SPU xFloat Accuracy: Approximate xFloat
[GPU]
Res Scale 100%
FSR Upscaling: 80%
Anti-Aliasing: Auto
Zcull Accuracy: Precise
Framelimit: Auto
Shader mode: Async (Multithreaded) ✓
Anisotropic Filter: 16x
Res Scale Threshold: Default
Write Color Buffers: Enabled
[Advanced]
Read Color Buffers: Enabled

Of course, depending on your hardware performance, some settings need to be changed, such as FSR Upscaling, Resolution Scale or Anisotrophic Filter, but the rest is good to keep that way.

Anyway, despite all these bugs in this game, I managed to make the game "playable" at least. Despite running a car game at 20FPS, which is already quite difficult, I managed to get used to the limitations. And about the stuff of the game crashing completely, there's no way, (I repeat with OpenGL this is rarer to happen, with Vulkan it's almost always crashes) you have to be patient and reopen the game again.

[Shoegzer]

@jenci8888: I reported the same issue #10886, and a few years ago @xddxd and I were thinking it was Linux-only, though from your observations apparently it isn't. I've never gotten this title to work, though others obviously have, so it must be related to some host platform-related difference that we haven't fully nailed down. From what you and others have posted though, it might be related to difference in CPU. In other words, all Intel users have reported crashing, and all AMD users reported that it works.

Also, just tested this against #13917 in the off-chance it was related since the symptoms are similar, though crashing still occurs here. In any event I would suggest closing this issue and reporting on the earlier one so we don't clutter up the issue log.