Search Issue Tracker
By Design
Votes
3
Found in
2018.3.0a4
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1133159
Regression
No
Standalone builds do not include instanced Terrain shaders if the Terrains are created dynamically at runtime.
How to reproduce:
1. Open the user-submitted project ("terrainbug.zip")
2. Open the "SampleScene" and enter Play Mode
3. Observe the Instanced terrain is working properly
4. Build the Project and observe the lack of a drawn terrain
5. Press "I" on your keyboard to toggle "drawInstanced" renderer off and observe the difference
Expected result: the terrain is rendered correctly both in the Editor and Standalone Build without any issues
Actual result: the terrain isn't rendered at all in the Standalone build when "drawInstanced" is set to true
Reproduced in: 2019.2.0a7, 2019.1.0b5, 2018.3.7f1, 2018.3.0a4
Couldn't test with: 2018.3.0a3, 2017.4.22f1 (these versions don't accept "drawInstanced" as a valid argument)
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note (2019.2.X):
Terrain shader is not included in the build if it's not used. Furthermore the instancing variant won't be included if instancing is not enabled on the terrain.
The right way to do runtime terrain creation is to include a Material referencing the terrain shader you want to use and enable instancing on it.