Homebrew RELEASE Development Thread - RetroArch libnx

[Ty_]

Awesome work dude, loving the overlay. For the sake of feedback, with vsync on I get slowdown in Tiny Toon Adventures: Buster Busts Loose, with it off performance and sound are perfect.

 

[ownedlol]

Still going.

closing up to 48h btw

You better stop before you reach 72... that's when interesting things start to happen.

 

[Ty_]

Hmm, having issues with the emu in general. If L, R or the right analog are touched any game I try crashes (even with vsync off)

 

[m4xw]

L/R do Save state / load state.

You are invoking crashes if you spam them like that

 

[Leonidas87]

Hmm, having issues with the emu in general. If L, R or the right analog are touched any game I try crashes (even with vsync off)

Idk how your managing that did extensive testing with those settings.

Working flawless and never experience those issues.

If you save a state wait about 15 seconds.

If you load a state same thing be patient

If you start pushing L and R over and over it will crash I can confirm that.

Patience as save states are slow loading and saving

 

[Ty_]

L/R do Save state / load state.

You are invoking crashes if you spam them like that

Yeah, I mean if I use either (tried them in different orders to be on the safe side), or moving the right analog at all

 

[m4xw]

Those functions will block in newer functions tho, but thats when I work at the UI stuff

Savestate can sometimes render the core in a unstable state.

I don't think thats related to the port tho, but its a old core!

Edit: Open your SD, delete the state file. If it crashed while writing it might broke some sectors of your sd card.

 

[Leonidas87]

Yeah, I mean if I use either (tried them in different orders to be on the safe side), or moving the right analog at all

Can disable in input settings all 3 of those hotkey bindings to avoid the issue for yourself

 

[Ty_]

Those functions will block in newer functions tho, but thats when I work at the UI stuff

Savestate can sometimes render the core in a unstable state.

I don't think thats related to the port tho, but its a old core!

It's cool, just passing on my findings

 

[Leonidas87]

It's cool, just passing on my findings

Much appreciated try what I recommended for now.

 

[m4xw]

It's cool, just passing on my findings

Yes, but it doesn't replicate for me.

Its a different Issue!

In any case, ill work on that

 

[Ty_]

Narrowed it down further, the emu (on 5.0.2) crashes whenever the right analogue stick is moved specifically to the right. Happens with every game I've tried

 

[Leonidas87]

Narrowed it down further, the emu (on 5.0.2) crashes whenever the right analogue stick is moved specifically to the right. Happens with every game I've tried

Maybe you need to reinstall the emulator and config file, etc by replacing you existing files

 

[CatmanFan]

I feel like I should have to start porting Mupen64Plus via LibNX to the Switch...if there's anyone that can help me, let me know, because I don't think I'm on my own this time; I might have to collaborate, learn and research a bit to make it happen. Also, let @m4xw know if I can use his Makefile in my port with his permission.
I'm 75% sure this is going to fail, and I'll not really be surprised if it does.

 

[SeongGino]

I feel like I should have to start porting Mupen64Plus via LibNX to the Switch...

N64 still requires 3D acceleration for its plugins, so it won't work out until we can get that working in Libretro.

 

[m4xw]

Narrowed it down further, the emu (on 5.0.2) crashes whenever the right analogue stick is moved specifically to the right. Happens with every game I've tried

Fixed the cnfig file.

Slow motion multi needs to be 1

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

N64 still requires 3D acceleration for its plugins, so it won't work out until we can get that working in Libretro.

First step would be using more than 1 cpu core lol

 

[CatmanFan]

N64 still requires 3D acceleration for its plugins, so it won't work out until we can get that working in Libretro.

I was thinking a bit about that...
We should try software acceleration for now, which isn't really better, but I just want to see a port of the LibRetro N64 core, even though it would be very slow on the first try.

 

[SeongGino]

First step would be using more than 1 cpu core lol

Wait, multi-threading isn't a thing yet--?

. . . H u h

 

[m4xw]

Wait, multi-threading isn't a thing yet--?

. . . H u h

Welcome to early homebrew!

Untested VBA-Next core(on request): https://mega.nz/#!ms8g0C7A!BpJsO9n-YqGATFMqZIOAFJS9fvxFKwk7a5WI2fSIF48
same icon/description tho

I am just waiting for my Pizza.

Gn8

 

[SeongGino]

Welcome to early homebrew!

Can't say I'm terribly surprised!
Still... huh.

Anyways, VBA build works. Fullspeed in-game on Double Dragon Advance (3fps drop while in menu), Monkey Ball Jr. runs at about ~45fps in-game (hard to tell since the onscreen notifications don't work).
Also probably intended, but it was currently set to using SNES overlays by default. Probs because the build was pushed out so early.