![]() ![]() ![]() Navigate to Catalyst Control Center -> Gaming -> 3D Application Settings -> All -> Wait for vertical refresh -> Change the slider to Quality to set V-sync to Always On Navigate to Radeon Settings -> Games ->select the game from the list -> Change Wait for vertical synchronization to Always on. Navigate to NVIDIA Control Panel -> 3D Settings -> Manage 3D Settings -> Program Settings -> select the game from the list -> Set VSync to On. To do this, right-click an empty area on your desktop and select: If there is no such setting, try forcing these settings in your graphics card's drivers. If you can find it, either change it to only run for essential services, or add pSX to the list of programs that it should ignore.Check if the game allows you to enable or disable VSync (other possible names are vertical sync, vertical refresh and similar). I have no idea how to access them through Vista (and I doubt it'd really have any impact of this kind on playing, as I'd assume it'd be more like a "work/not work" situation with it), but if it's similar or the same as XP, this is how to do it in XP (interpret as necessary): Control Panel -> System -> Advanced (tab) -> (Performance) Settings -> Data Execution Prevention (tab). Might be useful to check your DEP settings. I suppose trying 60Hz (as much as it may strain your eyes to try =P) might be good to try, just in case.Īlso, I didn't see you make any mention of this, but these messages are occuring in windowed mode, right? Trying a game from an original disc might be worthwhile too, just to see if it's a problem with image-handling somehow. For now, if it plays normally, I'd recommend keeping it at one of those refresh rates and just ignore the error messages until you or one of us can possibly figure out what's causing them.Ĭould you possibly try an older version of pSX, something like v1.6 or something, just to see if the same messages pop up at all. Pretty sure that data execution problem of months ago wouldn't have much to do with it. makes me wonder if the 64-bit set-up has anything to do with it. If I'm supposed to be able to enter fullscreen with 120Hz resolution running for the monitor, go ahead and let me know. I can't enter fullscreen of course (the emulator just freezes and starts sucking up 100% of the processor whenever I try, even at the BIOS intro), but I guess that could be understandable as I look through the list of resolutions for fullscreen and see nothing above 75Hz. Since everything seems fine, is there any risk that it'll cause long-term damage to the monitor, even with everything looking fine now? I'm gonna test pSX now to see if everything still works fine.Įdit: Hmm. So my refresh rate is now at 120Hz with no noticeable problems. And since the monitor is simply detected as a "Plug and Play monitor", I figured it could probably support higher than what Windows was saying. But I decided to try with this LCD monitor I've had for a year or two. And I recall that with my old CRT monitor, picking a refresh rate too high would cause my display to go out of control. ![]() I unchecked the box for not displaying modes the monitor can't support. Have you played this game on a Playstation - if not, what makes you think it plays too fast? However, my PAL copy of Wild Arms (SCES-00321) plays at just the same speed in pSX as it does on my Playstation. ![]() Some games actually play too slowly on the Playstation itself, but play at the correct speed on pSX, leading people to think that it's playing too fast on the emulator because they're used to the way the game plays on the Playstation. If you are using Windows, this suggests you may have a problem with your soundcard, and this may be responsible for the game not synchronising properly. However, it will skip in Linux unless you increase the values for the Latency sliders in Linux. Sound shouldn't be skipping in Windows, particularly with a fast processor. If you think the game is running too fast, you need to disable Frame skipping and enable VSync, unless you have a monitor refresh rate of 100Hz or more (although I think that issue was fixed - so enable VSync anyway. You need to try some other games, as well. We also need to know what version of the emulator you're using and what BIOS - also what OS you're using. We need the game ID for your version of Wild Arms, radikaldreamerx as, apart from there being several different versions of the game, it's required information when making a report or asking for help for a game. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |