Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0p4
Issue ID
976390
Regression
No
Compute shader with volume texture fails to dispatch
Reproduction steps:
1. Download project "ComputeTest2.zip" and open in Unity
2. Open scene ComputeTest
3. Enter Play mode (notice there are no snow particles visible)
4. Analyse frame with Unity Frame Debugger (notice the compute shader dispatch calls appear to be present)
5. Do a standalone Windows build and analyze a frame using the Visual Studio Graphics Debugger (the particle update dispatch calls are not visible - only one dispatch call, which is filling the wind volume with (1, 0, 0) every frame)
Expected: for snow to be visible and blown sideways
Actual: snow is not visible
Reproduced on: 5.5.6f1; 5.6.5f1; 2017.1.3f1; 2017.2.1p1; 2017.3.0p1; 2018.1.0b1
Note:
Removing the sampling of the wind volume from the particle update shader makes everything work fine (comment SnowUpdate.compute line - "vel += _WindVolume[uint3(0, 0, 0)].xyz;").
Works fine on Xbox One.
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