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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |