Search Issue Tracker
Fixed
Votes
0
Found in
5.5.1f1
Issue ID
896798
Regression
No
Custom shader produces incorrect results when built with GLES3 Graphics API
To reproduce:
1.Download and open "nmx_from_outsource.zip" project.
2.Build and run "Test_01" scene on a device.
3.Notice that sphere looks differently from the one in the editor.
Expected result: Shader is compiled correctly on device and sphere looks the same as in the editor.
Actual result: Shader looks incorrect when project is built on device.
Reproduced with : 5.5.3f1, 5.6.0f3, 2017.1.0a6
DUT:
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
Sony D6603 (Xperia Z3), OS:5.1.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:6.0.1, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:Verizon/heroqltevzw/heroqltevzw:6.0.1/MMB29M/G930VVRU2APG3:user/release-keys
Notes: Everything works as intended when built with GLES2 Graphics API on Galaxy S6 Edge and Xperia Z3. However, on Galaxy S7 Verizon on both GLES3 and GLES2 issue reproduces. Also reproduced on IOS device Apple Iphone 6s.
Verified with: 2017.2.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment