search

ndeadly / MissionControl

Use controllers from other consoles natively on your Nintendo Switch via Bluetooth. No dongles or other external hardware neccessary.
GNU General Public License v2.0
2.38k stars 137 forks source link

[Bug Report]: Module crashed switch while playing #758

Open alanblackvolt opened 7 months ago

alanblackvolt commented 7 months ago

Switch Firmware Version

17.0.0 (Latest)

Atmosphère Version

Other (please specify in issue description)

Mission Control Version

0.10.0 (Latest)

Boot Method

Hekate

Issue Description

Hi, this happened to me yesterday (Atmosphère Version: 1.6.2) The point is that I used two official playstation 3 controllers to play with my friends, they connected correctly and we could play (the game we were playing was overcooked 2) after 30 minutes of playing our controls stopped responding and only the home buttons responded, I tried to exit the game but could not, then I put the console in sleep mode with the power button and then when I hit the power button again, atmosphere crashed, I could not take a photo of the error but a log was generated in the crash_reports folder, I will leave it here so you can see what was the error, then i shutdown the console, I turned it on normally in stock mode without rcm, then I did the process to enter RCM and nothing unusual happened after that, I could boot atmosphere normally, nothing weird or critical happened after that.

Error Report

01700956243_0100000000000013.log

Additional Context

just in case the crash happened while me and my friends were playing Overcooked 2, the controllers stop responding and only the home buttons responded My controller was a Nintendo Switch Pro Controller (third party) and the other 2 controllers was Sony Dualshock 3 (both officials) i turn the console i sleep mode, then turned on and crash

ndeadly commented 7 months ago

I'm not actually sure if this is related to Mission Control or not. This error is the hid service crashing, which Mission doesn't directly interact with. It's possible the controller has sent something that hid doesn't like, but if that were the case then I would expect it to be just as likely for this to happen with any other controller type (we don't allow any original data packets from the controller to pass)

Nevertheless, I'll take a look at the traceback when I have time to see if there's any chance it's related. Maybe you could also list what other custom sysmodules etc you might be running.

alanblackvolt commented 7 months ago

well, mission-control is the only sysmodule that i got also I forgot to mention something else, after enter to stock and returning to Atmosphere, my friends and I played Mario Party Superstars with the same controls that I already mentioned and nothing weird happened, no crashes or the controls stopped responding, I don't know if it was a sysmodule booting issue or someting else.