i don’t think it’s anything that would be visible in a log, unfortunately.
1 Like
Got it, no need for further investigation then, I’ll stick with the non aarc64 from now on.
So, after fiddling a bit more with the settings and trying to figure out what was holding the performance down for no apparent reason, I noticed it’s “Input Block Timeout”. I had to set it to 2 to play SFA3 properly on FBNEO, but I had no clue it would impact performance as it did, as I use to save configs globally, it made Saturn unplayable and fast-forward in any other core almost useless, sometimes barely doubling the game’s native speed.
It just says "Use it if you have issues with simultaneous button presses (Android only).
It doesn’t at all say it will impact performance, so I have to ask, is this side effect expected, or it’s something maybe the devs didn’t know about? I imagine that if I want to play SFAZ3 on the Saturn core, it wouldn’t run full speed as I’d need to activate this feature to use the double button presses to throw, activate custom combos in V-ISM and more.
It’s known behavior, yes. It’s kinda like frame delay in that it pushes the emulation action until later in the frame so the input polling window is longer.
1 Like
Its better to always have core overrides for any options you change. Personally, i even have the main cfg as read only to avoid changing it in any way.
1 Like
Interesting, I’d guess that such impact in performance would be mentioned in the subtext, but at least I now know.
Fair enough, I just thought that since this option would be useful for other systems, I saved it in the main config. Many master system, neo Geo and other systems use double presses, but if I ever need this feature, I’ll save a game override.