Search Issue Tracker
Fixed
Fixed in 1.14.1
Votes
1
Found in [Package]
1.14.0
Issue ID
ISXB-1493
Regression
Yes
Input System UI Input Module action values set to "None" when disabling the component in Play mode
How to reproduce:
1. Open the attached “IN-98268_InputTest“ project
2. Open the “SampleScene“
3. Enter Play mode
4. In the Hierarchy window, select the “EventSystem“ GameObject
5. In the Inspector window, disable the Input System UI Input Module component
6. Observe the results in the Inspector window
Expected result: The Input System UI Input Module component values stay the same
Actual result: The Input System UI Input Module component action values (for example, “Point“, “Left Click“) turn to “None“
Reproducible with: 1.13.0 (6000.0.37f1, 6000.0.38f1), 1.14.0 (6000.0.45f1, 6000.1.0b13, 6000.2.0a8)
Not reproducible with: 1.7.0 (2021.3.50f1), 1.11.2 (2022.3.60f1), 1.12.0 (6000.0.37f1)
Reproducible on: MacOS 15.3 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested
Notes:
- This issue only reproduces in Play mode
- The input values restore to their correct values after exiting Play mode. Re-enabling the component during Play mode does not restore the values
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment