Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

It sounds very odd how it could be a problem on the controllers end when it works fine on HOS as explained earlier.
I'd be greatful if people tested any USB controller at all just to make sure.

I have tested on both the official Switch dock and a third-party one and all results end up the same,
Works on HOS (OFW) but not on Atmosphere.

Kinda hard, unless there is someone with the same controller, and same firmware and Atmosphere build, like @impeeza said you might have to use to use Mission Control.

 

[Cellsplitter]

Kinda hard, unless there is someone with the same controller, and same firmware and Atmosphere build, like @impeeza said you might have to use to use Mission Control.

I am just scratching my head over the fact that it stopped working.

The new Atmosphere version is promoting a new USB transfer feature, so I figured the implementation of this might've broken the USB controller capabilities that once existed.

Also, looking into Mission Control it seems to be more catered to Bluetooth controllers, which this is not.
The reason I am hoping to get the Retro Defender controller working again is it's killer turbo feature that have been very useful to me.

 

[Hayato213]

I am just scratching my head over the fact that it stopped working.

The new Atmosphere version is promoting a new USB transfer feature, so I figured the implementation of this might've broken the USB controller capabilities that once existed.

Also, looking into Mission Control it seems to be more catered to Bluetooth controllers, which this is not.
The reason I am hoping to get the Retro Defender controller working again is it's killer turbo feature that have been very useful to me.

You seem to be correct, I just tried a wired horipad, it doesn't work on Atmosphere 1.5.2

 

[impeeza]

Was this something that was recently removed? Because USB controllers have been working just fine up untill now on Atmosphere. Litteraly the only change is the new FW + Atmosphere version.

Edit: I want to make myself crystal clear.

The USB controller I am using worked flawlessly on both HOS and Atmosphere before FW 16 and Atmosphere 1.5.2 dropped.
After updating it only works on HOS. Both SysNAND and EmuNAND (aka Atmosphere) does not recognize the controller at all.

First at all I am very sorry for my lapsus, I did confused SYS-CON with Mission Control. let me explain again:

On plain HOS (ninty switch O.S.) and plain Atmosphère only official and licensed USB/Bluetooth controllers will work, period.

SYS-CON (https://github.com/cathery/sys-con) adds support to some USB controllers, SYS-CON is an Sysmodule which act as a MITM service which translate the third party controller protocol to official language and makes thinks to the HOS what you connected a pro controller.

Mission Control (https://github.com/ndeadly/MissionControl/) does the same but for Bluetooth controllers.

Is possible what you did have on the past SYS-CON installed and then you purged your SD:/ATMOSPHERE/CONTENTS folder getting rid of your Sysmodule.

 

[braydenm]

Battery need to be atleast 10% for it to power on, so probably keep it plug into the charger, not docked.

it was plugged in all last night and when it started happening my switch was at like mid 80s maybe 90s

 

[Hayato213]

it was plugged in all last night and when it started happening my switch was at like mid 80s maybe 90s

Did you had it on AutoRCM? AutoRCM automatically put the switch into RCM mode.

 

[braydenm]

i t

Did you had it on AutoRCM? AutoRCM automatically put the switch into RCM mode.

yeah i did

 

[Hayato213]

i t

yeah i did

If it has enough charge to get into RCM mode, you can check with like Tegrasmashgui see if says RCM detected.

 

[braydenm]

If it has enough charge to get into RCM mode, you can check with like Tegrasmashgui see if says RCM detected.

I checked for devices using webFG on my chromebook

 

[Hayato213]

I checked for devices using webFG on my chromebook

You can use that too, if it detect it in RCM mode, you can try to push a payload.

 

[braydenm]

You can use that too, if it detect it in RCM mode, you can try to push a payload.

It doesn’t show up

 

[GDF]

Any one tith a patched V2 Mariko (sx core) actually been able to dump their keys . Care tell. Many thanks

 

[ndeadly]

I asked this on the Atmosphere 1.5.2 release thread but got no response so giving it a shot here.

Can anyone confirm whether or not the latest Atmosphere update may have broken USB controller support?
I've been using the Retro Defender controller on my Switch before without any problems but now it doesn't work at all.
The "Pro Controller Wired Communication" is set to ON of course so that is not the issue here.

What's odd is that it's working just fine on OFW which made me wonder if it's an Atmosphere issue.

If it matters I am using a Switch OLED with HWFly chip modded.

Are you using Mission Control? There's a bug introduced in the latest release that stops the hid module from detecting usb devices https://github.com/ndeadly/MissionControl/issues/614

 

[Cellsplitter]

Are you using Mission Control? There's a bug introduced in the latest release that stops the hid module from detecting usb devices https://github.com/ndeadly/MissionControl/issues/614

Thank you. This actually worked.

Just now I was testing on my official Switch Pro controller just to prove that I wasn't crazy.
Worked perfectly through USB on HOS but not on Atmosphere (just bluetooth).

Then I tried the Mission Control hotfix you linked and now the official Switch Pro controller works in Atmosphere aswell.
I noticed the files in question were mostly Atmosphere files so I guess it was a bug there afterall?

 

[ndeadly]

Thank you. This actually worked.

Just now I was testing on my official Switch Pro controller just to prove that I wasn't crazy.
Worked perfectly through USB on HOS but not on Atmosphere (just bluetooth).

Then I tried the Mission Control hotfix you linked and now the official Switch Pro controller works in Atmosphere aswell.
I noticed the files in question were mostly Atmosphere files so I guess it was a bug there afterall?

The issue has nothing to do with atmosphere, sysmodules are just installed into the atmosphere directory tree. The latest version of Mission Control includes some USB functionality (neccessary for pairing Dualshock 3 controllers) and just happened to use the same USB interface filter setup as the system hid module. Since these are required to be unique it overrode the original filter put in place by hid. The fix I linked just reduces the scope of the interface filter to only include the DS3 controller and avoids the collision.

 

[engagelover]

Hello guys, so I successfully updated my atmosphere just now, did it for the first time. Nearly had a heart attack. So my question is do I need to remove fusee.bin in the bootloader/payloads before pasting my payloads.bin (to boot to hekate). From my understanding is that fusee.bin make it so my switch boot into atmosphere, whereas payload.bin make it boot into hekate. If I have both in the same folder, what will happen?

Just now I remove fusee.bin and only left the payload from hekate. Rebooted my switch and it tries to boot into atmosphere but it gives error missing fusee.bin. I panicked and press every button, and it somehome enters hekate, and from there I manage to update my atmosphere.

 

[Hayato213]

Hello guys, so I successfully updated my atmosphere just now, did it for the first time. Nearly had a heart attack. So my question is do I need to remove fusee.bin in the bootloader/payloads before pasting my payloads.bin (to boot to hekate). From my understanding is that fusee.bin make it so my switch boot into atmosphere, whereas payload.bin make it boot into hekate. If I have both in the same folder, what will happen?

Just now I remove fusee.bin and only left the payload from hekate. Rebooted my switch and it tries to boot into atmosphere but it gives error missing fusee.bin. I panicked and press every button, and it somehome enters hekate, and from there I manage to update my atmosphere.

The way payload.bin setup is set up what ever payload you name as payload.bin that would get boot up if you have hekate bootloader folder files on your SD, and the payload.bin, typically it is Hekate for that payload.

 

[engagelover]

The way payload.bin setup is set up what ever payload you name as payload.bin that would get boot up if you have hekate bootloader folder files on your SD, and the payload.bin, typically it is Hekate for that payload.

So if I want to boot into hekate, just paste payload.bin into bootloader? Then if I want to boot direct to atmosphere again, just delete the payload.bin?

 

[Hayato213]

So if I want to boot into hekate, just paste payload.bin into bootloader? Then if I want to boot direct to atmosphere again, just delete the payload.bin?

You also need the hekate bootloader folder and files associated with it, you can boot atmosphere two way, either using hekate.bin to boot package3 or use atmosphere own bootloader fusee.bin to boot package3.

 

[Shayuna]

I have a problem i hope someone can help me.... After i Updating Atmosphere to 16.0.2 i cant open the album while running a game... get a grey screen , can only see the A button and nothing works anymore. i need to hold POWER and then need to booting in hekate..

when i hold R and start a game i can open hbmenu but i cant close it... press + the screen goes black but hbmenu appears again, press home and back to game i see hbmenu...

and my cheats are gone but i have everything copy to the atmosphere > contents folder... and the BID from some games has changed and nope i didnt update anything on my games

thats so weird all...

someone know how i can fix it?