Hey thanks for the detailed reply hunterk! I absolutely agree that having choices is ok, especially when they offer differing performance so they can run well across a range of systems.
We support too many platforms, including underpowered jailbroken consoles, outdated PCs and crappy phones, for a one-size-fits-all solution to cover everyone. SNES is the most popular console we support, and it’s my favorite console, as well, so we want to make sure people everywhere have the options they want/need. The various MAME and FBA cores follow the same convention.
BEST SNES9X RETROARCH CORE FULL
Snes9x has gotten slower over time as its accuracy has improved, such that many of the weaker platforms we support can’t run mainline at full speed, so we have older forks that provide more favorable performance thresholds at the cost of accuracy.
BEST SNES9X RETROARCH CORE CODE
The date-stamped forks are snapshots from the year their code is based on. Snes9x with no date is the up-to-date mainline core that has upstream integration (i.e., the “official” snes9x). I agree that this one doesn’t need to be in the online updater but it is, so whatever. Many platforms we support are stuck with super-old compilers that don’t support the whiz-bang latest c++ features that byuu likes to use in bsnes mainline. We would drop the mainline bsnes cores in favor of the very similar “mercury” cores except a vocal segment of bsnes users are either under the erroneous impression that the mercury changes make it less accurate at default settings (you have to explicitly enable 2 core options to switch to the less accurate special chip HLE).īsnes c++98 is a special fork from around v085 that’s been backported to work with older compilers. The mercury cores are almost identical except we added back in the option to use special chip HLE (because, for example, Mega Man X2/3 requires an overclocked i7 to reach full speed with cx4 LLE) and made some small speed optimizations at the expense of code readability (it results in ~10% speedup, IIRC). I would prefer to offer their new “faust” core instead, since it’s at least its own new thing but it also is semi-broken because it’s new and undeveloped.ģx bsnes is self-explanatory.
It’s just there as a side effect of porting/forking mednafen for its other cores.
Something must have happened on your end.īeetle bsnes is a fork of mednafen-snes, which is itself a super-old fork of bsnes (~v060). Probably they all choose Snes 2010 since it has the most recent date.ĭunno what happened with your snes9x-next/2010 core, but we changed the name quite some time ago and never switched back. Is there a practical reason to have this many similar SNES cores? Is there a relatively recent FAQ on how they all differ? It just seems baffling to a veteran of emulation (began with Genecyst and Nesticle back in the 90s), so can imagine newbies just choose one randomly and hope for the best.
BEST SNES9X RETROARCH CORE HOW TO
I can’t even begin to fathom how to choose a BSNES core so I avoid that whole issue by not using any of them. I even checked github and couldn’t really tell) Snes9x (yes, that is all it says! Is it newer, older, faster, slower than the other Snes9x cores? Your guess is as good as mine.Beetle BSNES (I’ve never heard of this before, is it a new fork?).Let me list what is currently in the core updater: On the same note, I’m just completely overwhelmed and confused by the naming and amount of SNES emulators now in Retroarch. And it requires updating our per-core configs repeatedly. A few days ago when I updated cores, Snes9x Next is gone and Snes9x 2010 is back!? Extremely confusing. Then awhile ago that core got switched to be named Snes9x Next, for unknown reasons. So previously I was using Snes9x 2010 core.
0 kommentar(er)
