Post by Gamesoul Master on Jan 8, 2007 19:55:30 GMT -5
Not very often I come across a problem using pSX. I'd like to say from the start here, that it probably has to do with my video drivers, as I have never had this problem before, and it occurs for me in v1.4 to v1.10, and it only happens fully in full screen. Though the other symptoms occur in windowed mode too.
I'm currently using the Omega 2.5.97a Radeon drivers for my Radeon 9250 PCI 256 MB on WinXP Pro SP2. Changing any other relevant settings in pSX has no effect. At first I thought this was a simple fast forwarding glitch of some kind, and then I decided to hit Tab and look at some things. That's when I noticed something odd...
Pic taken while game is involuntarily fast forwarding:
Pic taken while fast forwarding normally (by holding Backspace):
Pic taken while game is running normally:
That last one was a little trouble to get. Because this problem is always occuring, I noticed that the only time the emulator runs "normally" is for a few seconds after doing a manual fast forward. After those few seconds, it goes back to fast forwarding itself. Observe the difference between the first two pics...
This problem occurs with every game I have, playing from any medium, using any BIOS... like I said, I tried everything I could think of to fix the problem, short of changing the video drivers, and nothing had any effect. The only exception is turning off VSync, which fixes the problem for some reason. I'll give more info when I can charge my phone battery. But right now, it's getting rather low and I don't have the spare phone to charge the battery. Figured I'd at least mention it though... give y'all a chance to ponder over it. Not really a big problem for me, since I normally don't use fullscreen (setting the window size up is good enough for me), but I happened to notice this and thought it was worth mentioning.
I guess I forgot to mention, though I had tested it... deleting psx.ini didn't work either. And upon looking, I'd like to add a detail... once I turn off VSync, the "adj=60.00fps[0]" stays at 0... which I assume to mean "disabled" as opposed to 1 meaning "enabled". So basically, the problem here is that leaving VSync on causes frameskipping to silently enable itself after a couple seconds. The configuration window, however, will still say that it's off, and even if I check and uncheck it, then hit Apply, the value still doesn't change unless I either turn off VSync or do a manual fast forward.
Something else that might be worthy of mention... though I didn't catch it in the pics... the skipscore value likes to run up while the frameskip value is being shown as 0... and then it runs back down to 0 once frameskip kicks in. However, this seems to relate to the actual fps, because once in a while, frameskip will reportedly kick in, but the fps will stay at 60.00... and basically, as long as the fps is 60, the skipscore value will go up, regardless of whether frameskipping is reportedly on or off.
For the record, I will probably *not* change my video drivers, as I am very happy with them, and this problem is not enough for me to start mucking up my drivers again. As I said before, I reported this problem more as a "just-so-you-know". I'm not all too concerned about it, especially since nobody else seems to have reported it.
I'm currently using the Omega 2.5.97a Radeon drivers for my Radeon 9250 PCI 256 MB on WinXP Pro SP2. Changing any other relevant settings in pSX has no effect. At first I thought this was a simple fast forwarding glitch of some kind, and then I decided to hit Tab and look at some things. That's when I noticed something odd...
Pic taken while game is involuntarily fast forwarding:
Pic taken while fast forwarding normally (by holding Backspace):
Pic taken while game is running normally:
That last one was a little trouble to get. Because this problem is always occuring, I noticed that the only time the emulator runs "normally" is for a few seconds after doing a manual fast forward. After those few seconds, it goes back to fast forwarding itself. Observe the difference between the first two pics...
This problem occurs with every game I have, playing from any medium, using any BIOS... like I said, I tried everything I could think of to fix the problem, short of changing the video drivers, and nothing had any effect. The only exception is turning off VSync, which fixes the problem for some reason. I'll give more info when I can charge my phone battery. But right now, it's getting rather low and I don't have the spare phone to charge the battery. Figured I'd at least mention it though... give y'all a chance to ponder over it. Not really a big problem for me, since I normally don't use fullscreen (setting the window size up is good enough for me), but I happened to notice this and thought it was worth mentioning.
I guess I forgot to mention, though I had tested it... deleting psx.ini didn't work either. And upon looking, I'd like to add a detail... once I turn off VSync, the "adj=60.00fps[0]" stays at 0... which I assume to mean "disabled" as opposed to 1 meaning "enabled". So basically, the problem here is that leaving VSync on causes frameskipping to silently enable itself after a couple seconds. The configuration window, however, will still say that it's off, and even if I check and uncheck it, then hit Apply, the value still doesn't change unless I either turn off VSync or do a manual fast forward.
Something else that might be worthy of mention... though I didn't catch it in the pics... the skipscore value likes to run up while the frameskip value is being shown as 0... and then it runs back down to 0 once frameskip kicks in. However, this seems to relate to the actual fps, because once in a while, frameskip will reportedly kick in, but the fps will stay at 60.00... and basically, as long as the fps is 60, the skipscore value will go up, regardless of whether frameskipping is reportedly on or off.
For the record, I will probably *not* change my video drivers, as I am very happy with them, and this problem is not enough for me to start mucking up my drivers again. As I said before, I reported this problem more as a "just-so-you-know". I'm not all too concerned about it, especially since nobody else seems to have reported it.