Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
7.1.5 - 7.1.7
Issue ID
1205902
Regression
Yes
Terrain Holes are not rendered in Build when HDRP is installed
Steps to reproduce:
1. Open the attached project named "Case_1205902"
2. Open SampleScene
3. Observe the visible Terrain holes in the Game view
4. Build the project and open the Build or open the attached "BuildHDRP7.1.7"
5. Observe the Build window
Expected behavior: The Build renders the Terrain hole the same way as in Editor "Build_2019.3.0a10_HDRP_7.0.0"
Actual behavior: No Terrain is rendered in the Build
Reproducible with: 2019.3.0b4(HDRP 7.1.5 became available), 2019.3.0f4, 2020.1.0a18
Not reproducible with: 2019.3.0a1, 2019.3.0b3
Could not test with: 2017.4, 2018.4, 2019.2(Terrain Hole functionality was introduced in 2019.3)
Not reproducible with package versions: 7.0.0
Reproducible with package versions: 7.1.5, 7.1.7
Could not test package versions: 7.1.1, 7.1.2
Notes:
Build targets tested - Windows x86 and Windows x86_64
Graphics APIs tested - D3D11, D3D12, Vulkan
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
This is not a bug but wrong Scriptable Rendering Pipeline settings setup. Unfortunately, it is not possible to add the requested warning message in the inspector window. However, we have added this message in the Terrain/Lit shader.