[Switch] MissionControl: Controller per Bluetooth ohne Adapter verbinden

  • Update auf Version 0.5.0 beta



    Atmosphère >= 0.19.5 is required to run this release.


    Changelog:

    • Added support for AtGames Legends Pinball controller
    • Added ips patches for all 12.x.x firmwares to relax device class checks added in 12.0.0. This allows ipega and several other controllers that advertise themselves as keyboards or other input devices to pair once again
    • Added support for the old Xbox One controller report format. Updating controller firmware is no longer a requirement for correct mapping of controls
    • Added a configuration option to disable the LED lightbar on Sony Dualshock4 and Dualsense controllers
    • Added delays when initialising Wii controller extensions. This should make detection of extension controllers more reliable for people who were experiencing issues
    • Reduced default reporting rate of Dualshock4 controller from 1000Hz to 125Hz to match Switch Pro Controller. This resolves an issue where using a Dualshock4 controller could seriously degrade wifi performance and caused issues with LAN play
    • SetTsi command is now only blocked from being sent to controllers where it is known to create issues (currently Xbox One and Gamesir controllers). This resolves an issue where a Dualshock4 controller connected alongside an official Nintendo controller would experience significant jitter, rendering it unsuitable for rhythm games. Blocking this command may also have played a part in the wifi issues mentioned above.
    • Fixed a bug where some wiimote buttons could not be pressed with an extension controller connected
    • Fixed a bug where Xiaomi controllers would always show low or empty battery levels
    • Improved accuracy of battery level reporting in general
    • Dropped custom fork of libnx now that all relevant changes have been upstreamed. The libnx submodule now points to the official master branch, and at the time of writing Mission Control can be built with the official release from devkitPro without the need to compile it yourself

    Download

    https://github.com/ndeadly/MissionControl/releases

  • Mission Control hat den Stable Status erreicht! Update auf Version 0.5.0!


    Atmosphère >= 0.19.5 is required to run this release!

    Note: after some discussion with other devs, the location used in the pre-releases for the module config .ini has been changed to sdmc:/config/MissionControl/missioncontrol.ini to be more consistent with other homebrew projects.


    Changelog:

    • Added support for the following controllers
      • Razer Raiju Tournament
      • Gamesir T1s
      • 8BitDo SN30 Pro Xbox Cloud Gaming Edition
      • Mad Catz C.T.R.L.R for Samsung
      • Steelseries Stratus Duo
      • iCade controller
      • LanShen X1Pro
      • AtGames Legends Pinball controller
    • Added full support for 12.0.0 firmware
    • Added ips patches for all 12.x.x firmwares to relax device class checks added in 12.0.0. This allows ipega and several other controllers that advertise themselves as keyboards or other input devices to pair once again.
    • Added ips patches for all 12.x.x firmwares to make Wii/WiiU and other controllers that use legacy pincode pairing work again
    • Added initial rumble support for selected major console controllers
    • Added a global module configuration ini file
    • Added support for spoofing the Bluetooth host adapter name and address
    • Added support for Sony Dualsense player LEDs/lightbar colour and battery level reporting (thanks @Hydr8gon)
    • Added support for the old Xbox One controller report format. Updating controller firmware is no longer a requirement for correct mapping of controls.
    • Added support for an alternative report format for Mocute 050 controllers on certain firmware revisions
    • Added a configuration option to disable the LED lightbar on Sony Dualshock4 and Dualsense controllers.
    • Button combos for Home and Capture buttons are now also applied to official Nintendo controllers. Note that currently the console will ignore the combos for buttons that are not supposed to be present on the controller (eg. home button on left joycon, capture button on right)
    • Fixed a bug caused by passing invalid analog stick factory calibration data for emulated controllers. This bug affected the scaling of analog stick data for all controllers to some degree, but was most noticeable for Xbox One controllers, where the stick values would max out when the stick was only around 60-70% tilted.
    • Added delays between reading/writing controller memory when initialising Wii controller extensions. This should make detection of extension controllers more reliable for people who were experiencing issues.
    • Reduced default reporting rate of Dualshock4 controller from 1000Hz to 125Hz to match Switch Pro Controller. This resolves an issue where using a Dualshock4 controller could seriously degrade wifi performance and caused issues with LAN play.
    • SetTsi command is now only blocked from being sent to controllers where it is known to create issues (currently Xbox One and Gamesir controllers). This resolves an issue where a Dualshock4 controller connected alongside an official Nintendo controller would experience significant jitter, rendering it unsuitable for rhythm games. Blocking this command may also have played a part in the wifi issues mentioned above.
    • Fixed a bug where some wiimote buttons could not be pressed with an extension controller connected.
    • Fixed a bug where Xiaomi controllers would always show low or empty battery levels.
    • Improved accuracy of battery level reporting in general.
    • Dropped custom fork of libnx now that all relevant changes have been upstreamed. The libnx submodule now points to the official master branch, and at the time of writing Mission Control can be built with the official release from devkitPro without the need to compile it yourself.
    • Removed call to CheckApiVersion function. This was intended for internal Atmosphere usage and was one of the major reasons Mission Control would often require an update after a new Atmosphere release.
    • Updated to use new sf semantics introduced in Atmosphere 0.18.0
    • Updated to use latest libstratosphere. This reduces the size of the module by almost 50%
    • Added git branch, commit hash and tagged version when generating .zip file for distribution


    Download

    https://github.com/ndeadly/MissionControl/releases

  • habe die neuste version installiert und jetzt habe ich nur noch nen black screen wenn ich atmosphere boote. hatte die neuste version von atmospehre


    irgendwie bin ich glaub ich zu blöd um mein ps5 controller zu verbinden.


    Habe die beiden Ordner ins root Verzeichnis von der SD Karte verschoben aber ich bekomme keine Verbindung zum controller. Muss ich noch irgendwas machen was ich übersehe?

  • Hast du es per Tesla Menü auch aktiviert?

  • ich habe nur die datein auf die sd karte kopiert. wo finde ich denn das tesla menu?


    okay tesla menu hab ich jetzt instaliert aber da finde ich kein eintrag dazu


    Diese datei habe ich runtergeladen, entpackt und in im root von der sd karte gepackt MissionControl-0.5.0-master-9547d51.zip

  • Hast du auch ovl-sysmodules drauf?

  • kann mir jemand helfen weil ich weiß nicht wie ich das Mission Controll installieren muss habe atmosphere drauf von Muxi das AtmosXl paket

    Muss ich einfach nur bei github den neusten 0.5.0 release laden auf die switch entpacken und das funzt dan einfach so ?

    Oder muss man da noch irgendwas beachten?

    Weil ich finde auch keine .nro

    Nutze alles auf einem emunand

    Bitte um hilfe danke:)

  • Einfach in die entsprechenden Ordner kopieren und neu starten, das war’s!

  • Muss ich einfach nur bei github den neusten 0.5.0 release laden auf die switch entpacken und das funzt dan einfach so ?

    Nein, du musst zuerst zu amsPLUS wechseln, weil AtmoXL nicht mehr auf dem aktuellsten Stand ist, da der Support vor einiger Zeit (unter AMS Version 0.19.1) bereits eingestellt wurde und die letzte Version von MissionControl darunter nicht betrieben werden kann.

  • Mas31187 Bist du auch bestimmt mit allen Komponenten auf dem aktuellsten Stand?

    CFW Version 0.19.5

    FW Version 12.1.0

    MissionControl Version 0.5.0

  • Hast du vielleicht noch weitere sysMods installiert, außer MissionControl und den Standard sysMods? Möglicherweise verträgt sich MissionControl nicht mit sysFTPD-Light oder dem Tesla Menü. Du kannst diese Mods über den Extras Aktivator auch gezielt deaktivieren lassen, um die Diskrepanz ermitteln zu können.

  • das tesla menu brauche ich nicht zwingend für mission controll oder?

    Nein, aber eventuell liegt es aber auch an sysFTPD-light, dann müsstest du nicht auf das Tesla Menü verzichten. FTP könnte alternativ auch über die HB-App FTPD genutzt werden.

  • Mission Control v0.5.1


    Changelog:

    • Added support for the following controllers:
      • Microsoft Xbox Elite Series 2 Controller
      • Gamesir T2a
    • Updated ips patch set to enable successful pairing of the Xbox Elite Wireless Series 2 controller .
    • Added file-based virtual SPI flash system. Data such as calibrations can now be stored and retrieved for each controller.
    • Analog values for L/R on the Wii Classic Controller are now taken into account when mapping controls. This allows for identical trigger behaviour of Gamecube controllers used via a wiimote adapter vs the official USB adapter.
    • Fixed a regression where Mocute 050 and 8bitdo Zero controllers were disconnecting due to receiving the SetTsi command from the console.
    • Rumble data sent along with the subcommand report (0x01) is now correctly handled.
    • Fixed an array subscript partly outside of array bounds warning during compilation of the module.

    Download:

    https://github.com/ndeadly/MissionControl/releases/download/v0.5.1/MissionControl-0.5.1-master-6fdc8ee.zip

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!