Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0b8
Issue ID
1097465
Regression
No
Sprites rendered through Command Buffers not displayed until rendered once with a default Renderer
Sprites rendered through Command Buffers not displayed until rendered once with a default Renderer
Steps to repro:
1. Open the scene and do not activate any components.
2. Enter the play mode.
3. Note how there are no sprites displayed. Command Buffer tries to render the sprites on the left to no avail.
4. Try enabling Sprite Renderer components on the sprites on the right. Notice how the moment the sprites are rendered with default renderers they start working fine with Command Buffers.
5. Exit and Re-enter the play mode again.
6. Notice how the Unpacked sprite still works while the Packed sprite needs rendering again to start working with Command Buffers.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment