Retroarch 1.6.9 update slowing emulations down?
-
@psyke83 said in Retroarch 1.6.9 update slowing emulations down?:
Thanks. So the "solution" is to use the default swapchain of 3 for the intensive systems such as SNES. Guides that advocated using a swapchain of 2 were technically correct, but it never made any difference until now.
You could try tweaking other settings (e.g. threaded video rendering) to see if the stutter can be improved with a swapchain of 2, but I'm uncertain if that will put you in a better or worse situation when it comes to input latency.
latency and stutter are two different things. these aggressive latency tweaks can only cause or increase stutter (frame drops) at the possible improvement in input latency. i cover them all here: https://github.com/RetroPie/RetroPie-Setup/wiki/Input-Lag
not that it appears it has dissuaded anyone from using these tweaks :/
-
@dankcushions said in Retroarch 1.6.9 update slowing emulations down?:
@psyke83 said in Retroarch 1.6.9 update slowing emulations down?:
Thanks. So the "solution" is to use the default swapchain of 3 for the intensive systems such as SNES. Guides that advocated using a swapchain of 2 were technically correct, but it never made any difference until now.
You could try tweaking other settings (e.g. threaded video rendering) to see if the stutter can be improved with a swapchain of 2, but I'm uncertain if that will put you in a better or worse situation when it comes to input latency.
latency and stutter are two different things. these aggressive latency tweaks can only cause or increase stutter (frame drops) at the possible improvement in input latency. i cover them all here: https://github.com/RetroPie/RetroPie-Setup/wiki/Input-Lag
not that it appears it has dissuaded anyone from using these tweaks :/
In an ideal world, reducing the swapchain count can theoretically work without introducing stutter. The problem is that the Pi is a low power device and many of the emulators are approaching the CPU/GPU limits.
My suggestion to enable threaded video with a swapchain of 2 is worth checking, since the Pi is quad core, but most emulators' logic runs on a single core. That may eliminate stuttering caused by a lower swapchain setting, but threaded video also increases latency, so the question becomes whether you will get a net benefit of reduced latency vs. a swapchain of 3 and threaded video disabled.
-
@psyke83 i see what you mean, but you should be clear that you mean to turn threaded_video on as typically they're all turning it off (on is the default in retropie). i actually have started making a little automated test suite which could be used to finally dial in what can and can't be handled by a pi: https://github.com/dankcushions/retropie-auto-testing (it's super not finished now), but it would still need a brunnis-style input lag test to see if there's actual benefits in such situations.
-
OK, I edited my post to make it clearer. I was replying to @AndersHP with the assumption that he/she applied all tweaks on the "Input Lag" page (including threaded video set to disabled), so I thought it would be obvious.
-
@andershp I knew it was a config problem. Try the same method for any other emulators causing slowdowns after updating to 1.6.9
-
@darksavior I did and it seems like it worked. My go-to point for latency testing has always been Batrider though, and this surely plays slower (=input laggier) than it did before. But I have not tried updating MAME2003 from source, will do this soon.
Maybe Batrider is generally just a game that's on the limit of the pi.. I tested a bunch of shooters and fighters yesterday and they all seem fine now.
-
@andershp Since batrider runs flawlessly for me, i'd say you still have a config problem. Retropie is already optimized for input lag so anything you modify you're on your own..
As I already said, fba is best with batrider. With the mame2003 binary I got like a .3 fps drop at best, with source like .2-.1 drop in areas where there's a lot happening. If I didn't have the fps counter on then I wouldn't notice.
-
@darksavior How sensitive are you personally to input lag? Because I'm not sure any of my friends would notice. I'm not talking about framerate drops for Batrider after I reset the cfg, but just input lag - this felt better in Retroarch 1.6.7 with threaded video = false and video_frame_delay = 5 , close to no input lag, and with 1.6.9 and no lag reducing settings I would say it feels like 200-300 msecs (no scientific investigation done, just a feeling), and WAY more than e.g. Dodonpachi or Fangun Feveron.
Tested Batrider with both fba and MAME2003 (binary), actually the latter ran better, but that could just be me. I did nothing to reduce input lag in the new cfg file and I do not run emulator-specific cfg files. Both FBA emulator and rom is 0.2.97.42.
Is there any other than the opt/retropie/configs/all/retroarch.cfg that needs resetting...?
-
@andershp said in Retroarch 1.6.9 update slowing emulations down?:
@darksavior How sensitive are you personally to input lag? Because I'm not sure any of my friends would notice.
I don't think I'm very sensitive to input lag. I've adjusted nothing but the tv's game mode (26ms according to rtings), because I did notice input lag without it. I can play mario and other platformers just fine. My tv's pc mode's (44ms) input lag seems fine for pc and console gaming but I really notice it on retropie.
Is there any other than the opt/retropie/configs/all/retroarch.cfg that needs resetting...?
I believe that's all you need to do. As I said, I just uninstall the emulator to empty the folder, then reinstall.
The sensitive people tend to swear by the dispmanx driver, but I don't believe it's supported anymore. I tested it against mike tyson himself, and I didn't notice a difference. I can't use shaders so that's a deal breaker. Maybe the input lag can improve whenever retropie is updated to stretch.
-
@andershp
Deleting the cfg files then reinstalling, (in my case, that included emulator-specific cfg files,) did the trick. You've bailed me out of having to redo everything, thanks. -
@slimy said in Retroarch 1.6.9 update slowing emulations down?:
@andershp
You've bailed me out of having to redo everything, thanks.@slimy forwarding this greeting to @dankcushions and @Darksavior :-)
Have you tried Armed Police Batrider, just for fun? See above correspondence. -
@andershp said in Retroarch 1.6.9 update slowing emulations down?:
@darksavior I did and it seems like it worked. My go-to point for latency testing has always been Batrider though, and this surely plays slower (=input laggier) than it did before. But I have not tried updating MAME2003 from source, will do this soon.
Maybe Batrider is generally just a game that's on the limit of the pi.. I tested a bunch of shooters and fighters yesterday and they all seem fine now.
You really should use FBA for certain Toaplan and Eighting / Raizing games, firstly due to the performance being better and with regards to
some games the Emulation of the sound and music is 100%............I use FBA for all these for the above reasons
Armed Police Batrider
Batsugun
Battle Bakraid
Battle Garrega
Dogyuun
Fire Shark
FixEight
Ghox (Next FBA release will have sound)
Kingdom GP
Knuckle Bash
Out Zone
Rally Bike
Sky Shark
Sorcer Striker
Truxton
V-Five
Vimana
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.