Template:Input/playstation motion sensors

Documentation for the above template (sometimes hidden from view).

Recognized values

• Camera
  • alias: Camera, Gyro Aiming, Gyro Aim, Gyroscope Aiming, Motion Sensor Aiming, Motion Sensor Aim, Motion Sensor Camera
• Cursor
  • alias: Cursor, Pointer
• Gesture
  • alias: Gesture, Action, Waggle, Shake

---

Additional Notes while assigning the values:

The vast majority of PC Games with Gamepad's Motion Sensor functionality tend to work on First-party PlayStation Controllers (DualShock 4 and DualSense Controller), this is because Sony's Input API happens to be the most commonly used input library for PlayStation Controllers, it also happens to be the most accessible way to implement Motion Sensor to your game (This applies to DualSense's Haptic Feedback and Adaptive Trigger support.) Unfortunately: it is also the least accessible for much smaller developers (requires a licensed SDK).

However: Some games may opt to use a third-party Input API or plugins (such as Steam Input, SDL Gamepad API, GameInput, Rewired Plugin for Unity Engine, etc.) that often than not: support Motion Sensors for additional Controllers.

To accommodate this, each major Controller Type table will have its own row for [Motion sensor support]. For instance, if a game supports Motion Sensors exclusively for PlayStation Controllers, set playstation motion sensors to true.

To properly use the rows, here are the recommendations for testing and verifying games that utilize the game's motion sensor features:

• You must use a First-Party PlayStation Controllers (DualShock 4, DualSense and DualSense Edge), This should help determine if a game can detect that specific Controller Type's Motion Sensors.
• Make sure the game's Motion Sensor features are enabled.

---

Reference:

Visit Template:Input/playstation motion sensors/Documentation to edit this text. (How does this work?)