Homebrew Retroarch Emulation Thread (Nightly Builds Included)

[Fatalanus]

I'll be able to provide feedback on the latest build tomorrow on N3DS.

 

[RocketRobz]

@aliaspider is once again bringing the goods!

He added a font driver and menu display driver today for 3DS. What this will mean is that we can use the fancier XMB/MaterialUI menus on the 3DS.

He says that the framerate is 55fps on his Old 3DS, and it's still a bit preliminary/experimental.

BTW, we need as much testing as possible with the current builds. Sticking to some old outdated build is not going to help us fix issues swiftly. So please be understanding of the fact that your testing matters here of the most recent builds.

The latest nightly .7z files are only 12KB.

 

[RupeeClock]

The latest nightly .7z files are only 12KB.

Probably just a build failure. It happens from time to time with any sort of nightlies.
Some newer nightlies from a few minutes ago seem to have built successfully.

 

[LibretroRetroArc]

The latest nightlies are 2016-09-30 -

https://buildbot.libretro.com/nightly/nintendo/3ds/

3dsx version is 13.1MB, CIA is 13.0 MB, complete package is 119MB

 

[DualBladedKirito]

ok the current nightlies cia are bugged. whenever i start a core it shows on the top screen an image of the last homebrew i loaded. in this case FBI. And it is completely unresponsive to any input

 

[RupeeClock]

ok the current nightlies cia are bugged. whenever i start a core it shows on the top screen an image of the last homebrew i loaded. in this case FBI. And it is completely unresponsive to any input

I have the same issue trying Picodrive and GenesisPlus cores, installed via CIA to my 11.1 A9LH/Luma setup on a N3DSXL system.
Does the issue only occur with the CIA builds? Not tested 3DS or 3DSX. What about on O3DS vs N3DS?

 

[kenseiden]

Yeah, the latest CIA nightlies crashing is happening on 2DS/3DS and New 3DS (confirmed on 2DS and N3DS).

 

[44100hz]

Just an update. I decided to make those icons. I'm going off the theme of flat 48x48 vectors of just the buttons for that given system. For the banners, just the emulator's logo plus a retroinvader in the corner. If there's no logo, then just "libretro" with the emulator's name underneath.

I'm about 2/3 done with them, though might redo some. And just for fun: for MAME, what arcade cabinet should I use for 2000? What about 2003?

EDIT: I'm also trying to do alternates that have alternative hardware for each emulator. So look out for that.

 

[RupeeClock]

Just an update. I decided to make those icons. I'm going off the theme of flat 48x48 vectors of just the buttons for that given system. For the banners, just the emulator's logo plus a retroinvader in the corner. If there's no logo, then just "libretro" with the emulator's name underneath.

I'm about 2/3 done with them, though might redo some. And just for fun: for MAME, what arcade cabinet should I use for 2000? What about 2003?

Will each icon/banner have clear differentiation of the cores?
Before, it was really hard to tell apart certain cores without setting the icon size to largest + title.

 

[44100hz]

Will each icon/banner have clear differentiation of the cores?
Before, it was really hard to tell apart certain cores without setting the icon size to largest + title.

Should be clear what's what, even at very small sizes. I made sure of that.

 

[DualBladedKirito]

I have the same issue trying Picodrive and GenesisPlus cores, installed via CIA to my 11.1 A9LH/Luma setup on a N3DSXL system.
Does the issue only occur with the CIA builds? Not tested 3DS or 3DSX. What about on O3DS vs N3DS?

I just tested them only as cia on an n3ds. Results: image of the last app I opened before the core on top screen . With complete input lockup. forcing me to hard reset. The bottom screen stops initializing after it reads: loading history file:sdmc/retroarch/content _history.lpl

 

[LibretroRetroArc]

I just tested them only as cia on an n3ds. Results: image of the last app I opened before the core on top screen . With complete input lockup. forcing me to hard reset. The bottom screen stops initializing after it reads: loading history file:sdmc/retroarch/content _history.lpl

Since when did this start happening?

 

[Jstar269]

I can also confirm this. I installed the PlayStation 1 emulator (PCSX ReARMed) through FBI, and upon opening it, came across a screenshot of my last homebrew loaded up. Rebooting just gave me a fizzy screen and a hard reboot was needed in both cases. Attempted on New 3DS with the 9/30 nightly as a CIA.

Edit: The 9/28 nightly works just fine. The last thing that came up on the bottom screen can be seen below.

RetroArch [INFO] : : Loading history file : [sdmc:/retroarch/content_history.lpl].

 

[kenseiden]

Since when did this start happening?

20160930 nightlies, the very same ones announced a few posts back.

Just an update. I decided to make those icons. I'm going off the theme of flat 48x48 vectors of just the buttons for that given system. For the banners, just the emulator's logo plus a retroinvader in the corner. If there's no logo, then just "libretro" with the emulator's name underneath.

