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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment