Search Issue Tracker
By Design
By Design in 6000.2.X
Votes
3
Found in
6000.0.49f1
6000.1.4f1
6000.2.0b2
Issue ID
UUM-105679
Regression
Yes
Error “Unable to add Renderer to the Scene after Culling.“ is present when Non-draw instanced Terrain is rendering in a camera within the rendering callbacks of another camera in Built-In Render Pipeline
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/OPEN_ME.unity” Scene
3. In Hierarchy, under “Enable Mirror to break :(" GameObject, select “Mirror"
4. In Inspector, enable the GameObject
5. Enter the Play Mode
Expected result: No Errors exist
Actual result: Error “Unable to add Renderer to the Scene after Culling.“ is present
Reproducible with: 2023.2.0a2 (0ded2ee3bb66), 6000.0.49f1, 6000.1.4f1, 6000.2.0b2
Not reproducible with: 2022.3.62f1, 2023.2.0a1 (6c240b609079)
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
The ability to inject render commands during these callbacks was never intended, and it was very easy to trash the render state which would result in a hard crash.
Therefore new functionality was introduced to block certain API calls from being available when using them was unsafe. Trying to call these functions during critical states results in an error like you are seeing now.
We apologize for the inconvenience.
Resolution Note (6000.2.X):
The ability to inject render commands during these callbacks was never intended, and it was very easy to trash the render state which would result in a hard crash.
Therefore new functionality was introduced to block certain API calls from being available when using them was unsafe. Trying to call these functions during critical states results in an error like you are seeing now.
We apologize for the inconvenience.