Search Issue Tracker
Fixed in preview-6.9.0
Votes
0
Found in [Package]
4.1.0-preview
Issue ID
1195465
Regression
No
[HDRP][URP][macOS] Content of render target is invisible in Frame Debug window
How to reproduce:
1. Create new HDRP project
2. Select Window -> Analysis -> Frame Debugger
3. Click Enable button in Frame Debug window
4. Select the 'Render Additional Shadows' draw call
Expected result: Content of Render Additional Shadows is visible in Frame Debug window
Actual result: Content of Render Additional Shadows is invisible in Frame Debug window
Reproducible with: 2018.4.12f1(4.1.0-preview)
Not reproducible with: 2019.2.12f1(6.9.0, 6.9.2), 2019.3.0b10(7.0.1, 7.1.2), 2020.1.0a12(7.0.1, 7.1.2)
Could not test: 2017.4.34f1 because HDRP is not introduced
Notes:
- Not reproducible with built-in pipeline
- Not reproducible on Windows
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
Add comment