Search Issue Tracker
Not Reproducible
Votes
0
Found in
2021.3.37f1
2022.3.26f1
2023.1.13f1
2023.2.0f1
6000.0.1f1
Issue ID
UUM-70845
Regression
No
[Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Steps to reproduce:
1. Download attached project and open in Unity
2. In Rendering Debugger, select the Lighting tab
3. Press Play button
4. In Rendering Debugger, select Lighting Debug Mode from None to Difusse Lighting
Observe the Console:
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.
Actual results: InvalidOperationException in the Console. Game View is not affected by the selected debug mode
Expected results: No InvalidOperationException in the Console. Game View is rendered accordingly to the selected Lighting Debug Mode.
Reproducible with versions:
2021.3.37f1, 2022.3.26f1, 2023.1.13f1, 2023.2.0f1, 6000.0.1f1
Tested on (OS):
MacBook Pro (16-inch, 2021), CPU: Apple M1 Max, Memory: 64 GB, macOS: Ventura 13.3.1 (a) (22E772610a)
Notes:
- Works fine with the Old input system.
- To change the input system go to Project Settings >> Player >> Configuration >> Active Input Handling(dropdown menu)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Not reproducible with latest version