So we made some changes to survive to this new upgrade Hardwareĭoes the internal Pi3/Pi0-w bluetooth work ? The 4.0.0 release was such a huge success that our servers were overwhelmed by the requests. The update is progressively made available to everyone. It's way beyond the release time, and still no update showing, why ? In that case, just change you updates.type to stable in the nf The only ones who can do the upgrade are those who upgraded from 4.0.1/4.0.2 and were on the last unstable we released back in april. people who upgraded from 4.0.x to unstable have better chances to update.some people still have a very early unstable 4.1, you won't be able to upgrade.If you were using an early one, you'll have some silent trouble while upgrading and won't notice it, making the upgrade partial and really buggy We wouldn't recommend you upgrade from an unstable version for MANY reasons : I'm on 4.0.0 (or even before), can I upgrade ? As usual before a major update, we strongly recomment you make a backup of your data Recalbox version before upgrading As you may have some questions before upgrading, let's try to summarize all here ! Feel free to ask questions related to 4.1, we'll eventually update this post to add them. There really seems to be some kind of bug in the rom handling of the libretro-version of fba.As some of you may know already, 4.1 will be released on 13th of October 8pm CET. I also tested the windows version of fba and that one works with non-merged roms.
Now, mame is working correctly with non-merged rom sets, but as it's a very old mame version I would much prefer using the fba-libretro core for all Recalbox arcade game purposes. The reason for using non-merged sets exactly is to eliminate the parent/clone rom set dependencies. But there should only be the need to keep the parent rom when using split roms. Or maglordh will only run if maglord is also present. For example rtypej will only run if rtype is present. The MAME 2003 core in Recalbox works as expected, but the fba-libretro core does not!Įven if you use non-merged sets the parent rom has to be present or else the game will not run and just quit back to Emulation Station. As long as you use non-merged roms sets, a clone version should work without having to have the parent rom set. I only keep rtypej and delete rtype and rtypeu. For example, I would only keep and play the latest japanese revision of a Capcom or Irem game and delete all other versions.
I prefer to use non-merged roms and I only keep one version of a game. Now to the problem I am having: I am a long time MAME user and I know about correct rom auditing, the different possibilites of storing roms (split, merged and non-merged) and parent/clone relationships. First, let me start by saying that Recalbox is awesome!
0 kommentar(er)
