Search Issue Tracker

Fixed in Unity 2017.2

Votes

0

Found in

2017.1.0b1

Issue ID

901719

Regression

No

Shader errors appear in console after building "PostProcessing" asset on Vulkan

Shaders

-

-

Priority: 7Not yet prioritized for a release

-

Severity: 3Workaround is possible

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

Comments (6)

  1. De538f6303bc4c5fbed82b7dcefab0a9?d=mm

    SweatyChair

    Jun 19, 2017 06:01

    Upgraded to 5.6.1p4 and reimported the shader, still have the problem~

  2. De538f6303bc4c5fbed82b7dcefab0a9?d=mm

    SweatyChair

    Jun 19, 2017 03:02

    2 Months later and still in 5.6.1.p1!

    Updated Post Processing plugin and still not working...

  3. 2a93f5da1916a018b6b54de9530279e2?d=mm

    rs233

    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

  4. E003b0f4b9db80b2c2d25590bc7ea735?d=mm

    jiangzhen

    May 27, 2017 10:35

    5.6.1p1 exists

  5. 55ec6bb515359be7fd231666c299cbd1?d=mm

    Maulwurfmann

    May 24, 2017 18:52

    Not resolved in 5.6.1f1 :(

  6. 6ada54c086e289ddb671414d0e85e259?d=mm

    Invertex

    May 13, 2017 09:17

    This issue still exists in 5.6.0p3 and 5.6.0p4.

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.