Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.1.0b1
Issue ID
901719
Regression
No
Shader errors appear in console after building "PostProcessing" asset on Vulkan
Reproduction steps:
1. Open project attached (VulkanCompilation.zip).
2. Build it for Vulkan.
Expected result: Build will be completed without any problem.
Actual result: Output in console:
Error: "Shader error in 'Hidden/Post FX/Screen Space Reflection': '' : compilation terminated at line 141 (on vulkan)"
Error: "Shader error in 'Hidden/Post FX/Screen Space Reflection': 'z' : vector field selection out of range at line 141 (on vulkan)"
Warning: "Shader warning in 'Hidden/Post FX/Screen Space Reflection': '' : all default precisions are highp; use precision statements to quiet warning, e.g.: at line 25 (on vulkan)"
Note: Instead of using attached project, you can also create new project and download PostProcessing from GitHub.
Reproduced on: 5.6.0p1, 2017.1.0b1
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
rad1c
Jun 17, 2018 12:43
Dev to issue: welcome back in 2018.1.2p1
SweatyChair
Jun 19, 2017 06:01
Upgraded to 5.6.1p4 and reimported the shader, still have the problem~
SweatyChair
Jun 19, 2017 03:02
2 Months later and still in 5.6.1.p1!
Updated Post Processing plugin and still not working...
biodam
May 31, 2017 19:58
Hello. Using 5.6.1f1 and got the same bug.
Here is a workaround by disabling vulkan:
https://forum.unity3d.com/threads/5-6-1-vulkan-shader-error.470690/#post-3090144
And here is the issue on github with people saying it is resolved on Unity 2017.1 beta. But will this come to 5.6?
https://github.com/Unity-Technologies/PostProcessing/issues/157
jiangzhen
May 27, 2017 10:35
5.6.1p1 exists
Maulwurfmann
May 24, 2017 18:52
Not resolved in 5.6.1f1 :(
Invertex
May 13, 2017 09:17
This issue still exists in 5.6.0p3 and 5.6.0p4.