Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1312569
Regression
No
[AssetBundles] [Shaders] Terrains loaded from Assetbundles does not render properly on the player
Reproduction steps:
1. Open attached project "hdrp_terrain8layers.zip" and scene "SampleScene"
2. Run and Build
3. In Build, observe the two loaded terrains
Expected result: No differences
Actual result: The terrain on the right is not rendered properly
Reproducible with: 2020.2.4f1, 2021.1.0b6, 2021.2.0a4
Could not test with: 2018.4.31f1, 2019.4.20f1 (compilation errors)
Note:
Issue does not reproduce in the Editor
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note:
Shaders built with the BuildPipeline.BuildAssetBundles api require special case handling in order for them to build all the included shader features. Such as setting the shader stripping options in the Graphics Settings inspector, or using a Shader Variant Collection to provide necessary shader features to the asset bundle build pipeline. This process was changed with the Scriptable Build Pipeline package to removed the need for the special case handling.