Search Issue Tracker
Fixed
Fixed in 1.14.1
Votes
0
Found in [Package]
1.7.0
1.11.2
1.14.0
Issue ID
ISXB-1152
Regression
No
Default Button Press Point value set in the Editor is not respected and always forced to 0.5 value in m_DefaultButtonPressPoint
Steps to reproduce:
1. Open the attached "buttonPressPoint.zip"
2. Connect a gamepad (needs a right trigger)
3. Enter Play Mode
4. Press the right trigger on the controller and observe the values printed
5. NOTICE: isPressed becomes true at 0.5
5. Navigate to "Project Settings > Input System Package Settings" and observe Default Button Press Point set to 0.15 value
Expected results: Default Button Press Point value set in the Editor is respected
Actual results: Default Button Press Point value set in the Editor is not respected and always forced to 0.5 value
Reproducible with: Input System 1.7.0 (2021.3.45f1), 1.11.2 (2022.3.52f1, 6000.0.25f1, 6000.1.0a2)
Testing Environment: Windows 11
Not reproducible on: no other environment tested
Notes:
-Issue does not reproduce if Default Button Press Point value is set during runtime (while already in Play Mode)
-m_DefaultButtonPressPoint = 0.5f is forced in the Input System package InputSettings.cs script line 773
-OpenXR Plugin ActionToHaptics.cs script is modified to compare against action.Performed and action.WasPressedThisFrame
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Blank, Light-Themed "Create Node" window becomes visible on the next project open
- UI Elements/Layout inconsistencies in the Particle System component
- The Game view and Scene view fail to render when launching the Editor with a maximized Render Graph Viewer window
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
Add comment