Homebrew Retroarch Emulation Thread (Nightly Builds Included)

  • Thread starter Thread starter Stack3r
  • Start date Start date
  • Views Views 1,557,773
  • Replies Replies 7,032
  • Likes Likes 64
good! i've downloaded a game but every time i try to open this game with mame 2000 it says it was faild to start an audio driver... i need some help please ;-;
 
The controls no longer work for me. I only mapped the UDLR buttons to the Circle Pad, and when starting any core, any buttons except the Circle Pad don't work. Even deleting the .cfg files doesn't fix the problem. Anything else I need to do?
 
Last edited by RocketRobz,
good! i've downloaded a game but every time i try to open this game with mame 2000 it says it was faild to start an audio driver... i need some help please ;-;
What game is it? Did you try MAME 2003?

--------------------- MERGED ---------------------------

The controls no longer work for me. I only mapped the UDLR buttons to the Circle Pad, and when starting any core, any buttons except the Circle Pad don't work. Even deleting the .cfg files doesn't fix the problem. Anything else I need to do?
If you did delete the .cfg files and nothing happened try to delete the retroarch folder but first get any bios files you have out of there as well as any saves you want to keep. Then just re download the stable release and put the retroarch folder from it back on the root of your sd card. As far as what stable release to go with, I think 1.3.3 is the best right now as the later releases have a screen tearing problems (I have not tried the latest nightlies so I don't know if that was fixed).
 
Last edited by abelxcane,
If you did delete the .cfg files and nothing happened try to delete the retroarch folder but first get any bios files you have out of there as well as any saves you want to keep. Then just re download the stable release and put the retroarch folder from it back on the root of your sd card. As far as what stable release to go with, I think 1.3.3 is the best right now as the later releases have a screen tearing problems (I have not tried the latest nightlies so I don't know if that was fixed).
Still didn't fix the problem. :(
I'm using the CIA builds.
 
That is strange. If you have an email address and don't mind sharing it I can send you my folder. To see if it fixes the problem.
Found the problem. There was a file called "3DS Controller.cfg" on the SD root. Deleting it fixed the problem.
 
In case this has been missed, people using the mGBA core in Retroarch should really switch to using the official mGBA nightly build instead because LibRetro is NOT kept up to date with the latest mGBA nightly. That, and people should stick with Retroarch 1.3.3 anyway.

Use the mGBA development build from here instead,
https://mgba.io/downloads.html
 
  • Like
Reactions: cvskid
In case this has been missed, people using the mGBA core in Retroarch should really switch to using the official mGBA nightly build instead because LibRetro is NOT kept up to date with the latest mGBA nightly. That, and people should stick with Retroarch 1.3.3 anyway.

Use the mGBA development build from here instead,
https://mgba.io/downloads.html
I would do that if mGBA had the Full screen option.
For some reason, starting from a few builds before 0.4.0 the full screen option for the standalone mGBA is not working, it simply boxes it instead of covering the full screen.

I've been posting constantly with both endrift and LibRetro team, giving feedback but nothing so far.
 
I would do that if mGBA had the Full screen option.
For some reason, starting from a few builds before 0.4.0 the full screen option for the standalone mGBA is not working, it simply boxes it instead of covering the full screen.

I've been posting constantly with both endrift and LibRetro team, giving feedback but nothing so far.

The mGBA standalone is faster than the retroarch core (only on N3ds) because it adds threaded renderer, making it even faster than the vita version.

So I think its fair to give it a shot :)
 
  • Like
Reactions: SLiV3R
I would do that if mGBA had the Full screen option.
For some reason, starting from a few builds before 0.4.0 the full screen option for the standalone mGBA is not working, it simply boxes it instead of covering the full screen.

I've been posting constantly with both endrift and LibRetro team, giving feedback but nothing so far.
That's strange, full screen is working perfectly for me using this .cia build from yesterday.

https://mobile.twitter.com/endrift/status/763116553697005569

Pressing Y switches the modes, including to stretched full screen and AR-obeying full screen.
 
The mGBA standalone is faster than the retroarch core (only on N3ds) because it adds threaded renderer, making it even faster than the vita version.

So I think its fair to give it a shot :)
That's strange, full screen is working perfectly for me using this .cia build from yesterday.

https://mobile.twitter.com/endrift/status/763116553697005569

Pressing Y switches the modes, including to stretched full screen and AR-obeying full screen.
Wait I got confused.
I thought we were talking about the Wii port, not the 3DS port haha, sorry.
I use mGBA through RetroArch on my Wii due to the full screen issue in the standalone build.

As for the 3DS port, how well does it run the games now?
I remember back in 1.3.6 it still had issues with FPS in games like SMA3 and Golden Sun.
Has speed been improved/dynarec been implemented?
 
  • Like
Reactions: cvskid

Site & Scene News

Popular threads in this forum