Search Issue Tracker
Fixed
Fixed in 1.9.0
Votes
0
Found in [Package]
1.7.0
1.8.0-pre.1
1.8.0-pre.2
Issue ID
ISXB-718
Regression
No
Errors are thrown when entering the Play Mode after modifying the InputActions asset with Domain Reload turned off
Reproduction steps:
1. Open the attached “BugRepro“ project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. In the Game View click the button
5. Exit the Play Mode
6. Open “Assets/InputActions.inputactions” asset
7. Select “Point” in Actions
8. In Action Properties click the + next to “Processors” and add “Scale Vector 2”
9. Click the “Save asset” button
10. Enter the Play Mode
11. Try to interact with the button in the Game View
12. Observe the Console window
Expected result: No errors are thrown
Actual result: Errors are thrown
Reproducible with: 1.7.0 (2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0a14),
1.8.0-pre.1 (2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0a14),
1.8.0-pre.2 (2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment