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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment