Search Issue Tracker
Won't Fix
Fixed in 6000.3.0a2
Votes
0
Found in
6000.0.48f1
6000.1.1f1
6000.2.0a10
6000.3.0a1
Issue ID
UUM-103981
Regression
No
InvalidOperationException occurs when binding 3D Rendertexture or 2D RenderTextureArray as Multiple Render Texture in RenderGraph
How to reproduce:
1. Open the attached “IN-99904” project
2. Observe the Console window
Expected result: No errors appear
Actual result: An “InvalidOperationException: Trying to SetRenderAttachment on a texture that is already used through UseTexture/SetRenderAttachment” error appears
Reproducible in: 6000.0.0f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Could not test with: 2021.3.51f1, 2022.3.61f1, 6000.0.0b16 (RenderGraph features not supported)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Version 6000.2.0a10 also displays a “RenderGraph Execution Error”
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:
This will be handled as a feature request.