Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.3.6f1
2019.1.0a1
2019.2.0a1
Issue ID
1147095
Regression
No
In the Editor terrain is not rendered correctly when "Draw Instanced" on custom shader is enabled
How to reproduce:
1. Open attached project "NewDepthProject 2.zip" and scene "Main"
2. In the Hierarchy window, select "Terrain" object
3. In the Inspector window, "Terrain" component select "Terrain Settings" icon
4. Make sure "Terrain" -> "Basic Terrain" -> "Draw Instanced" is enabled
5. Enter Play mode
6. Observe Game View
Expected result: there are no visual differences between enabled and disabled "Draw Instanced", the terrain is visible
Actual result: the background becomes white, the sphere becomes black, the terrain is not visible
Reproducible with: 2018.3.13f1, 2019.1.0f2, 2019.2.0a12
Could not test with: 2017.4.26f1 due to the "Draw Instanced" not yet implemented
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [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
Resolution Note (2019.3.X):
Terrain instancing is not supported in Shader Replacement mode. I don't think we want to invest into this because:
* Shader replacement is an ancient feature. SRP provides a much powerful alternative to the solution.
* For a simple use case such as this one, it's better to just use the camera depth texture, which supports terrain instancing.
* Terrain rendering will become much different once Environment package is shipped.