Search Issue Tracker
By Design
Votes
0
Found in
6000.0.29f1
6000.1.0a6
Issue ID
UUM-89975
Regression
Yes
Error "InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings." is present when using UI Toolkit and New Input System
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/dadasd.unity” Scene
3. Enter the Play Mode
4. Click on Game view
Expected result: No Errors exist
Actual result: Error “InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings.” is present
Reproducible with: 2023.2.0a16, 6000.0.29f1, 6000.1.0a6
Not reproducible with: 2022.3.53f1, 2023.2.0a15
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- This does not reproduce with Active Input Handling set to “Both” or “Input Manager (Old)“
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
Add comment