03-10-2024, 11:02 PM
Hi, hopefully I'm posting correctly. Lately I've come across an issue where regardless of my settings, game, or configurations I cannot make the turbo or fast-forward buttons work as intended (default binds: F4 and period, respectively). I've never had an issue with these before and never had I touched them, not even their bindings, but now it seems that they don't work anymore.
I first noticed this in Tokyo Xtreme Racer 3, but since I had patched it recently to fix the end-game wanderer problem, I thought that maybe the patch did it. Thankfully I had a backup of the original game. Tried it again, and what would you know, the same problem occurred.
At first I figured I just downloaded a nightly build that just came with the bug. No biggie, I just reinstalled the emulator with a version that I knew worked before, but now the same problem occurs, which I thought was interesting (my pcsx2 is always installed under Documents, never have I had a problem with it there).
The next step was to open logs and just tinker with the settings a lot. I noticed something interesting here in the logs that happened when I tapped the F4 or the period keys to turbo (first image):
A ton of 'Vsync is OFF' messages.
I did some digging on my own and found some old thread in the forums that also had a Vsync issue, but their problem was that it intermittently changed between 'Vsync is ON' and 'Vsync is OFF'. So it seems I may not have the same problem.
I went into Nvidia's control panel, found pcsx2, and forced Vsync on from there (and I also did it from the graphics options per game, forced it on with the check mark). Now, the log didn't show this anymore, but I had another issue entirely which was even more strange and seems undocumented from what I was able to find - whenever I touched F4 or period, the game would actually slow down for a moment.
That was incredibly weird and behavior I'd never seen anywhere in years of using the emulator, frankly. Plus, if I tapped F4 or period fast enough, I could simulate a large (almost 50% from 60fps to 30fps) slowdown into the game. And what's more perplexing is that the actual slow-down function (default binding Shift+Backtab) works just fine!
Can anyone help out with this issue? I've also attached my log as a text file.
I first noticed this in Tokyo Xtreme Racer 3, but since I had patched it recently to fix the end-game wanderer problem, I thought that maybe the patch did it. Thankfully I had a backup of the original game. Tried it again, and what would you know, the same problem occurred.
At first I figured I just downloaded a nightly build that just came with the bug. No biggie, I just reinstalled the emulator with a version that I knew worked before, but now the same problem occurs, which I thought was interesting (my pcsx2 is always installed under Documents, never have I had a problem with it there).
The next step was to open logs and just tinker with the settings a lot. I noticed something interesting here in the logs that happened when I tapped the F4 or the period keys to turbo (first image):
A ton of 'Vsync is OFF' messages.
I did some digging on my own and found some old thread in the forums that also had a Vsync issue, but their problem was that it intermittently changed between 'Vsync is ON' and 'Vsync is OFF'. So it seems I may not have the same problem.
I went into Nvidia's control panel, found pcsx2, and forced Vsync on from there (and I also did it from the graphics options per game, forced it on with the check mark). Now, the log didn't show this anymore, but I had another issue entirely which was even more strange and seems undocumented from what I was able to find - whenever I touched F4 or period, the game would actually slow down for a moment.
That was incredibly weird and behavior I'd never seen anywhere in years of using the emulator, frankly. Plus, if I tapped F4 or period fast enough, I could simulate a large (almost 50% from 60fps to 30fps) slowdown into the game. And what's more perplexing is that the actual slow-down function (default binding Shift+Backtab) works just fine!
Can anyone help out with this issue? I've also attached my log as a text file.
