Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.4
2019.4
2020.1
2020.1.7f1
2020.2.0a1
Issue ID
1282195
Regression
No
Custom Render Textures are not rendered in a Standalone Build
How to reproduce:
1. Open the attached project named "CustomRenderTextureMaterialIssue"
2. Open the SampleScene and enter Play mode
3. Observe that the Plane is rendered green
4. Build the project
5. Launch the build and observe the color of the Plane
Expected result: The plane is rendered green same as in Play mode
Actual result: The plane is rendered black
Reproducible with: 2018.4.29f1, 2019.4.13f1, 2020.1.0a1, 2020.1.11f1, 2020.2.0a1, 2020.2.0a7
Fixed in: 2019.4.14f1, 2020.1.12f1, 2020.2.0a8, 2020.2.0b10, 2021.1.0a3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in - 2019.4.14f1, 2020.1.12f1, 2020.2.0a8 and above