Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X, 2023.1.X
Votes
0
Found in
2022.2.0a15
2022.2.0b2
2023.1.0a4
Issue ID
UUM-10038
Regression
Yes
[URP] UGUI disappears when using RenderObjects Renderer Feature which is executed in AfterRenderingPostProcessing event
Steps to reproduce:
1. Open the user's attached project "renderobjectsuiissue-2022.2.zip" and "SampleScene.unity"
2. Make sure that Render Objects renderer feature in URP-HighFidelity-Renderer is disabled
3. You can see "New Text" gui in game view
4. Enable Render Objects renderer feature in URP-HighFidelity-Renderer
5. You can see that "New Text" is disappears
Expected results: UI should be shown regardless of the RenderObjects renderer feature
Actual results: UI stops being rendered
Reproducible with: URP 14.0.2 - 15.0.0 (2022.2.0a14, 2022.2.0b2, 2023.1.0a4)
Not reproducible with: URP 10.9.0 - 14.0.2 (2020.3.37f1,2021.3.6f1, 2022.1.9f1, 2022.2.0a13)
Notes:
-If you change render mode of canvas to Camera space, it will be shown. This issue only affects screen-space overlay canvas
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
- Warning icon is cut off and misplaced in Inspector when selecting a Shader with a compiler warning
- AI Navigation Sample Scenes do not work and throws “InvalidOperationException”, “Curl error3”, “CrashReporter”, and “NullReferenceException” errors when using the new Input System Package (default) on a new project
- Bottom of Build Size window in Project Auditor becomes inaccessible when a monitor has a high display scaling
- AI Assistant fails to load account information when AI assistant is opened
- [Linux] Improve "GPUResidentDrawer" warning message to include actionable guidance when creating a new Unity project using Universal 3D Template
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.1.X):
There are no fixes planned for this Bug
Resolution Note (2023.1.X):
cannot reproduce on 23.1
Resolution Note (2022.2.X):
This issue could not be reproduced on 23.1 or 22.2