Yeah, this is partly what I'm referring to when I say the intensity is a bit unbalanced. Some of this is unavoidable, since with standard rotating mass motors the amplitude and frequency can't be decoupled like the HD rumble can. In particular, short, low frequency bursts of vibration can be problematic because the motor barely has time to spin up. I believe it could be improved though by mapping some of these up into higher ranges that are more responsive. It's just not something I find particularly interesting to work on.The only problem I saw was that vibration is not working for some weapons of Doom eternal(Some low-level vibration weapons)
Just a heads up to anyone using this, it's been reported to me that running nx-btred alongside mission control will increase input latency with controllers. By how much I'm not sure, YMMV, but enough to significantly impact performance in rhythm games at least.https://github.com/plutooo/nx-btred
It needs missioncontrol on +12.0, working fine in a aliexpress bt receptor
Care to elaborate?"R TYPE FINAL 2" error
Can not enter the game, prompted to press L, R to confirm the handle, but the button does not workYeah, this is partly what I'm referring to when I say the intensity is a bit unbalanced. Some of this is unavoidable, since with standard rotating mass motors the amplitude and frequency can't be decoupled like the HD rumble can. In particular, short, low frequency bursts of vibration can be problematic because the motor barely has time to spin up. I believe it could be improved though by mapping some of these up into higher ranges that are more responsive. It's just not something I find particularly interesting to work on.
Just a heads up to anyone using this, it's been reported to me that running nx-btred alongside mission control will increase input latency with controllers. By how much I'm not sure, YMMV, but enough to significantly impact performance in rhythm games at least.
--------------------- MERGED ---------------------------
Care to elaborate?
L + R is really meant for determining the joycon grip orientation. On official controllers, this also has the side effect of waking the controller but doesn't actually do anything in the case of the Pro Controller. For unofficial controllers you should interpret this as "wake your controller". For the DS4 controller this is done by pressing the PS button.Can not enter the game, prompted to press L, R to confirm the handle, but the button does not work
MissionControl 0.5.0 pre-release (ps4 controller v2)
FW: 12.0.1
Atmosphere 0.19.1
DeepSea 2.2.2
I'm connecting again, and it's working, thanksL + R is really meant for determining the joycon grip orientation. On official controllers, this also has the side effect of waking the controller but doesn't actually do anything in the case of the Pro Controller. For unofficial controllers you should interpret this as "wake your controller". For the DS4 controller this is done by pressing the PS button.
The Ps4 controller working fine? Any delay problems?L + R is really meant for determining the joycon grip orientation. On official controllers, this also has the side effect of waking the controller but doesn't actually do anything in the case of the Pro Controller. For unofficial controllers you should interpret this as "wake your controller". For the DS4 controller this is done by pressing the PS button.
Yes, all is working fine as long as you skip firmware 12.0.0 as it introduced bugs to the controller pairing that were fixed in 12.0.1. I've never experienced any noticeable delays with normal use. It really depends on what else you have running though. If there is a lot of activity on the CPU or UART interface due to other sysmodules that it has to compete with then it wouldn't be that surprising if delays occurred. I've had a report that running nx-btred seems to do just this. Whether it's a system limitation or can be optimised away remains to be seen.The Ps4 controller working fine? Any delay problems?
This is the first I've heard of a controller that still isn't pairing after the release of 12.0.1. Did you previously have it working? Could you try using the latest mission control with your firmware downgraded below 12.0.0? I'm curious as to whether it's the 12.0.0 changes or something I changed since 0.4.1.wellp, even with the latest update of MC and on 12.0.1 i cant re connect my ipega, its sad cuz I don't have any other controller to play
This is the first I've heard of a controller that still isn't pairing after the release of 12.0.1. Did you previously have it working? Could you try using the latest mission control with your firmware downgraded below 12.0.0? I'm curious as to whether it's the 12.0.0 changes or something I changed since 0.4.1.
As I side note, if that works you can upgrade back to 12.0.1 and the pairing will be retained unless you try to pair the controller to something else
Yeah that all makes sense and is expected. Stuff definitely got changed in the bluetooth service, they rewrote a chunk of it and in the process I think introduced some bugs. I thought 12.0.1 fixed whatever broke pairing, but maybe not entirely. Or maybe something I've changed since the previous release has affected the ipega controllers somehow. That's why I want to see what happens with 0.5.0-alpha on a lower firmware.prior to 12.0.0 it worked perfectly using to that time the latest mc update, after 12.0.0 it stoped working, even using, as I mentioned, the latest update of MC. Its odd perhaps some stuff on 12.0.0 got changed, I will try to go back to 11.0 if i can use choidojours only using touch controls and try that
It's fine if you're already using the controller below 12.0.0. It's only pairing of those that still needs an update for 12.x.x. If it's already paired it will continue to work as usual. I'm in the process of moving apartments at the moment so I can't say how long before I'll be able to find time to release the final version with full 12.x.x support.Is it safe to update to 12.x + latest MC beta if I'm using a Wii U Pro Controller or should I wait a bit longer?
Controller audio is not supported.It worked with Dualshock 4. However, when connecting my wired headset to the controller, the audio was still coming out on the TV. Is there any way to fix it?
Wii controller pairing needs to be updated to work on 12.x.x. it wasn't added at the time I made the pre-release because 12.0.0 broke pairing for most controllers. See here for a more detailed explanation.For some reason i can't connect my official Wii U pro controller and some knockoffs that I could on 11.1
is there any fix? I tried a clean install of everything and yet doesn't work
Switch 12.1 AMS 19.2
Firstly, you should update to the latest atmosphere and mission control versions. There should be no issues with wiimote pairing on 11.0.1, so I can only guess you either aren't on the correct menu or you have a 3rd-party knockoff controller that is incompatible. You should be on the Change Grip/Order screen and pressing the red sync button on the controller.I am using system 11.0.1 and ams 17.1 and when I try to pair a wii mote the 4 blue leads on the wiimote flash but nothing else happens. What am I doing wrong?
Sent from my Surface Duo using Tapatalk