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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment