Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.5.0a9
6000.6.0a1
Issue ID
UUM-138269
Regression
No
Camera target RenderTexture intermittently stops receiving Graphics.DrawMesh output when in Play Mode
How to reproduce:
1. Open the attached “IN-136059” project
2. Go to Assets → My → Scenes and open scene “scene01”
3. Enter Play mode
4. Press “Esc” on the keyboard and toggle setting “push grass” off
5. Click apply
6. Toggle setting “push grass” on
7. Click apply again
8. Observe the Game view
Actual result: After some time, the grass displacement intermittently turns off and then on again
Expected result: The displacement camera should consistently render the Graphics.DrawMesh spot into the target RenderTexture
Reproducible with: 6000.5.0a9, 6000.6.0a1 (7dc703ab9bd8)
Could not test with: 2023.1.0a1, 6000.0.71f1, 6000.3.12f1, 6000.4.1f1 (custom package errors)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- When failure occurs, the grassDisplacement RenderTexture asset preview is black, indicating the RT is being cleared but not receiving the expected spot draw output
- spotDisplace.Update() continues executing
- Issue potentially related to render ordering/synchronization
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
Add comment