Search Issue Tracker
Fixed in 1.1.0-preview.4
Votes
1
Found in [Package]
2019.3.15f1
2019.4
2020.2
Issue ID
1251720
Regression
No
[Input System] Buttons cannot be pressed after additively loading Scenes with additional Event Systems
Reproduction steps:
1. Open customer's attached project in "TestProject1251720.zip (32 KB)"
2. Open Scene1 and enter play mode
3. Press "Test Button For Input" to verify the button is working
4. Press "Load Scene2" button
5. New Scene will be loaded and Event System switched
6. Try pressing buttons
Expected result: the buttons work
Actual result: the buttons do not work
Reproducible with: Input System preview.1 - 1.1.0 (2019.4.10f1, 2020.1.5f1, 2020.2.0b2)
Could not test with 2018.4 because references get removed
Notes:
1. Each scene has its own Event System (it seems that buttons work when the Event System of that Scene is still active), meaning that multiple Event Systems are active at one time
2. Reproducible in build (tested Mac Standalone and iOS)
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
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
- Shader Graph template titles blink and render incorrectly in “Create New Shader Graph Asset” window
- Profiler Captures List foldouts do not open when clicked on the foldout title
Resolution Note (fix version 1.1.0-preview.4):
Fixed in Input System 1.1.0-pre.5 (verified in 2019.4.27f1)