Search Issue Tracker
Fixed
Fixed in 6000.3.15f1, 6000.4.6f1, 6000.5.0b5, 6000.6.0a3
Votes
0
Found in
6000.3.11f1
6000.4.0b9
6000.5.0a8
6000.6.0a1
Issue ID
UUM-137626
Regression
Yes
"None" is only present when using HDRP Rendering Debugger's "Freeze Camera For Culling" dropdown
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/OutdoorsScene.unity” Scene
3. Open the Rendering Debugger window (Window > Analysis > Rendering Debugger)
4. Go to Rendering tab and open the "Freeze Camera For Culling" dropdown list
Expected result: Camera that is in the Scene is present
Actual result: The only option available is "None"
Reproducible with: 6000.2.0a4 (56df1dd3b76d), 6000.3.11f1, 6000.4.0f1, 6000.5.0b1, 6000.6.0a1
Not reproducible: 6000.0.71f1, 6000.2.0a3 (a53718ca3c62)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note:
Fixed in 6000.6.0a3
Resolution Note (fix version 6000.6.0a3):
Fixed in 6000.6.0a3
Resolution Note (fix version 6000.5.0b5):
Fixed in 6000.5.0b5
Resolution Note (fix version 6000.4.6f1):
Fixed in 6000.4.6f1
Resolution Note (fix version 6000.3.15f1):
Fixed in 6000.3.15f1