Search Issue Tracker

Fixed in 2017.2.0f3

Fixed in 2017.2



Found in


Issue ID




Shader breaks and outputs 'unknown semantics "SV_InstanceID" specified for "instanceID"' (d3d9) error after upgrading to 2017.3



How to reproduce:
1. Open users attached project and Scene.unity file in 2017.1.0p2
2. Notice the Cube is blue and its "Diffuse" shader does not display any error in the Inspector
3. Open users attached project and Scene.unity file in 2017.3.0a2

Expected result: Cube is blue, its shader does not break and its "Diffuse" shader does not output any error
Actual result: Cube is white, its shader is broken. Three errors are output in "Diffuse" Inspector settings:
1. 'unknown semantics "SV_InstanceID" specified for "instanceID"' (d3d9 - 79)
2. 'Integer varying instanceID must be flat' (d3d9 - 79)
3. 'implicit cast from "half4" to "half3"' (d3d9 - 140)

Note: After reverting back to 2017.1, Shader stays broken and outputs this error: 'Unexpected identifier: UNITY_INSTANCING_BUFFER_START". Expected one of: typedef const void'

Regression introduced in - 2017.3.0a1
Reproducible with - 2017.3.0a2, 2017.3.0a1
Not reproducible with - 2017.2.0a4, 2017.1.0p2, 5.6.2p4

Comments (1)

  1. C33f99d9a6de7900834889aa58c27873?d=mm


    Dec 22, 2017 01:26

    This is not fixed in 2017.3.0f3 I'm experiencing the exact same issue:

    1. I created a project on 2017.2, render was ok on Editor
    2. Publish to Android, all right.
    3. Update Unity to 2017.3.0f3, render was ok on Editor
    4. When publishing to Android the render was white.
    5. Open the project on 2017.2, render white on editor and Android

    I get error log:
    Shader error in 'FOVV/Clip': Unexpected identifier "UNITY_INSTANCING_BUFFER_START". Expected one of: typedef const void inline uniform nointerpolation extern shared static volatile row_major column_major struct or a user-defined type at line 38

    I hade to rollback to 2017.2. and remake all the shader files.

Add comment

Log in to post comment

All about bugs

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