ndeadly
ndeadly
Hmm ok, that's interesting. I don't think it's your sd card, I think the problem with the patches might not be where I thought it was. Leave it with me...
@Somozjx this ought to fix it now [MissionControl-0.9.3-develop-913c89b.zip](https://github.com/ndeadly/MissionControl/files/12448887/MissionControl-0.9.3-develop-913c89b.zip)
Try again with this. It will make a log in `sdmc:/mc-mitm.log`. Post it here for me to take a look at. [MissionControl-0.9.3-debug-logging-a3f60ba.zip](https://github.com/ndeadly/MissionControl/files/12457235/MissionControl-0.9.3-debug-logging-a3f60ba.zip)
> It will make a log in sdmc:/mc-mitm.log sdmc is the root of your sd card
This is a duplicate of https://github.com/ndeadly/MissionControl/issues/683, but I will keep this issue open if you actually own the controller (the guy who made the other issue doesn't have the controller...
Interesting idea. I don't even know how to access the console motion data, so will have to look into that first.
What worked? The controller connected now? Do buttons work? > Do You want me to senda You something? Because I've got Lost with that log in > thing XD I'm...
Use the new 0.9.4 release I made. You shouldn't use these debug log builds for everyday use as the logging slows things down and can create problems
No. I asked around and it seems like in order to access the raw motion data I need to talk to the hardware directly over SPI. This is more trouble...
Mission Control doesn't currently support wired controllers.