Homebrew mGBA official standalone Wii port

[nakata6790]

Nvm, latest build is September 20! I'll give it a spin and report back

 

[sindrik]

The emu is still kicking ass and taking names.

New features that i saw: clock on the menu, take screenshot, configuration for frameskip, show framerate, use bios, and bios path.

Awesome!

Just avoid using the BIOS for now, you will lose a good chunk of performance. Tested in Final Fantasy IV intro.

 

[nakata6790]

Indeed! And with the frameskip option, Asterix XXL, Duke Nukem 3d and others are perfectly playable now. Motoracer is @~40fps, not ideal but playable none the less. Good job!!

How difficult would a savestate/loadstate setting be?

P.S. I think it's time for gbatemp to make a forwarder for this emu

 

[ShadowOne333]

Golden Sun 2 still has issues with sound cracking up when an attack lands.
And damn... Meggido sure lags a lot. xD
So far that has been the only problem I've found!

I would kill for a button mapping and an unfiltered option, those are the only things keeping me from moving away from VBAGX right now. :/

 

[Ferrox]

240p and borders would be amazing.

 

[Deleted User]

240p and borders would be amazing.

Yeah, you can already do that on RA, but still.

 

[zerofalcon]

240p and borders would be amazing.

Game and border in 240p mode (CRT TV) with mGBA core. It looks great with non emulated scanlines.

 

[ShadowOne333]

Game and border in 240p mode (CRT TV) with mGBA core. It looks great with non emulated scanlines.

Is that the mGBA oficial port?
It's not the RA core right?
What else is new in the latest nightly?

 

[zerofalcon]

Is that the mGBA oficial port?
It's not the RA core right?
What else is new in the latest nightly?

It's the mGBA RA core, sadly very unstable at the moment for 32 mb roms (most 16 mb and lower roms crash). I did some changes in the code weeks ago and right now I'm working on it again to check more deeply if it can be fixed.

 

[ngs428]

Zip support would be greatly appreciated.

 

[the_randomizer]

It's the mGBA RA core, sadly very unstable at the moment for 32 mb roms (most 16 mb and lower roms crash). I did some changes in the code weeks ago and right now I'm working on it again to check more deeply if it can be fixed.

I love the fact that the RA team doesn't even bother looking into the issue -_- Speaking of RA issues, they told me to compile a new build for the Wii and test to see if performance is better, but there's no tut for building Wii dols, so...
https://github.com/libretro/RetroArch/issues/2164

IDK.

 

[zerofalcon]

I love the fact that the RA team doesn't even bother looking into the issue -_- Speaking of RA issues, they told me to compile a new build for the Wii and test to see if performance is better, but there's no tut for building Wii dols, so...
https://github.com/libretro/RetroArch/issues/2164

IDK.

Oh I see, I'm going to compile latest genesis plus core with RGUI 1.0.0.2, maybe this will perform better.

 

[the_randomizer]

Oh I see, I'm going to compile latest genesis plus core with RGUI 1.0.0.2, maybe this will perform better.

Hmm, so Twinaphex wasn't talking about the RA core itself, but the emulator cores? I thought he was talking about the RA GUI itself (boot.dol). Huh. I did download some nightly builds too, but haven't tested said builds. I can try the nightlies as well, but yeah, let me know how it goes

 

[Jacobeian]

No, he is telling you to recompile Retroarch from the latest source because latest release is now quite outdated compared to current source. However, on Wii, building Retroarch requires that you first build the core because they are linked together (one core per dol).

As for building it for Wii, there are basic instructions at the end of the readme
https://github.com/libretro/RetroArch

1) run "make -f Makefile.libretro" in the core source directory to compile it
2) then rename the generated .a file into libretro_wii.a and copy it to the root of retroarch source directory
3) run "make -f Makefile.Wii" in retroarch source directory to build the output .dol

 

[the_randomizer]

No, he is telling you to recompile Retroarch from the latest source because latest release is now quite outdated compared to current source.

As for building it for Wii, there are basic insteuctions at the end of the readme
https://github.com/libretro/RetroArch/

To compile cores, make -f Makefile.libretro in the core directory should work then rename the generated .a file into libretro_wii.a and copy it to the root of retroarch source directory as indicated.

Can't I just....use the nightly builds instead? Compiling from source seems a bit too daunting to download all the libraries, the programs to compile them, etc, to be honest. That and Zerofalcon said he wanted to take a crack at it as well.

Edit: Also, no guide for Windows users, that's just great.

Edit 2: Okay, there is, but there are too many instructions and my not-so-adept-programming head doesn't seem to make sense out of it.

 

[ShadowOne333]

Why compile the latest commit when you can simply download the latest Nightly from Retroarch Buildbots? :v

 

[Clydefrosch]

Why compile the latest commit when you can simply download the latest Nightly from Retroarch Buildbots? :v

where can you do that?

 

[the_randomizer]

Why compile the latest commit when you can simply download the latest Nightly from Retroarch Buildbots? :v

While that is true, something in the RA core itself could be FUBAR and botched up how the performance is handled (emulation regression); I'll be testing out updated core for two versions today

 

[ShadowOne333]

where can you do that?

Here:
http://buildbot.libretro.com/nightly/nintendo/

While that is true, something in the RA core itself could be FUBAR and botched up how the performance is handled (emulation regression); I'll be testing out updated core for two versions today

What do you mean by FUBAR?

 

[the_randomizer]

Here:
http://buildbot.libretro.com/nightly/nintendo/


What do you mean by FUBAR?

Fragged up beyond all recognition, it's a military term Meaning, royally jacked up, the recent RA has a massive regression with 16-bit emulators and dropping frames randomly, and the developers suggested a new build is compiled is likely has been fixed.

https://github.com/libretro/RetroArch/issues/2164

As such, I'll be testing a new Genesis Plus core (most recent version) on 1.0.0.2 and 1.2.2