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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.