Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2.0a1
2021.3.5f1
2022.1.8f1
2022.2.0a18
2023.1.0a1
Issue ID
UUM-7793
Regression
Yes
Terrain is missing the Hidden/TerrainEngine/Details/WavingDoublePass shader when AssetBundles are built in older Unity Versions
How to reproduce:
1. Open the user's attached project
2. Open Assets > Scenes > SampleScene.unity
3. Enter Play Mode and press spacebar
4. Observe the Console window and the terrain in the Game view
5. The "Hidden/TerrainEngine/Details/WavingDoublePass (UnityEngine.Shader) is here" message is present in the Console window
6. Go to File > Build Settings and press Build And Run
7. Observe the terrain in the Player and press spacebar
8. Go to the Player.log and look for the "Hidden/TerrainEngine/Details/WavingDoublePass (UnityEngine.Shader) is here" message
Expected result: The WavingDoublePass shader isn't missing and AssetBundles built with older Unity versions should still work
Actual result: The WavingDoublePass shader is missing and the terrain is different
Reproducible with: 2021.2.0a1, 2021.3.5f1, 2022.1.8f1, 2022.2.0a18, 2023.1.0a1
Not reproducible with: 2019.4.40f1, 2020.3.36f1, 2021.1.28f1
Reproducible on: Windows 10
Notes:
1. The tested AssetBundle is built using Unity 2019.4.30f1
2. The WavingDoublePass shader seems to be replaced by “Legacy Shaders/Diffuse shader” in the Frame Debugger ("FrameDebugger_Player_ActualResult.png")
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
We've examined the AssetBundles and do not find any problem with the format or contents. Rather this appears to a case where 2020 version of Unity cannot work with serialized terrain objects from 2019. Although we strive to hvae backward compatibility sometimes there are major changes in features that require that AssetBundles be rebuilt. So the recommended resolution is to rebuild the AssetBundles with a new version of Unity.