Search Issue Tracker
Active
Votes
0
Found in
6000.0.57f1
6000.1.16f1
6000.2.3f1
6000.3.0b1
Issue ID
UUM-116762
Regression
No
Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
*Steps to reproduce:*
1. Open the attached “RenderTexture.zip” project from Google Drive link
2. Make sure “SampleScene” is open
3. Select “Main Camera” GO in Hierarchy window
4. In Inspector window wind Output Component
5. In “Output Texture” select “New Custom Render Texture” asset
6. Observe the Console and move mouse around the Editor
*Actual results:* Unclearable errors and warnings are spammed in the Console window and when moving the mouse in the Editor, rendering artefacts are visible
*Expected results:* No errors or warnings should spam in the Console, a warning box should show up, stating that the 3D textures with depth are no supported, no rendering artefacts should be visible in the Editor
*Reproducible with versions:* 6000.0.57f1, 6000.1.16f1, 6000.2.3f1, 6000.3.0b1
*Tested on (OS):* macOS Silicon, Sequoia 15.6 (M1)
Errors spammed:
- EndRenderPass: Not inside a Renderpass
- RenderTexture.Create failed: 3D textures with depth are not supported
- Renderer2D Pass/Light2D Volumetric Pass: Unable to find surface for attachment 0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment