Search Issue Tracker
Fixed in 10.x
Votes
0
Found in [Package]
9.0.0 preview.33.
Issue ID
1263347
Regression
No
[HDRP] SetRenderTexture called on property errors on saving DefaultCompositionGraph after assigning Sample Virtual Texture node
SetRenderTexture called on property errors are thrown continuously on saving DefaultCompositionGraph after assigning Sample Virtual Texture node to Virtual Texture property.
Steps to repro:
1. Create a new HDRP template project
2. Windows > Render Pipeline > HD Render Pipeline Compositor.
3. Enable Compositor > Close the Compositor window.
4. Assets/Compositor/DefaultCompositionGraph > Open.
5. Blackboard > Add Virtual Texture > Drag it to Graph Editor.
6. Assign Sample Virtual Texture(VT) > Save the Graph.
Actual Result:
SetRenderTexture called on property errors in the console.
Expected Result:
No error in the console.
Reproducible in:
2020.2.0a18, 2020.1.0b16, 2020.1.0b13 with Package version 9.0.0 preview.33
Note: HDRP Compositor window introduced in 9.0.0 preview.33.
Environment:
Occurring only on Windows.
Stacktrace:
SetRenderTexture called on property 'Layer0' which is part of a stack. Stack values cannot be with render textures.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
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 (fix version 10.x):
Fixed in: Package version: 10.1.0