Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 5.6.X, 2017.1.X
Votes
29
Found in
5.6.0f3
Issue ID
899502
Regression
Yes
[Android] [iOS] GLSL shader compilation failure on some mobile devices
Steps to reproduce:
1) Download attached project 'UnityGLSLBug-Unity522.zip'
2) Build and run 'TestingGLES' scene on a devcie
Note: shader will fail to compile (sphere in a scene will be pink)
Expected result: Shader will be compiled without any issue (check attached image 'expected.png')
Actual result: GLSL shader compilation failure (check attached image 'actual.png')
Regression from:
5.6.0b3
Reproduced with:
5.6.0b3, 5.6.0f3, 2017.1.0b1
Not reproduced with:
5.5.3p1, 5.6.0b2
DUT:
Reproduced with:
GLES2 and GLES3
iPhone 6S iOS10.3
Samsung SM G925F (Galaxy S6 Edge), OS:6.0.1, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zeroltexx/zerolte:6.0.1/MMB29K/G925FXXU5DQA7:user/release-keys
Samsung GT N7100 (Galaxy Note 2), OS:4.4.2, CPU:armeabi-v7a, GPU:Mali-400 MP, Build:samsung/t03gxx/t03g:4.4.2/KOT49H/N7100XXUFNE1:user/release-keys
Not reproduced with:
Sony D6603 (Xperia Z3), OS:6.0.1, CPU:armeabi-v7a, GPU:Adreno (TM) 330, Build:Sony/D6603/D6603:5.1.1/23.4.A.1.264/2418263178:user/release-keys
Verizon SM G930V (Galaxy S7 Verizon), OS:7.0, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Verizon/heroqltevzw/heroqltevzw:7.0/NRD90M/G930VVRU4BQA2:user/release-keys
Comments (26)
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
AndrewRH
Aug 25, 2017 11:25
I found this issue mentioned in the 2017.2 beta 7 release notes:
"Shaders: Fixed GLSL shader compile errors due to lack of default precision specifier. (899502)"
AndrewRH
Aug 23, 2017 18:10
Just received another email from Unity saying "The issue was back-ported to 5.6.3p2 which is the next patch release", so we'll see :)
AndrewRH
Aug 22, 2017 10:34
Mmm still broken in 2017.1.0p4
AndrewRH
Aug 16, 2017 16:20
I just received email from Unity about this issue:
"
Thanks for reporting the issue.
We have fixed the GLSL shader compilation bug and it should not appear in the latest patch release version of Unity - 2017.1.0p4.
If you are still able to reproduce it on the latest version of Unity, please respond to this email.
We also plan to ship the fix in Unity in one of the forthcoming patch releases of Unity 5.6.0. This will be done soon, but currently we cannot exactly say in which version it will be fixed."
Mandelboxed
Aug 15, 2017 13:07
Is this actually fixed in any available version of Unity? It was initially reported as fixed in 2017.1 but was not, and now it says fixed in 2017.2. I just tried the available beta of 2017.2 and the problem persists.
AndrewRH
Jul 17, 2017 16:37
From Unity: "I have good news, this bug has been fixed and is going to be backported to 2017.1 and 5.6. I'll get back to you as soon as I know which patches will contain the fix." < great :) So hopefully it'll be coming in a patch release soon...
RenderHeadsSupport
Jul 10, 2017 11:25
Tested on 2017.1.0f1, still appears to be broken.
Tom-Goethals
Jun 28, 2017 06:19
Issue is still present in 5.6.1p3 and 5.6.2f1
studentvz
Jun 08, 2017 07:50
Instead of I develop more games and make money most time I only track and wait for new Unity releases and fixes, just to realize that when you fix one thing 3 more become broken. Please stop making fixes, thank you.
Tom-Goethals
Jun 07, 2017 11:02
Issue is still present in 5.6.1p1 and 5.6.1p2