Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0a1
2018.4
2018.4.11f1
2019.2
2019.3
2020.1
Issue ID
1195008
Regression
Yes
[Mobile][AssetBundles] Shadows and/or Scene Objects are not loaded when loading a scene from an Asset Bundle built in 2017.x
Reproduction steps:
1. Open "1195008" project
2. Notice that the cube in the scene (LightTest) casts a shadow on the plane
3. Build & Run for Android
4. Notice that the cube doesn't cast a shadow on the plane
5. Check the logcat for "GLSL link error"
Expected Result: Shadows/Scene objects should be present when loading a scene from an Asset Bundle built in 2017.x
Actual Result: Shadows are missing and/or Scene Objects are not loaded when loading a scene from an Asset Bundle built in 2017.x
Reproduced with: 2020.1.0a12(No Scene loaded), 2019.3.0b10(No Scene loaded), 2019.2.12f1(No Scene loaded), 2018.4.12f1 (No Shadows loaded, GLSL error), 2018.3.14f1 (No Shadows loaded, GLSL error), 2018.3.0a1(No Scene loaded)
Did not reproduce on: 2018.2.21f1, 2018.1.9f2, 2017.4.34f1
"Error: Uniform _WorldSpaceCameraPos precision mismatch with other stage.
Adreno : Error: Linking failed.
GLSL link error: Error: Uniform _WorldSpaceCameraPos precision mismatch with other stage.
Error: Linking failed."
Reproduces with: OpenGLES3, Vulkan, Metal; Mono, IL2CPP;
Doesn't Reproduce with: OpenGLES2;
Repro Devices:
iPad 7 gen (iOS 13.1)
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android 10, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00099, Google Pixel XL (Pixel XL), Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00147, Razer Razer Phone (Phone), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00127, Lge Nexus 5X (Nexus 5X), Android 8.0.0, CPU: Snapdragon 808, GPU: Adreno (TM) 418
VLNQA00170, Google Pixel 2 (Pixel 2), Android 10, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00262, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Shaders had a breaking change between 2017 and 2018 that requires them to be rebuilt in order to be loaded.