Jittery/Stuttering graphics

barbudreadmon

@Quackwalks Are you using runahead ?

I don't see how a kernel would cause tearing on mame2003+ but not on fbneo ? If anything i would expect the accurate cps2 refresh rate in fbneo (59.63Hz, mame2003+ has it rounded to 60 it seems) to be more of a hassle for that kind of issues ?

Quackwalks

@barbudreadmon I don't have run ahead enabled for mame, but I do for nes, snes, master system, megadrive, gb, gbc, gba, Atari games, turbografix 16, and virtual boy.

barbudreadmon

@Quackwalks said in Jittery/Stuttering graphics:

@barbudreadmon I don't have run ahead enabled for mame, but I do for nes, snes, master system, megadrive, gb, gbc, gba, Atari games, turbografix 16, and virtual boy.

Ok, with mame2003+ runahead support being behind FBNeo's, i thought it might have been a possible cause for the "ghosting" difference.

Maybe your screen refresh rate is a bit below 60Hz ? I guess that could explain why FBNeo has no tearing issues while mame2003+ does ?

Quackwalks

@barbudreadmon I'm using a Samsung smart TV and my HDMI source is set to use pc mode, so I think that changes the type of display standard, or something.... This gsync stuff sounds like it might be the solution but I'll have to test later tonight after work.

quicksilver

I have witnessed this issue in a number of retroarch cores. Doesn't seem to affect any of the standalone emulators (at least from my observations). It's part of the reason I started using redream over flycast. It seems to be especially prevalent when there is a lot of action on the screen or the pi is being pushed hard. The fix that @pjft proposed does work. MY tv is not gsync/freesync capable yet somehow it works. Only issue with that fix is that it seems to add extra overhead. Many N64 games I was running with mupen64plus-next became unplayable with that setting turned on. If anyone uses it I would recommend only using it on a core by core basis.

pjft

@quicksilver Huh, intrigued - thanks for the heads up. I added it to my main retroarch.cfg file, but if you have any other specific cores where it doesn't help because of the overhead I'd love to know!

quicksilver

@pjft I didn't do thorough testing with it (I turned it off after I noticed the issue with N64) but I would be interested to hear yours or anyone elses impressions as well. It might be worthwhile to run some cores with the option turned on and off while running htop to compare and see what's going on behind the scenes.

barbudreadmon

@pjft @quicksilver i recommend disabling all RA video sync stuff for any hardware-accelerated core, it has a tendency to screw performances, actually if you got vsync enabled for flycast it might be part of the performance issue

quicksilver

@barbudreadmon the screen tearing issue is significantly worse then. To the point it makes some games almost unplayable.

pjft

@barbudreadmon said in Jittery/Stuttering graphics:

RA video sync stuff for any hardware-accelerated core, it has a tendency to screw performances, actually if you got vsync enabled for flycast it might be part of the performance issue

Oh my. I might - I actually use flycast for Naomi emulation, where it works awesome, but for Dreamcast I tend to stick to redream .

I'll see if I have vsync turned on, but I don't know what cores would have hardware acceleration.

@quicksilver we have mostly run MAME, FBNeo, Nestopia and Flycast around here, as far as RA cores go, in the last few months on the Pi4. I have had no meaningful issues with the setting on these, but will be on the lookout.

barbudreadmon

@pjft said in Jittery/Stuttering graphics:

I don't know what cores would have hardware acceleration

Any core that produce real 3D through the gpu.

pjft

@barbudreadmon Thanks for the clarification.

Educated guess then:

PCSX Rearmed
Yabasanshiro
Flycast
<the N64 ones>

Uneducated guesses or questions - for others who might know:

I believe MAME does everything on the CPU, even for 3D games, so that wouldn't be one.
Where does FB Neo stand in that regard?
Sega 32X cores? And is it at the core level, or would it be per-game (meaning, would 2D games not be affected)?

Sorry - video pipelines are not my expertise.

barbudreadmon

@pjft said in Jittery/Stuttering graphics:

PCSX Rearmed

Nope, that one is software-rendered. FBNeo, MAME and picodrive (32X core) too.

Quackwalks

@quicksilver I'm trying to find what I need to type in my retroarch.cfg to enable gsync but can't find anything. Could you help? Also, how do you Eggheads figure out exactly what needs to be typed?

pjft

@Quackwalks it should be

vrr_runloop_enable = "true"

if I recall correctly. I ended up reading the code on GitHub and digging into it from the initial commit.

Quackwalks

@pjft Thank you.

Clyde

@pjft said in Jittery/Stuttering graphics:

EDIT: and to be clear, my monitor is also not GSync compatible,

I think I found the solution for this "riddle". The option isn't actually only GSync, but at least GSync and FreeSync (and maybe other similar techniques? Are there any more?)

According to this comment from a contributor to an RA issue, "Sync exact framerate only works with g-sync/freesync displays." The Emulation General Wiki also sounds like, while MAME and RA do "make use of this functionality", they only do so on compatible monitors.

So the question is, does anyone who experiences an improvement by this option has a screen with such a functionality he/she don't know about, or does this option actually do more than its describtions says, or is it just an confirmation bias / placebo effect?

That said, the corresponding config line vrr_runloop_enable doesn't sound anything like the option in the RGUI/XMB or its description. Does anyone know what a "VRR Runloop" actually is?

Sorry for the subsidiary topic, but I think it may be helpful for understanding which options may (or actually can) help against tearing or stuttering and if so, in which circumstances.

dankcushions

the pi models do not support g sync/free sync.

quicksilver

@Clyde said in Jittery/Stuttering graphics:

@pjft said in Jittery/Stuttering graphics:

EDIT: and to be clear, my monitor is also not GSync compatible,

I think I found the solution for this "riddle". The option isn't actually only GSync, but at least GSync and FreeSync (and maybe other similar techniques? Are there any more?)

According to this comment from a contributor to an RA issue, "Sync exact framerate only works with g-sync/freesync displays." The Emulation General Wiki also sounds like, while MAME and RA do "make use of this functionality", they only do so on compatible monitors.

So the question is, does anyone who experiences an improvement by this option has a screen with such a functionality he/she don't know about, or does this option actually do more than its describtions says, or is it just an confirmation bias / placebo effect?

That said, the corresponding config line vrr_runloop_enable doesn't sound anything like the option in the RGUI/XMB or its description. Does anyone know what a "VRR Runloop" actually is?

Sorry for the subsidiary topic, but I think it may be helpful for understanding which options may (or actually can) help against tearing or stuttering and if so, in which circumstances.

My tv 100% does not have free/g sync capabilities. I have a Vizio TV and it was not introduced as a feature on Vizio TVs until a year after I got my tv. I can confirm that vrr_runloop_enable does turn on/off the setting in question. You can enable it in the retroarch core options config and then when in game check the retroarch menu and you'll see the setting has been enabled. Before redream was added as an optional emulator I was using flycast and the screen tearing/jitter issue was so prevalent
on the pi 4 that it made me almost stop using that core altogether. However I found that by enabling that setting it was no longer a problem. If you look back through the "working dreamcast games" thread you can see my previous discussion about it. I'd gladly provide my tv model/specs and a video of before and after it would help convince anyone.

pjft

@Clyde Info on the option:

https://github.com/libretro/RetroArch/pull/7019 and https://github.com/libretro/RetroArch/pull/7042