Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4.9f1
2018.4.16f1
Issue ID
1252232
Regression
Yes
Shader in asset bundle built with Unity newer Version is broken on older Versions
How to reproduce:
1. Download and extract the attached "Bundle.zip" file
2. Navigate to <...>\case_1252232-Bundle\Bundle folder
3. Run this command to build Asset Bundle(instead of <path to version> type in the path to your 2018.4.23f1 version):
start-process "build-bundle-in-ver.bat" "<path to version>\editor"
4. After the build finishes run this command(instead of <path to version> type in the path to your 2018.4.9f1 version):
start-process "load-loader-in-ver.bat" "<path to version>\editor"
5. Enter Play Mode
Expected Behavior: The shader is working (attached screenshot "expected.png")
Actual Behavior: The shader is not working, the terrain is dark (attached screenshot "actual.png")
Reproducible with: 2018.4.16f1, 2018.4.23f1
Not Reproducible with: 2018.4.15f1
Note: There are path examples provided in the initial user's description. The report was tested only on the LTS, where it was introduced. The developer said that he will fill in the rest of the information if it is needed.
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
- OnApplicationPause pauseStatus is incorrect after losing focus on macOS
- Animator Blend Tree weight defaults to 0 for a frame when AnimationClipPlayable is created with script in Play Mode
- Memory gets allocated for GC each frame when using PrefabStageUtility.GetPrefabStage
- Light brightness gets intense until the 'Lightmap Encoding' quality is changed when baking Lightmap
- [Preset] Some properties cannot be excluded from Texture Importer Preset through the Inspector window
Resolution Note (fix version 2020.2):
Fixed an issue where older Unity versions inside the same Minor release couldn't load Shaders made by a newer patch version.