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
- 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