Ridge Racer 7 3D [NPUB30457]

My conclusion is that this game has desync problems for low end PCs, you need a beefy PC to run the game without issues, maybe one with 4 cores minimum, but 6 cores is better.

I can go ingame, but have the same issues Emogop mentions on my dual core E5700, the game freezes after a couple of minutes of play. This happens on all versions of the game, both US and European versions.

I can play other not demanding games at decent speeds.

The most common issue I have is "RSX: FIFO error: possible desync event (last cmd = 0x2062000)" and the debug panel asks me to increase the Driver Wake-Up Delay, but no matter what number I use for the Wake-Up Delay, I cannot fix the issue.

Using an ISO instead of a pkg game doesn´t fix the issue either.

So devs should say the game is playable only for lucky people who can afford a six core PC, not for the rest of us.

---

I've got an issue with my game here. I downloaded Ridge Racer 7 3D NPUB3045 on my computer. I can get in-game but the game freezes either at the menu screen, or when i'm starting a race. I've noticed that if i can get in a race, the fps drops to 10, and there's tremendous lag and i can only go this far. It's either freezing at menu screen or freezing when i'm about to start a race. Is it the game's problem or my hardware's problem, cause my hardware isn't very good either.

Intel core i5 7200u
Nvidia Geforce 920MX
8GB RAM
1TB HDD

The game's definitely NOT playable.  At least not for all of us.
I may have a slightly better CPU i3 6100 @ 4,5 Ghz but it can run the game at 60 fps and still I got this message:

Code:

E {RSX [0x0cc1b10]} RSX: nv406e::semaphore_acquire has timed out. semaphore_address=0x40300800

Or even this:

Code:

E {RSX [0x0cdead0]} RSX: FIFO error: possible desync event (last cmd = 0x2062000) x21
F {RSX [0x0cdead0]} SIG: Thread terminated due to fatal error: Dead FIFO commands queue state has been detected!
Try increasing "Driver Wake-Up Delay" setting in Advanced settings.
(in file d:\a\1\s\rpcs3\Emu\RSX\RSXThread.cpp:2318)

And it's not even that CPU demanding.
And no, setting Driver Wake-Up Delay other than 0 or 1 resulting in black screen at the launch.
So it's INGAME for now.

I totally agree with you, have exactly the same issues on dual core PC.