Homebrew RELEASE Development Thread - RetroArch libnx

[rad.i.kal]

I just wish people would update to 5.1, that is where all dev stuff will happen

 

[ShadowOne333]

I just wish people would update to 5.1, that is where all dev stuff will happen

Seeing how consoles with <=3.0.0 firmware have a potential coldboot alternative, I highly doubt those on lower firmwares would want to do that.
That is actually why I haven't updated my 3.0.0 Switch.

 

[SeongGino]

The cores are just being rebuilt right now.

You can check the status on the main post. This is the Input fix ! Ping @SeongGino

Works swimmingly. I can play vidya gamus now.

 

[rad.i.kal]

Seeing how consoles with <=3.0.0 firmware have a potential coldboot alternative, I highly doubt those on lower firmwares would want to do that.
That is actually why I haven't updated my 3.0.0 Switch.

I started with a console over 3.0, are you speaking of an alt for the RCM jig?

 

[SeongGino]

I started with a console over 3.0, are you speaking of an alt for the RCM jig?

Jig-less, yes. That's, as far as we know, the only viable alternative.
Then again, assuming Atmosphere installs itself directly after the first boot, this may be a moot point...

 

[ballcity]

Please is there any fix for 3.0.0?

There is nothing wrong on 3.0 with the stable builds.

Threading is WIP, won't work until its ready. Stop asking.

It only delays it if I have to take the time to answer.

Okay, I noticed someone said this earlier in the thread, but I wanted to test/confirm this.

For what it is worth, I am on 3.0.0, and if I use Hekate-ipl to boot into a CFW allowing you to use HBL from the Album icon, I can run the threaded versions fine. There is no crash on ROM load.

HOWEVER, if I instead use the Pegaswitch exploit via the custom DNS server, every time I get a crash in using the threaded version immediately upon selecting a ROM (but the "stable" non-thread version works fine).

So, it must be some issue with how the "older" exploit chain works, or there is something else Hekate is patching that allows you to use more cores or something. Again, no idea why this is happening, just wanted to clarify specifically that it isn't necessarily a Horizon 3.0.0 issue.

 

[ShadowOne333]

I started with a console over 3.0, are you speaking of an alt for the RCM jig?

Correct.
Apparently there's another way to do this for consoles on 3.0.0 or below, which doesn't require RCM or anything like that, and should be tetherless as well.

 

[m4xw]

Okay, I noticed someone said this earlier in the thread, but I wanted to test/confirm this.

For what it is worth, I am on 3.0.0, and if I use Hekate-ipl to boot into a CFW allowing you to use HBL from the Album icon, I can run the threaded versions fine. There is no crash on ROM load.

HOWEVER, if I instead use the Pegaswitch exploit via the custom DNS server, every time I get a crash in using the threaded version immediately upon selecting a ROM (but the "stable" non-thread version works fine).

So, it must be some issue with how the "older" exploit chain works, or there is something else Hekate is patching that allows you to use more cores or something. Again, no idea why this is happening, just wanted to clarify specifically that it isn't necessarily a Horizon 3.0.0 issue.

Are u fucking shitting me?

 

[l_steve_l]

There is nothing wrong on 3.0 with the stable builds.

Threading is WIP, won't work until its ready. Stop asking.

It only delays it if I have to take the time to answer.

Are u fucking shitting me?

I mean.... reading is hard stuff I guess....

 

[Gold_Experience]

I mean.... reading is hard stuff I guess....

Games work well. tried most ps1 games on switch. when will it run smoothly with audio?

 

[SeongGino]

Games work well. tried most ps1 games on switch. when will it run smoothly with audio?

It won't. It's a PoC core.
Wait for PCSX-ReARMed to get ported for PlayStation w/ audio.
Something tells me BeetlePSX-NX this early was a mistake.

 

[m4xw]

I mean.... reading is hard stuff I guess....

No thats not what it was about.

He supplied value information.

Honestly I dont know what the fuck is going on, that would actually explain it, even tho there are a million possibilities why it does happen then

 

[SeongGino]

No thats not what it was about.

He supplied value information.

Honestly I dont know what the fuck is going on, that would actually explain it, even tho there are a million possibilities why it does happen then

I sincerely hope the stark contrast in compatibility with threading is more of a bug on PegaSwitch's part, and NOT a bug/feature exclusive to Atmosphere/current Hekate implementation.

 

[ballcity]

No thats not what it was about.

He supplied value information.

Honestly I dont know what the fuck is going on, that would actually explain it, even tho there are a million possibilities why it does happen then

That's what I took it as - no worries! Just wanted to make sure accurate information was provided to help narrow down where the issue might be. Honestly, I am probably just going to be using Hekate going forward now that the sleep bug is fixed, and will be using Atmosphere (cold boot?!) when it gets released. So it might not even be worth investigating why the Pegaswitch chain is having issues -- Hekate all the way . Of course I'm sure 3.0.0 via Pega users will still complain and wonder why it's not working...

I sincerely hope the stark contrast in compatibility with threading is more of a bug on PegaSwitch's part, and NOT a bug/feature exclusive to Atmosphere/current Hekate implementation.

Hekate is implemented at such a higher level, my speculation is that it enables higher level system calls or the like -- but pure conjecture there. Sticking to Hekate as a community is clearly the answer .

 

[SeongGino]

Hekate is implemented at such a higher level, my speculation is that it enables higher level system calls or the like -- but pure conjecture there. Sticking to Hekate as a community is clearly the answer .

Technically lower-level in this context, since it is directly patching the kernel rather than being a basic unsigned code exploit, but indeed. Would be beneficial if we stood by one platform. CoughTXcough

 

[wicksand420]

F TX

 

[Gold_Experience]

It won't. It's a PoC core.
Wait for PCSX-ReARMed to get ported for PlayStation w/ audio.
Something tells me BeetlePSX-NX this early was a mistake.

Nah it wasn't. why wait. The Switch homebrew scene has a lot of emulators. it's nice. The wii u had a psx emulator too but at the end of it's life.

 

[slyd0r]

Both me and my kids have lots of fun with the Snes emulator and the GBA one.
Works great, even in docked.
I had to delete the cfg file, saving/loading on physical buttons isn't my thing.
And the PSX emulator works great, can't wait to see what you archive with the other psx core.
Just wanted to say thank you.
Also it would be great if we could play Multiplayer with two joycons.

 

[SeongGino]

Nah it wasn't. why wait. The Switch homebrew scene has a lot of emulators. it's nice. The wii u had a psx emulator too but at the end of it's life.

Honestly, I don't feel like optimizing the core. Doesn't look future proof to me

This is more of a proof-of-concept to me

You'll have to wait either way anyways. But we'd rather wait for something that'll work better than struggling to make something else not befitting of the hardware work by brute force. It's why everyone else says to use PCSX-ReARMed instead of the Mednafen based cores.

Hint hint, it's why 4DO, VirtualJaguar, Yabause, and etc. are not worth the trouble of improving individually atm.

 

[m4xw]

Both me and my kids have lots of fun with the Snes emulator and the GBA one.
Works great, even in docked.
I had to delete the cfg file, saving/loading on physical buttons isn't my thing.
And the PSX emulator works great, can't wait to see what you archive with the other psx core.
Just wanted to say thank you.
Also it would be great if we could play Multiplayer with two joycons.

Immer gerne!

Technically lower-level in this context, since it is directly patching the kernel rather than being a basic unsigned code exploit, but indeed. Would be beneficial if we stood by one platform. CoughTXcough

Sounds to me to some privilege problems, maybe its still somewhat sandboxed/didn't get full privileges, I don't know how the priv. escalation of pegaswitch works.