Not sure anyone can really answer this but I’m just curious, in general which one emulates it’s system more accurately overall?
why compare cores that emulate different systems?
Just curious how they stack up against each other in general. I think they both have similar goals of performance/accuracy but I’m not sure.
It is indeed an apples-to-oranges comparison, but I guess I would give it to GenPlusGX. However, Genesis/MD is a simpler system to emulate, in general, so that may be a factor.
Snes9x is not too shabby either, it is a High accuracy emulator and can be compared to Bsnes-Balanced.
GPGX and Snes9x are more than good enough for almost all games.
There are some noticeable visual bugs in SNES9x with two high profile games that I’ve come across so far. The worst is this screen “bounce” issue in CT whenever you enter battle. Then there’s the intro of KSS going out of sync with the audio because there’s some slowdown during it. That one’s not too bad since I often skip it anyways. I don’t know of anything like those two in GPGX.
Is that chrono trigger one known by Snes9x devs? It’s on the libretro github. I’d assume so at least it’s a pretty high profile game.
It only happens in the libretro version. It’s actually related to the overscan padding bug I think. If you disable crop overscan it doesn’t happen.
I think it might be fixed in latest Snes9x or at least I don’t notice it with overscan on or off. It sounds like it’s supposed to be pretty jarring but I don’t see it.
DOOM is also problematic in SNES9x, with artifacts on the graphics.
I don’t think it’s nowhere near as accurate/compatible as BSNES balanced like it’s been suggested.
It should be pretty obvious, and I’m using the latest nightly of the core. I made a quick gif of it:
Wow thanks for making the gif, I always like seeing the glitch in action.
k nm i have it too, no idea how i didnt see it jeez
OK after testing it some more, it lookks like for me it only happens if I have crop overscan on AUTO, if it’s set to ON or OFF I don’t see it happening.
The auto setting must be thrown off by the transition somehow.
LOL, I really should have thought to try that. I was assuming auto worked pretty much the same as on. Thanks for testing that; I’ll reply on the github issue with that as a work around.
Edit: Oh, you already did 
I actually just made an account on github for that ha.
I thought I was blind for not noticing it after seeing your gif. I was only testing with off and on at first.