Search Unity

  1. Dismiss Notice
  2. All Pro and Enterprise subscribers: find helpful & inspiring creative, tech, and business know-how in the new Unity Success Hub. Sign in to stay up to date.
    Dismiss Notice
  3. Dismiss Notice

WebGL Unsupported Shader Errors in Chrome and Firefox

Discussion in '5.2 Beta' started by muzzythom, Sep 2, 2015.

  1. muzzythom

    muzzythom

    Joined:
    Dec 1, 2014
    Posts:
    17
    In chrome (everywhere) and on firefox (only on mac), we get a bunch of messages pertaining to unsupported shaders.

    The specific messages are:

    Code (csharp):
    1. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'FORWARD' has no vertex shader
    2. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'FORWARD_DELTA' has no vertex shader
    3. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'SHADOWCASTER' has no vertex shader
    4. WARNING: Shader Unsupported: 'Standard (Specular setup)' - Pass 'DEFERRED' has no vertex shader
    5. WARNING: Shader Unsupported: 'Standard (Specular setup)' - All passes removed
    6. WARNING: Shader Unsupported: 'Standard' - Pass 'FORWARD' has no vertex shader
    7. WARNING: Shader Unsupported: 'Standard' - Pass 'FORWARD_DELTA' has no vertex shader
    8. WARNING: Shader Unsupported: 'Standard' - Pass 'SHADOWCASTER' has no vertex shader
    9. WARNING: Shader Unsupported: 'Standard' - Pass 'DEFERRED' has no vertex shader
    10. WARNING: Shader Unsupported: 'Standard' - All passes removed
    On Chrome we also get several messages of "WebGL: INVALID_OPERATION: texImage2D: incompatible format and internalformat"

    The end result is that the UI has several solid black areas where there should be color or texture (I'm not positive about this, but I suspect that it's any UI texture where there is no alpha channel). (This is visible on the first attached image, and the 5.1 version is the 3rd attached image)

    The standard shader also appears to be not applying light, resulting in an extremely dark scene. (This is visible on the second attached image, where the 5.1 rendering is the 4th attached image).
     

    Attached Files:

  2. Marco-Trivellato

    Marco-Trivellato

    Unity Technologies

    Joined:
    Jul 9, 2013
    Posts:
    1,654
    I don't think this is a problem we are already aware of. Could you please submit a bug report ?
     
  3. muzzythom

    muzzythom

    Joined:
    Dec 1, 2014
    Posts:
    17
    I had tried to submit one before, but hadn't been sure it went through. I guess it had not.

    Anyway, this has been submitted as case 725756.
     
  4. Marco-Trivellato

    Marco-Trivellato

    Unity Technologies

    Joined:
    Jul 9, 2013
    Posts:
    1,654
    we received the bug report. thanks!
     
  5. MartijnDekker

    MartijnDekker

    Joined:
    Feb 13, 2015
    Posts:
    8
    I have the same problem, perhaps this is introduced in version 5.2 ?
     
  6. muzzythom

    muzzythom

    Joined:
    Dec 1, 2014
    Posts:
    17
    Just tried using Unity 5.2f3 (the 5.2 release). The issue is still present in most places, but it now works in Chrome developer channel on windows.

    Just tried it on the browsers I have immediately available to me:

    - Chrome developer channel on windows (Version 47.0.2503.0 dev-m) works.
    - Firefox v39.0 and v40.0.3 on windows works (as before).
    - Safari 8.0.6 on mac works.

    - Chrome stable channel on windows (Version 45.0.2454.85 m) does not work.
    - Chrome beta channel on mac (Version 46.02490.13 beta) does not work.
    - Firefox Developer edition on mac (Version 42.0a2) does not work.

    The ones that do work appear to still have unsupported shader messages in the logs, but render correctly. The incompatible format error is not present on the working chrome version, (making me think that this is probably the issue, and that the shader issue is something unrelated... but this is just speculation).
     
    kazumasa0421 and MrEsquire like this.
  7. OrenMunkyFun

    OrenMunkyFun

    Joined:
    Jun 7, 2013
    Posts:
    7
    We're seeing the same errors on Android as well.
     
unityunity