I figure some people are still going to be directed to this thread, if that's the case for you, we moved into a new one: https://gbatemp.net/threads/melonds-for-switch-continuation.570021/
It means you need the ds biosim honestly conused by what it means by >> "bios7.bin", bios9.bin", and "firmware.bin".
These are the bios bios files, search with google to find them and use the newest release posted in the catlover thread.im honestly conused by what it means by >> "bios7.bin", bios9.bin", and "firmware.bin".
This guy also says it works. So I am very confused whether it works or not.Hey Guys for people using SXOS, melonDS works perfectly fine on SXOS. I know the devs say it doesn't support SXOS but I have been using it on SXOS for a while now. I don't want misinformation being spread about melondDS not working on SXOS.
To make sure it works on SXOS be sure to have the program NRO2NSP and just convert the NRO file into NSP and then install it on your Switch and you are good to go. Have been playing Pokemon and a few others well on my SXOS Switch.
This guy also says it works. So I am very confused whether it works or not.
developement continued here: https://gbatemp.net/threads/melonds-for-switch-continuation.570021/Is there any was to set the laguage to German or french, when i Play an EU Rom? The default is english.
And.another unrelated question: how is the Performance of the stand alone MelonDS version in comparison to retroarch in Terms of the zelda games?
nothing you can doOn retroarch i use maximum oc. The gameplay is quite fluent with almost stable 60fps. Cutszenes however drop to 40 fps. Is this known, or might my settings be not optimized?
nothing you can do
once I get to finally write an optimised 3d rasteriser, yesok, thank you.
Do you think this might change in the future?
bios files in place?I'm trying to use the libretro core but whenever I attempt to run Chrono Trigger DS atmosphere crashes.
Error code: 2162-0002
Program: 0100000000000012
Firmware: 11.0.1
I'm launching it by holding R for full RAM access. I deleted all my configs incase I changed something which is causing it, but that hasn't fixed anything. The same file launches fine with the DesMuMe core so it isn't the rom itself either.
Any ideas?