Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.6f1
2023.1.7f1
2023.2.0b3
Issue ID
UUM-45338
Regression
No
Renderer Feature sub-assets aren't updated when removing or adding them
How to reproduce:
1. Open the attached “AR Shader Demo.zip“ project
2. Select “URP-HighFidelity-Renderer“ asset in the Settings folder
3. Remove the SSAO Renderer Feature
Expected result: The SSAO sub-asset is removed
Actual result: The SSAO sub-asset is not removed
Reproducible with: 2021.3.29f1, 2022.3.6f1, 2023.1.7f1, 2023.2.0b3
Reproduced on: macOS 13.4.1 (Intel), Windows 10 (by reporter)
Note: The sub-asset should also be updated (created) when adding a Render Feature to the “URP-HighFidelity-Renderer“ asset
-
DevDunk
Aug 15, 2023 07:25
I think this is a pretty major issue. It is basically misinformation to the end user, especially since it works fine in older Unity versions. Would be disappointing if a clearly visual issue like this will never be fixed. It can already be fixed by adding a '*' on the tab like Shader Graph does, or just autosave when a change in the inspector is made instead of only while CTRL S.
It doesn't seem like a hard issue to fix either.
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
- [VFX] Missing Expand Toggle with Output Slot
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
Resolution Note:
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.