Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in [Package]
9.0.0, 8.1.0
Issue ID
1246274
Regression
No
[URP] Renderer Object does not add inside CustomForwardRendererData asset on undoing after removing from the Inspector
Renderer Object does not add inside CustomForwardRendererData asset on undoing after removing from the Inspector.
Steps to repro:
1. Create a new URP Project.
2. Project Window > Right Click > Create Rendering > Forward Renderer.
3. Add Renderer Feature > Add two Render Objects.
4. Remove all added Renderer Objects.
5. Press CTRL + Z.
Actual Result:
Renderer Object does not add inside CustomForwardRendererData asset.
Expected Result:
Renderer Object should add inside CustomForwardRendererData asset.
Reproducible in:
2020.2.0a11, 2020.1.0b9, 2019.3.0f3 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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Resolution Note:
The proper fix for this bug is to move away from subassets and implement polymorphic serialization. However PolymorphicSerialization has some issues that prevent us to use it. Postponing the bug marking the issue to be reopened when the dependent serialization issue is fixed.