You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, these functions should return the same as the "Get [Motion Sensor]" functions that already exist.
For platforms that support multiple devices with motion sensors (such as PS3, PS4, PS5, and Switch), These functions should return the motion data provided by the individual controller.
Progress
Fallback implementation
Switch implementation
The text was updated successfully, but these errors were encountered:
halotroop2288
changed the title
Input -> "Get Controller [Motion Sensor]" and "Set Controller [Motion Sensor]" function for GDScript
[3.5 | Switch] Input -> "Get Controller [Motion Sensor]" and "Set Controller [Motion Sensor]" function for GDScript
Jan 24, 2024
halotroop2288
changed the title
[3.5 | Switch] Input -> "Get Controller [Motion Sensor]" and "Set Controller [Motion Sensor]" function for GDScript
[3.5] Input -> "Get Controller [Motion Sensor]" and "Set Controller [Motion Sensor]" function for GDScript
Nov 10, 2024
By default, these functions should return the same as the "Get [Motion Sensor]" functions that already exist.
Actually I'd like to amend this to just return zero for everything except pad index 0, the emulated gamepad. Because on PC, these will always return zero until they're implemented for controllers. And on mobile, external controllers should not reflect the state of the mobile sensors.
The Vita does not support multiple controllers. And these functions do not exist in the upstream, so I know they're not implemented in any existing ports.
Currently, the Vita will simply use the value returned by the device motion sensor in my implementation. The same as every other platform.
Though as I mentioned above, I'd like to change it to return zero so all the controllers don't accidentally move at the same time.
Progress
The text was updated successfully, but these errors were encountered: