 No.00407
Tafoid Administrator
Mar 25, 2008, 20:40
|
As I understand the command, -refreshspeed is only used when using a video syncing command (-syncrefresh, -triplebuffer, -waitvsync). My tests here (pacman, mrdo, phoenix) show that it does indeed work when using those commands and stays at a solid 100% when not. To me, it makes little sense to slow down emulation to match monitor refresh speed if you are not going to sync it to this lower speed. Ensure you have a syncing command on and use -autoframeskip to alleviate any stutters that might occur. Any other comments? |
|---|---|
 No.00408
Mr_Person Tester
Mar 25, 2008, 20:59
|
Running, say, "vmame64 pacman -refreshspeed -triplebuffer" on 0.123 results in perfectly smooth audio and video. The same command on 0.124a results in audio pops and occasional jerkiness, as if it were still running at 60.6Hz. I didn't bother trying -refreshspeed without a syncing command because I assumed it's intentionally ignored there, as seems to be the case. |
 No.00409
aaronmod Developer
Mar 25, 2008, 21:42
|
I'm not surprised it is broken. The speed parameter is computed before the system is launched, and the way we fetch screen refresh information at that point changed. I don't think we updated the code there. |
 No.00552
aaron Developer
Apr 4, 2008, 13:32
|
Actually, it's broken. I didn't fix it all the way. |
|
No.00553
aaron Developer
Apr 4, 2008, 13:32
|
Ok, now it's fixed for real. |