Post by Gamesoul Master on Dec 16, 2008 6:13:04 GMT -5
- pSX v1.13 (multiple BIOS)
- Intel Pentium Dual-Core E2200 @ 2.20 GHz
- ATI Radeon HD 3450 PCI-E (512 MB)
- 3 GB RAM
- Windows XP Pro SP3
I mention Linux because the same exact problem was mentioned here as a Linux-exclusive problem, which it is not. This is most definitely a *pSX* problem. I'm posting this to confirm that fact, and to elaborate a bit on the exact problem from what I can tell.
When you toggle to fullscreen (via Alt+Enter), everything works as intended. However, if you try using Alt+Enter (or Esc if you have it set to exit fullscreen also), pSX instead switches to a pseudo-fullscreen mode, where it *looks* like fullscreen, but is pretty much just pSX in a maximized windowed mode (640x480), and the FPS lag a bit as if I simply took the window and maximized it (my monitor is 1680x1050, so the stretch is quite ugly... lol).
It doesn't *always* do that though. Sometimes if you try to exit fullscreen, you'll go back to seeing a 640x480 window, but that window itself acts like fullscreen (mouse doesn't show up in it and no menu bar). It's a very odd problem, and very annoying that I have to close pSX via the Task Manager whenever it happens.
Another interesting note about the problem is that it's not actually a maximized window effect. I noticed that if I change the fullscreen resolution to something less than my desktop resolution, when I try to exit fullscreen mode, the pseudo-fullscreen is actually a window of the resolution specified in my fullscreen settings (1280x800 made a fullscreen-window that took most of my screen, and 320x240 made a fullscreen-window that looked extremely tiny... lol). Note that all these "windows" are oriented to the upper-left corner of the screen (which probably isn't important, but meh).
The funny thing is that, when I start pSX in fullscreen with the -f switch, this problem doesn't seem to happen at all.
Not sure if I was going anywhere with that -f switch paragraph, but I just realized something. I was playing around with different refresh rates, seeing if they too would try to stick when leaving fullscreen (to see if my graphics card would freeze up trying to figure out how to do a 75 Hz refresh rate in the "window" and 60 Hz for the rest of the desktop... LOL). After nothing bad happened the first try, I turned off fullscreen VSync to see if that would make a difference. Instead of causing some kind of freeze/lock-up, it actually *fixed* the problem.
So what this whole problem actually amounts to is yet another bug with VSync. I guess pSX Author has really bad luck with VSync, eh?
- Intel Pentium Dual-Core E2200 @ 2.20 GHz
- ATI Radeon HD 3450 PCI-E (512 MB)
- 3 GB RAM
- Windows XP Pro SP3
I mention Linux because the same exact problem was mentioned here as a Linux-exclusive problem, which it is not. This is most definitely a *pSX* problem. I'm posting this to confirm that fact, and to elaborate a bit on the exact problem from what I can tell.
When you toggle to fullscreen (via Alt+Enter), everything works as intended. However, if you try using Alt+Enter (or Esc if you have it set to exit fullscreen also), pSX instead switches to a pseudo-fullscreen mode, where it *looks* like fullscreen, but is pretty much just pSX in a maximized windowed mode (640x480), and the FPS lag a bit as if I simply took the window and maximized it (my monitor is 1680x1050, so the stretch is quite ugly... lol).
It doesn't *always* do that though. Sometimes if you try to exit fullscreen, you'll go back to seeing a 640x480 window, but that window itself acts like fullscreen (mouse doesn't show up in it and no menu bar). It's a very odd problem, and very annoying that I have to close pSX via the Task Manager whenever it happens.
Another interesting note about the problem is that it's not actually a maximized window effect. I noticed that if I change the fullscreen resolution to something less than my desktop resolution, when I try to exit fullscreen mode, the pseudo-fullscreen is actually a window of the resolution specified in my fullscreen settings (1280x800 made a fullscreen-window that took most of my screen, and 320x240 made a fullscreen-window that looked extremely tiny... lol). Note that all these "windows" are oriented to the upper-left corner of the screen (which probably isn't important, but meh).
The funny thing is that, when I start pSX in fullscreen with the -f switch, this problem doesn't seem to happen at all.
Not sure if I was going anywhere with that -f switch paragraph, but I just realized something. I was playing around with different refresh rates, seeing if they too would try to stick when leaving fullscreen (to see if my graphics card would freeze up trying to figure out how to do a 75 Hz refresh rate in the "window" and 60 Hz for the rest of the desktop... LOL). After nothing bad happened the first try, I turned off fullscreen VSync to see if that would make a difference. Instead of causing some kind of freeze/lock-up, it actually *fixed* the problem.
So what this whole problem actually amounts to is yet another bug with VSync. I guess pSX Author has really bad luck with VSync, eh?
