Search Issue Tracker
Fixed in 10.0.0-preview1
Fixed in 7.5.0, 8.3.0, 9.0.0-preview.57
Votes
0
Found in [Package]
9.0.0, 8.1.0
Issue ID
1246256
Regression
No
[URP] RenderObject name does not reflect inside CustomForwardRendererData asset on renaming in the Inspector
RenderObject name does not reflect inside CustomForwardRendererData asset on renaming in the Inspector.
Steps to repro:
1. Create a new URP Project.
2. Project Window > Right Click > Create Rendering > Forward Renderer.
3. Add Renderer Feature > Render Objects.
4. Change the name of the New Render Objects component.
Actual Result:
RenderObject name does not reflect inside CustomForwardRendererData asset.
Expected Result:
RenderObject name should reflect inside CustomForwardRendererData asset
Reproducible in:
2020.2.0a11, 2020.1.0b9 with Package Version 9.0.0, 8.1.0, 8.0.1, 7.1.8.
Environment:
Occurring on Windows 10 & Mac 10.15.
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
- 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
Resolution Note (fix version 10.0.0-preview1):
Fixed in Package version 10.0.0-preview.26.
Resolution Note (fix version 9.0.0-preview.57):
Fixed RenderObject to reflect name changes done in CustomForwardRenderer asset.
Resolution Note (fix version 8.3.0):
Fixed RenderObject to reflect name changes done in CustomForwardRenderer asset.
Resolution Note (fix version 7.5.0):
Fixed RenderObject to reflect name changes done in CustomForwardRenderer asset.