I've just woken up to the new update and already had a user on reddit complain of the same thing. I'll look into it.
Edit: just installed 0.14.3 on 10.0.0 and everything is working fine. I'll update the system to 10.2.0 later when I have time and see if that's the issue.
No need to apologise. Given what appears to have changed in the update I'd have told you it's safe to go ahead.Thanks! I am on 0.14.3 on 10.2.0. It's probably what caused it. Sorry for jumping the gun!
Custom boot2 was only needed to start with because of an issue with previous Atmosphere versions. Issue is now resolved in the latest couple of Atmosphere releases, so MissionControl won't need custom boot2 any more in future.Ndeadly - any possibility that the Atmosphere team would incorporate your boot2 so it doesn't have to be re-written everytime.
As hippy dave said, the custom boot2 was only needed in 0.1.0 as a workaround to an issue SciresM fixed for me in Atmosphere 0.14.2. There's no custom boot2 in the 0.2.0 release. I haven't been able to install 10.2.0 yet, but I suspect this issue you're seeing has something to do with thread priorities.Updated sigpatches just arrived!
I haven't re-installed MissionControl to test it with the new firmware and atmosphere (and Sigpatches). Will wait for Ndeadly to give us the go ahead.
Ndeadly - any possibility that the Atmosphere team would incorporate your boot2 so it doesn't have to be re-written everytime.
You need to update the controller firmwareHave a question, is having button mappings all messed up by default normal for an Xbox One Controller?(https://www.walmart.com/ip/Microsof...Edition-Walmart-Exclusive-WL3-00149/948347409)
Also can't seem to get the home button to work as the Xbox Button.
That fixed it thanks. Sorry for wasting your time by not reading all the documentation.You need to update the controller firmware
https://github.com/ndeadly/MissionControl#frequently-asked-questions
Thanks for the response. Does this mean I should just wait until you have a chance to try out 10.2.0?I haven't been able to install 10.2.0 yet, but I suspect this issue you're seeing has something to do with thread priorities.
I have it working again now. Just need a bit of time to make a release.Thanks for the response. Does this mean I should just wait until you have a chance to try out 10.2.0?
https://github.com/ndeadly/MissionControl#known-issues-and-limitationsIt won't see my ps4 gamepad.
I updated the latest atmosphere and 0.2.1
It's official ps4 gamepad but not 2.0 (old version)
No.wil this work on sx os
Why =(
https://github.com/ndeadly/MissionControl#frequently-asked-questions said:Does this run on <insert CFW here>? No. MissionControl will only run under Atmosphère. This is not some petty act of malice toward other CFWs and their users. Others simply don't (currently) provide the framework neccessary for this sysmodule to work.
This is an issue I haven't heard of before. Could you explain in more detail? I can't think of why the docked joycons would receive the vibration packets for other controllersWorks like a charm!
Using my PS4 & WiiU Pro and my GameSir S3 Controller.
Only issue: the JoyCon docked on the Switch are vibrating instead of the used controllers. so I have to unmount them, because of the noise they create in my furniture