I'm about 2/3 done with them, though might redo some. And just for fun: for MAME, what arcade cabinet should I use for 2000? What about 2003?

EDIT: I'm also trying to do alternates that have alternative hardware for each emulator. So look out for that.

Looking forward to these! For MAME 2000/2003, I think having an arcade cabinet icon would suffice. Maybe use the same icon for both but in different colors for each version, e.g. a red cabinet for 2000 and blue for 2003.

 

[SG6000]

Just an update. I decided to make those icons. I'm going off the theme of flat 48x48 vectors of just the buttons for that given system. For the banners, just the emulator's logo plus a retroinvader in the corner. If there's no logo, then just "libretro" with the emulator's name underneath.

I'm about 2/3 done with them, though might redo some. And just for fun: for MAME, what arcade cabinet should I use for 2000? What about 2003?

EDIT: I'm also trying to do alternates that have alternative hardware for each emulator. So look out for that.

You know what would be really cool but probably a pain in the ass to practically and artistically implement? A couple of sets of 3DS-model-specific banners for the Sega cores that accurately reflect which classic systems they emulate at full speed on that system.

This could be seen as useful because these cores strengths are utilised differently depending on whether they're run on original or new 3DS, with both cores being able to emulate an extra two Sega platforms on N3DS:

O3DS banners could reflect that:
- Picodrive runs Sega Master System and Genesis
- Genesis GX runs SG-1000 and Game Gear

N3DS banners could reflect that:
- Picodrive runs Sega CD and 32X
- Genesis GX runs SG-1000, Sega Master System, Game Gear and Genesis

I have no idea as to whether it's even possible for buildbot to use separate O3DS and N3DS banner (and maybe icon) data for its building of the Picodrive and Gens GX cores, but I personally think it would be a pretty nice touch.

 

[MarkDarkness]

Awesome to see that things are heating up again on this front!

 

[44100hz]

You know what would be really cool but probably a pain in the ass to practically and artistically implement? A couple of sets of 3DS-model-specific banners for the Sega cores that accurately reflect which classic systems they emulate at full speed on that system.

This could be seen as useful because these cores strengths are utilised differently depending on whether they're run on original or new 3DS, with both cores being able to emulate an extra two Sega platforms on N3DS:

O3DS banners could reflect that:
- Picodrive runs Sega Master System and Genesis
- Genesis GX runs SG-1000 and Game Gear

N3DS banners could reflect that:
- Picodrive runs Sega CD and 32X
- Genesis GX runs SG-1000, Sega Master System, Game Gear and Genesis

I have no idea as to whether it's even possible for buildbot to use separate O3DS and N3DS banner (and maybe icon) data for its building of the Picodrive and Gens GX cores, but I personally think it would be a pretty nice touch.

The buildbot creates one set of binaries for both o3ds and new3ds. Interesting idea, though. That also reminds me, maybe I should use a master system pad for Picodrive.

 

[SLiV3R]

@aliaspider is once again bringing the goods!

He added a font driver and menu display driver today for 3DS. What this will mean is that we can use the fancier XMB/MaterialUI menus on the 3DS.

He says that the framerate is 55fps on his Old 3DS, and it's still a bit preliminary/experimental.

BTW, we need as much testing as possible with the current builds. Sticking to some old outdated build is not going to help us fix issues swiftly. So please be understanding of the fact that your testing matters here of the most recent builds.

Yay, sounds awsome


Thanx for continue working on the best and the most important 3ds homebrew!!!

 

[aliaspider]

new builds up with a fix for the cia issue.

for the XMB menu, you need to get the assets from here : https://github.com/libretro/retroarch-assets/archive/master.zip

extract the archive to your assets directory on your SD (which can be set in settings --> directory --> assets). and then change the menu driver to "xmb" (settings --> drivers --> menu driver) and relaunch retroarch.

this is still experimental, so expect slow performance and high loading times.

if anything goes wrong, edit your retroarch.cfg, find the menu_driver="xmb" setting, and change it back to menu_driver="rgui".

 

[kenseiden]

new builds up with a fix for the cia issue.

for the XMB menu, you need to get the assets from here : https://github.com/libretro/retroarch-assets/archive/master.zip

extract the archive to your assets directory on your SD (which can be set in settings --> directory --> assets). and then change the menu driver to "xmb" (settings --> drivers --> menu driver).

this is still experimental, so expect slow performance and high loading times.

if anything goes wrong, edit your retroarch.cfg, find the menu_driver="xmb" setting, and change it back to menu_driver="rgui".

Just installed a couple of the new nightly CIAs to test. They load up now! However, they seem to crash upon loading content (tested with Picodrive on 2DS and FCEUMM on New 3DS).