Skip to content

MissionControl 0.3.0
Compare
Choose a tag to compare
@ndeadly ndeadly released this 04 Oct 20:40
· 387 commits to master since this release
v0.3.0
41e6ca4

GitHub Releases

This is the fourth official release of MissionControl.

This release fixes a critical bug in the setting of thread priorities, reworks the way that controller inputs were being handled and adds support for a handful of new controllers, amongst other things. See below for the full changelog.

New users landing on this release page should first check out the readme on the main project page. Most of your questions will be already answered there.

Thanks again to all the users that requested and helped identify and test new controllers.
Also thanks to peteruk for sending me an icon to use for btdb.nro

IMPORTANT: Atmosphère >=0.14.2 is required to run this release of MissionControl. Older Atmosphere versions will cause the console to hang or crash during boot.
Users upgrading from version 0.1.0 of MissionControl are also advised to wipe their pairing database and re-pair controllers running 0.2.0 or greater. Failure to wipe the old entries may result in non-switch controllers being detected incorrectly.

Changelog

  • Added support for the following controllers
    • NVidia Shield (2017) Controller
    • TaTaCon (Taiko drum) Wii extension controller
    • 8bitdo zero
    • GameSir G4s
    • ipega 9076, 9078, 9087
    • PowerA Moga Hero
    • PowerA Moga Pro 2
  • Fixed an issue where threads were being assigned lower than intended priorities. This caused the game Hades to freeze at the loading screen when wifi was disabled, and possibly other unreported issues due to conflicting threads.
  • Changed the way that controller input reports are handled. State is now stored for each controller and updated with each incoming report. This should fix several cases where controllers could register false button presses/stick movements.
  • Unrecognised controllers now show up as connected to the console after successful pairing (may require a button press before the console sees the controller). These will display with red coloured buttons in the Controllers menu to indicate they are not being mapped. This should help eliminate some of the confusion between paired/connected state experienced by users requesting controller support.
  • Added the button combos MINUS + DPAD_DOWN and MINUS + DPAD_UP to act as HOME and CAPTURE buttons respectively, to act as a fallback for controllers where these buttons can't be mapped.
  • Reduced the brightness of Dualshock4 controller lightbar by 50%.
  • btdb.nro now has an option to clear the controller pairing database
Assets 4
Loading