Search Issue Tracker
Fixed in 1.1.0-pre.6
Votes
0
Found in [Package]
1.1.0-pre.5
Issue ID
1350139
Regression
No
Inconsistent ENABLE_PROFILER scripting defines in InputManager.cs when using Profiler.BeginsSample and Profiler.EndSample
How to reproduce:
1. Create a new project using the default 3D template
2. Import the "Input System" package
3. Open the package's "InputManager.cs" script
4. Inspect the "ENABLE_PROFILER" defines
Expected result: Scripting define is used for all Profiler.BeginsSample and Profiler.EndSample calls
Actual result: Scripting define is only used for some Profiler.BeginsSample and Profiler.EndSample calls and can result in an error "Non matching Profiler.EndSample (BeginSample and EndSample count must match): Transparents"
Reproducible with: 1.1.0-pre.5 (2019.4.29f1, 2020.3.16f1, 2021.1.17f1, 2021.2.0b5, 2022.1.0a4)
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
- Threads dropdown in the Profiler is not scrollable even when not all options in the list are visible
- Memory leak when a lot of Particle Systems instantiated while Profiler is open
- "ArgumentOutOfRangeException" error is thrown when trying to delete letters from an RTL TextField when using the Advanced Text Generator
- Rendering issues when using the Triplanar Node in ShaderGraph
- Entering a big number into the "Target Frames Per Second" in Profiler's Preferences inconsistently converts it either to 1FPS or 1000FPS
Resolution Note (fix version 1.1.0-pre.6):
Fixed package version available in Unity 2019.4.0f1 and above