Search Issue Tracker
Fixed in 10.2.2
Votes
1
Found in [Package]
10.0.0-preview.27
Issue ID
1281049
Regression
No
[HDRP] Frame Debugger shows draw calls when all settings in Frame Settings are disabled
How to reproduce:
1. Open attached "case_1281049 FrameSettingsIssue" project
2. Open Assets/TESTSCENE
3. Open Frame Debugger
4. Press Enable in the Frame Debugger
5. Observe the Main List
Expected result: No draw calls are in the Main list
Actual result: There are draw calls in the Main list
Reproducible with: 7.5.1(2019.4.11f1), 8.2.0(2020.1.6f1), 10.0.0-preview.27(2020.2.0b5)
Can't test: 2018.4 (No Frame Settings)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 10.2.2):
Shows only one Post Processing draw call in the Frame debugger, that's expected. Fixed in HDRP 10.2.2 and above, available in Unity 2020.2.0b12 and above