Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.

Postponed

Votes

0

Found in

5.4.0f3

Issue ID

828953

Regression

No

Trigger input value is 0 on startup on OSX but becomes -1 after pressing the trigger

Input

-

Controller trigger input is treated differently across different platforms - on OSX the default value of triggers is 0, but after they are pressed it becomes -1. This does not occur on Windows, where the default is -1 all the time.

Steps to reproduce:
1) Open the attached project (TriggerTest.zip).
2) Open scene 'Test'.
3) Connect a game controller to the Mac (like a DualShock 4).
4) Press play.
- The input values of triggers are displayed on the screen, they should be equal to 0.
5) Push the triggers.

The default input value (when the triggers are not pressed) becomes -1 instead of 0.

Expected behavior: the default value remains the same before and after pressing the trigger.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.