Search Issue Tracker
By Design
Votes
1
Found in
5.2.2f1
Issue ID
742519
Regression
No
[RenderTexture|Compute] RenderTexture used in ComputeShader does not work in Standalone (works in the Editor)
To reproduce:
- Open attached project
- Open "WaterEffect" scene and play
- Notice RenderTexture rendered correctly
- Build this scene and play
Actual behavior: notice that screen is white
Expected behavior: RenderTexture should be rendered as in the editor
Additional notes:
All shaders are being compiled into the build.
The plane is being assigned a redertexture at runtime and another render texture is being created to take the input from the camera filming the scene. both are being passed into a computshader and a wave effect is being applied to the output render texture that is shown on the plane.
The builds log sometimes has a line that says the render texture is being released from the camera.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Add comment