Search Issue Tracker
Fixed in 6000.0.31f1
Fixed in 6000.0.X, 6000.1.X, 7000.0.0a16
Votes
6
Found in
6000.0.24f1
6000.1.0a1
Issue ID
UUM-85293
Regression
Yes
NRP RG - Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
Reproduction steps:
1. Open the attached “Unity6TestProject.zip” project
2. Open the “SampleScene”
3. Select the “PC_Renderer.asset” from the Project Window (Assets > Settings)
4. Enable the last Renderer Feature
5. Observe the Console
Expected result: No errors
Actual result: “Render Graph Execution error”, “Exception: Invalid version: 20" and “InvalidOperationException: Trying to use a texture (_InternalGradingLut) that was already released or not yet created. Make sure you declare it for reading in your pass or you don't read it before it's been written to at least once.” errors
Reproducible with: 2023.3.0a18, 6000.0.24f1, 6000.1.0a1
Not reproducible with: 2021.3.45f1, 2022.3.51f1, 2023.3.0a17
Reproducible on: Windows 10, Windows 11
Not reproducible on: no other environment tested
Note:
- Reproducible on a new URP project
Comments (3)
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
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
CsabaMarosi91
May 23, 2025 15:17
I also get this error in 6.1.1f1
This is NOT fixed.
It's thrown when:
- Usin SSAA
- Using my custom render feature with any injection point expect "After Renderein Transparant."
YohannV
Jan 08, 2025 18:26
Hello @OTTOCORRECT,
I just tried and cannot reproduce the issue anymore using 6000.0.31f1 with the latest URP package. Can you double-check and file a new bug report with a repro project if the issue still happens on your side?
OttoCorrect
Jan 05, 2025 16:58
Unfortunately, this isn't fixed in 6000.0.31f1 as mentioned above or in 6000.0.32f1. I'm still getting the same error