Homebrew Question Trouble building for Swich with Unity3D

[Naminave]

You can also use Rewired/Incontrol that makes everything out of the box. Need to test my custom YT videoplayer but I think it's blocked for avoiding a 3ds-like exploit

For this it was necessary the switchsdkpluginunity that brings the entire library of the HID of the INPUT. With the Input Manager it is easy to work since the joy-con maps as well as an Xbox 360 control. But I have had problems when using the new Input System, since both iconTROL and Rewired have not supported and do it manually

 

[lyokohack]

It is easy to make, just take a look at Xbox one and just port the stuff to nn.hid.

you can explain to me this method for xbox one to activate the development switch?

 

[Manurocker95]

you can explain to me this method for xbox one to activate the development switch?

Eing?

 

[lyokohack]

It is easy to make, just take a look at Xbox one and just port the stuff to nn.hid.

You can only get it login into Nintendo's Switch developer portal or make your own. It is easy to make, just take a look at Xbox one and just port the stuff to nn.hid.

this method that you cited
I want to know how it works to activate my switch account from an XBox account
If I understood correctly

 

[Manurocker95]

this method that you cited
I want to know how it works to activate my switch account from an XBox account
If I understood correctly

No. I meant creating the NintendoSwitchInputDeviceManager looking at the xbox device manager xd

 

[LeyendaV]

D3fau4 managed to port Helltaker and it's working perfectly. You could take a look at the project.

https://github.com/D3fau4/Helltaker-switch

 

[Manurocker95]

D3fau4 managed to port Helltaker and it's working perfectly. You could take a look at the project.

https://github.com/D3fau4/Helltaker-switch

He only shares the resources and the nsp, not the code. And afaik, it uses the old input system

 

[Independent1997]

BTW, switch support for the new input system was moved to external packages starting v0.9.6. I tried v0.9.5 and its working great so far.

 

[lyokohack]

Manurocker95
thank you for correcting my misunderstanding

 

[Kolyasisan]

But, I don't get something regarding the helltaker port...

With an SDK, you can build the game and export it into two formats: an NSP (which seems to have wacky headers in its NCAs, never managed to extract them) or an NSPD file with the romfs and code NCA folders already exported.

Since it's not feasable to use the created NSP file, it seems that we'll have to use the extracted ones that sit alongside the NSPD. Question is: how do we pack them for it to be installable onto a retail system?

I've tried to mess around with hacPack for it and never made anything installable. If I try to pack NCAs from extracted files, then I get stuck immediately while packing the main NCA because I don't know the TitleID. How do we even get it? It's not getting created in any of the metadata files and getting it from the NSP file doesn't work (tools refuse to work with its NCAs). Not to mention that a ControlNCA is also needed in order to generate the meta NCA. So, we're stuck.

Going another path I tried to mess around with the Helltaker port. I built my main NCA using Helltaker's TitleID, but the resulting file's name turned out different and this made the NSP not installable. Renaming it made the game unbootable. And this is a pain because, once again, I don't think it's possible to generate the meta NCA.

So, I'm completely confused, what am I doing wrong? There's just not enough to work with, how exactly did this Helltaker port came to be?

If you build an NSP with Unity, it's not installable and messy so every tool refuses to work with it. If you build an NSPD, then there's not enough data to build an NSP yourself. You can't build just the main NCA and replace it over some other game's main NCA because the meta NCA will need to be rebuilt, otherwise results in it being unbootable. Pick your poison?

 

[Manurocker95]

But, I don't get something regarding the helltaker port...

With an SDK, you can build the game and export it into two formats: an NSP (which seems to have wacky headers in its NCAs, never managed to extract them) or an NSPD file with the romfs and code NCA folders already exported.

Since it's not feasable to use the created NSP file, it seems that we'll have to use the extracted ones that sit alongside the NSPD. Question is: how do we pack them for it to be installable onto a retail system?

I've tried to mess around with hacPack for it and never made anything installable. If I try to pack NCAs from extracted files, then I get stuck immediately while packing the main NCA because I don't know the TitleID. How do we even get it? It's not getting created in any of the metadata files and getting it from the NSP file doesn't work (tools refuse to work with its NCAs). Not to mention that a ControlNCA is also needed in order to generate the meta NCA. So, we're stuck.

Going another path I tried to mess around with the Helltaker port. I built my main NCA using Helltaker's TitleID, but the resulting file's name turned out different and this made the NSP not installable. Renaming it made the game unbootable. And this is a pain because, once again, I don't think it's possible to generate the meta NCA.

So, I'm completely confused, what am I doing wrong? There's just not enough to work with, how exactly did this Helltaker port came to be?

If you build an NSP with Unity, it's not installable and messy so every tool refuses to work with it. If you build an NSPD, then there's not enough data to build an NSP yourself. You can't build just the main NCA and replace it over some other game's main NCA because the meta NCA will need to be rebuilt, otherwise results in it being unbootable. Pick your poison?

The NSP is built with the Devkit Keys, so you can only play that NSP with a real devkit. However, you can unpack it and repack it again with retail console keys. This only applies to sdk builds, not libnx (devkitpro) compiling nsps.

iirc, d3fau4 used libnx as compiler so you are out of luck checking it, but I'd recommend you to check authoring tools folder

 

[Kolyasisan]

The NSP is built with the Devkit Keys, so you can only play that NSP with a real devkit. However, you can unpack it and repack it again with retail console keys. This only applies to sdk builds, not libnx (devkitpro) compiling nsps.

iirc, d3fau4 used libnx as compiler so you are out of luck checking it, but I'd recommend you to check authoring tools folder

Can you even use libnx with Unity? I thought that it's heavily dependant on the official SDKs to compile code and shaders. I'm pretty sure that my NSPs were compiled with the leaked SDK. I can surely unpack my NSPs and repack them with my retail keys, but the NCAs are still wacky, so they again result in being not installable.

 

[Manurocker95]

Can you even use libnx with Unity? I thought that it's heavily dependant on the official SDKs to compile code and shaders. I'm pretty sure that my NSPs were compiled with the leaked SDK. I can surely unpack my NSPs and repack them with my retail keys, but the NCAs are still wacky, so they again result in being not installable.

Afaik, If you know how, yes, it is possible. Then you are not doing correctly. Unpacking with authoring tools and repacking it with nsp builder works out of the box on retail consoles .

 

[Kolyasisan]

Afaik, If you know how, yes, it is possible. Then you are not doing correctly. Unpacking with authoring tools and repacking it with nsp builder works out of the box on retail consoles .

Hmmmmm..... I'm obviously missing something.
Can you please correct me to what I'm potentially doing wrong? I'm doing roughly this:
1 - Export the NSP from Unity
2 - Unpack it with leaked SDKs authoring tools
3 - Repack the entire folder (including all the NCAs, icons, XMLs) using hackPack

After doing that, the NSP behaves like an initial NSP straight from Unity. It's not installable on my system, DBI (for example) complains about the NCA magic number.

Maybe the problem is in the TitleID? I can't get it from the original NSP because its NCAs are unreadable, so I tried to generate ones myself or try using the Helltaker's one. Both didn't work. Then again, it does go back to one of my previous points in my initial message.

Thanks.

 

[Kolyasisan]

Using a different tool (NSPack) moved things a bit further. Now an NSP builds and installs successfully, but bootloops on the startup. I'm pretty confused, I've been doing the exact same things as with hacPack.

 

[Deleted User]

Does UnitySetup-Nintendo-Switch-Support-for-Editor-2018.2.0b3 work with Unity 2019 or is it limited to the same Unity build from the pastebin? I'm unable to find a leak of the newer version.

 

[Kolyasisan]

Does UnitySetup-Nintendo-Switch-Support-for-Editor-2018.2.0b3 work with Unity 2019 or is it limited to the same Unity build from the pastebin? I'm unable to find a leak of the newer version.

From my experience the build target installation only works with a matching Unity version, so, yeah, you'll need the 2018.2.0b3 editor to work with the target installation.

 

[Deleted User]

From my experience the build target installation only works with a matching Unity version, so, yeah, you'll need the 2018.2.0b3 editor to work with the target installation.

I assumed that as well, issue is there isn't a newer build leak so I have no idea how some users have a newer build.

 

[Kolyasisan]

I assumed that as well, issue is there isn't a newer build leak so I have no idea how some users have a newer build.

Maybe some of them actually have a devkit or two and just use the officially provided SDKs to them?

 

[lyokohack]

I got the error that this version of Unity

https://www.youtube.com/watch?time_continue=4&v=ES1omDeON4w&feature=emb_logo

"Unity3d 2018.2.0b3" and I have this SDK "SIMONMKWII"

and i want how to ignore this error from this SDK