Search Issue Tracker
Fixed in 12.0.1
Votes
0
Found in [Package]
12.0.0
Issue ID
1343570
Regression
No
[XPipeline] RenderPipelineGlobalSettings cannot be unassigned.
Repro steps:
1. Open an HDRP or a URP project
2. Go to Project Settings > Graphics > HDRP or URP Settings
3. Try to unassign the Global Settings asset by browsing and selecting 'None'
4. Observe the assed is still assigned
Expected outcome:
- The asset to be unassigned.
Notes:
- Since the asset is required, perhaps unassigning it could provide a warning message under it with a 'Fix It' button (akin to the HDRP Wizard settings) if the Global Settings asset belongs to the currently active render pipeline.
- There are use cases for unassigning this asset, like removing it for an inactive pipeline.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "List is empty" is poorly visible in the "Create Node" window
- [Android] GameObject with a custom shader becomes invisible when deployed with the Vulkan Graphics API
- “ReferenceError: Pointer_stringify is not defined” error is thrown when downloading a file
- GameObjects are not rendered when using a fragment shader with RWStructuredBuffer in URP
- [Profiler] The GPU Highlight module flags the frame before the spike when using DoInference in a coroutine
Add comment