Search Issue Tracker
Fixed
Fixed in 1.14.1
Votes
1
Found in [Package]
1.13.1
1.14.0
Issue ID
ISXB-1446
Regression
Yes
"Index out of range" and "NullReferenceException" Input System errors when combining InputTestFixture with Scene loading tests on subsequent runs
Reproduction steps:
1. Open the attached “IN-93841.zip” project
2. Open the “Test Runner” Window (Window > General > Test Runner)
3. Go to the “PlayMode” tab
4. Click “Run All”
5. Observe no errors in the Console
6. Click “Run All” again
7. Observe the Console
Expected result: No errors
Actual result: “Map index out of range in ProcessControlStateChange”, “Control index out of range”, “Binding index out of range” errors and “NullReferenceException” exceptions are thrown
Reproducible with: 1.8.2 (6000.0.40f1, 6000.1.0b8, 6000.2.0a5), 1.13.1 (6000.0.40f1, 6000.1.0b8, 6000.2.0a5)
Not reproducible with: 1.8.1 (2022.3.59f1, 6000.0.40f1, 6000.1.0b8, 6000.2.0a5) , 1.8.2 (2022.3.59f1), 1.13.1 (2022.3.59f1)
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: No other environment tested
Note:
- Does not reproduce if Domain reload is enabled (Edit > Project Settings > Editor > When entering Play Mode > Reload Domain and Scene) or if the “UIDocument” GameObject in the “Playground” Scene has “Panel Settings” set to 'None'
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
Resolution Note (fix version 1.14.1):
Fixed errors caused by recreation of DefaultInputActions instance in InputSystemProvider