Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: Dacasks on April 19, 2018, 07:39:14 pm
-
Some bad things happening in my life. One of those is that all of my 15khz monitors "fried". Most of them pissed by some of mine twelve cats.
So I turned into regular, old PC CRT capable of 120hz+ at low resolutions, because they are cheap and I also need a monitor (My Freesync monitor was also a cat pee victim. Life's f'up)
And the results were really good.
Anyway, I noticed that, no matter if used "Super" or "Magic" resolution, and no matter what Frame_Delay setting, I get a really "shocking like" screen tearing, that moves really really slowly as the scroll rolls on.
That happens only when Gmame bumps the refresh rate to circa 120hz in order to use native resolution.
In fact, to get rid of the annoying tearing, What I'm doing is bumping/double the resolution and using a external scanline generator with it. So If I'm playing a game that uses x224... I'm forcing x448 (at say, 60hz), with a scanline generator, and the results are pretty good actually, you couldn't tell a difference from a distance... But unfortunately my scanline generator displays the lines a little bit transparently, so, it's not perfect like using the native resolution anyway.
So I ask: Is that a common behavior with 31khz/pc CRT setups? Thanks in advance.
(I really don't know if it was case of logging, since... it's just... a display "issue", but if needed..)
-
So I ask: Is that a common behavior with 31khz/pc CRT setups? Thanks in advance.
I think it is, yes. I think there was another thread not too long ago that talked about this issue, but i can't find anything beyond your own post about it in March :/
-
Hmmm, I see. Well it's not thaaat annoying actually, and the upscaling approach is okay as well.
Funny thing though, is that by using the 120hz route, no matter what Frame_delay level I toss on it it works full speed, even with FD 9.
I tend to "fast forward" a lot when I game (My shortcut is the "3 kick buttons + "Select" =D ), and the fast forwarding speed is also Sky Rocketed compared to the "60hz" common way (like... ridiculous 1600% in any game).
Besides, going "60hz", I only manage to reach FD 7, just like using a 15khz monitor that way.
I wish I could find a cheap monitor around here to do some of those crappy lag tests of mine (again). It may be placebo, but I feel that using 120hz gives a better input latency, I don't know. Maybe I'm trying unconsciously making it up for it to use that route instead.
-
Hi Dacasks,
GM defaults to triplebuffer when using double refresh rates. Triplebuffer is not compatible with frame delay, that's why it tears. You must force syncrefresh in order to use frame delay. Now, you need to set a high enough frame delay value so in jumps one vblank consistently for each frame. If frame delay is too low, it will run at full speed.
Besides, if your video card is not fast enough you'll have static tearing whith super resolutions and frame delay. Either use vsync offset to compensate for this or, better, use normal dynamic resolutions with double refresh.
-
Hi Dacasks,
GM defaults to triplebuffer when using double refresh rates. Triplebuffer is not compatible with frame delay, that's why it tears. You must force syncrefresh in order to use frame delay. Now, you need to set a high enough frame delay value so in jumps one vblank consistently for each frame. If frame delay is too low, it will run at full speed.
Besides, if your video card is not fast enough you'll have static tearing whith super resolutions and frame delay. Either use vsync offset to compensate for this or, better, use normal dynamic resolutions with double refresh.
Hey Calamity, much thanks for taking the time to answer. GMAME has the best "Customer Service" on the planet =D
hmmm... So, if I understood, it's... only a matter of turning on syncrefresh?
I'm using a R9 380 by the way... so I guess it wouldn't be a problem. And it's not static, anyway.
So I turned on syncrefresh on ini (if that's the case), messed around with some other "sync related" settings as well... but no luck. Still getting those results, and same performance and everything with double refresh. But you know... as for now I got used to it but, if there's a way to prevent that from happening... Or maybe I got it wrong :s
-
Nevermind, got it working *Lil Jon* YEYYYAAHH. Normal behavior, just like using the 15khz monitor (Max of FD 7, no tearing and everything)
but why it only works when I put "syncrefresh 1" per game ini?
put 1 on mame.ini did nothing... weird.
-
but why it only works when I put "syncrefresh 1" per game ini?
That's because -autosync is enabled in mame.ini. Disable it and syncrefresh will behave.
-
but why it only works when I put "syncrefresh 1" per game ini?
That's because -autosync is enabled in mame.ini. Disable it and syncrefresh will behave.
Holy crap, didn't answer/thank you back that after all this time. Much thanks Calamity!