switch pro controller weird behaviour + question

[kienan94]

controller works fine on phone on pc even when using stuff to convert to an xbox controller the x axis is not recognised when it says "controller press a button or move a joy on the game controller" but is recognised under the controller test tab both running 2025.05. also have a question regarding a feature with the 42176 technic move hub. is it possible to get self centre steering with playvm turned off? i much prefer the way it accelerates and breaks in that mode but steering is useless have got it to kinda work but when i steer it cuts out acceleration.

[vicocz]

controller works fine on phone on pc even when using stuff to convert to an xbox controller the x axis is not recognised when it says "controller press a button or move a joy on the game controller" but is recognised under the controller test tab both running 2025.05.

Hi,
if I understand your report properly, Switch Pro Controller works properly on your phone, but when running the app on Windows, X axis is shown in Controller test page, but it's not detected when waiting for gamepad event in order to add a new controller event . Is it?
From the description it seems to me there might be issue with values of X axis provided to the app as it requires circa value of 0.8 and more in order to add a new event for given axis.
Could you check what minimum and maximum values are reported for X axis on Controller test please?

also have a question regarding a feature with the 42176 technic move hub. is it possible to get self centre steering with playvm turned off? i much prefer the way it accelerates and breaks in that mode but steering is useless have got it to kinda work but when i steer it cuts out acceleration.

Unfortunately when PLAYVM mode is disabled, the hub does not support setting of degrees (as it restarrts the hub). THerefore there is no option to apply servo stearing mode for C channel nor any calibration / center steering.

Regards
Vico

[kienan94]

x axis seems to range from 0.100 minimum to 0.783 max on windows. so you are correct its not reaching a value of 0.8
on phone reaches a value off 1.0 max same minimum

[vicocz]

x axis seems to range from 0.100 minimum to 0.783 max on windows. so you are correct its not reaching a value of 0.8 on phone reaches a value off 1.0 max same minimum

Yeah, that's it.

From application perspective, I've adjusted 80% threshold to 50% only, so this should be fixed.
But without any additional setting, you will get only 78% percent of channel power when an axis is fully pushed. I've found that 8 years ago there was a hack for Android: Nintendo Switch Pro controller hack ([-0.69:0.7] -> [-1:1]) imurvai#2 so I guess that's the reason why it works for Android right now.

Recently I've created the following item #201 so as it could be possible to define some adjustments directly by users.

[kienan94]

from my reseach on the switch pro controller seems to be default behaviour on windows that it only shows 0.7-0.8 on the x axis with 0.7 being the worst i had seen. so maybe a threshold of 70% may be more suited. though yes giving the user the option to configure axis on the app would be a better alternative