Search Unity

  1. Unity 2019.2 is now released.
    Dismiss Notice

Build error: "Shader compiler: internal error compiling shader snippet type=0 platform=5"

Discussion in 'Unity Cloud Build' started by tatata, May 17, 2016.

  1. Kiupe

    Kiupe

    Joined:
    Feb 1, 2013
    Posts:
    528
    Any news about this issue ? All my builds failed because of that and I don't know how to to fix that. Kind of frustrating.
     
  2. Kmausser

    Kmausser

    Joined:
    Feb 17, 2016
    Posts:
    23
    This is my log:

    1: [Unity] Initialize engine version: 5.6.1f1 (2860b30f0b54)
    2: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    3: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    4: [Unity] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
    5: [Unity] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
    6: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    7: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    8: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    9: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    10: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Vectorscope Render' - Pass '' has no vertex shader
    11: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Vectorscope Render' - Setting to default shader.
    12: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Vectorscope Render' - Pass '' has no vertex shader
    13: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Vectorscope Render' - Setting to default shader.
    14: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Parade Render' - Pass '' has no vertex shader
    15: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Parade Render' - Setting to default shader.
    16: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Parade Render' - Pass '' has no vertex shader
    17: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Parade Render' - Setting to default shader.
    18: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Pass '' has no vertex shader
    19: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Setting to default shader.
    20: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Pass '' has no vertex shader
    21: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Setting to default shader.
    22: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Waveform Render' - Pass '' has no vertex shader
    23: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Waveform Render' - Setting to default shader.
    24: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Waveform Render' - Pass '' has no vertex shader
    25: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Waveform Render' - Setting to default shader.
    26: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Histogram Render' - Pass '' has no vertex shader
    27: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Histogram Render' - Setting to default shader.
    28: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Histogram Render' - Pass '' has no vertex shader
    29: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Monitors/Histogram Render' - Setting to default shader.
    30: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Depth Of Field' - Pass 'COC TEMPORAL FILTER' has no vertex shader
    31: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Depth Of Field' - Pass 'COC TEMPORAL FILTER' has no vertex shader
    32: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Temporal Anti-aliasing' - Pass '' has no vertex shader
    33: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Temporal Anti-aliasing' - Pass '' has no vertex shader
    34: [Unity] Initialize engine version: 5.6.1f1 (2860b30f0b54)
    35: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    36: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    37: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    38: [Unity] Assets/TouchJoysticks/Scripts/RightJoystickPlayerController.cs(11,23): warning CS0414: The private field `RightJoystickPlayerController.rigidBody' is assigned but its value is never used
    39: [Unity] [ 161 MB ]WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
    40: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
    41: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
    42: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
    43: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Depth Of Field' - Pass 'COC TEMPORAL FILTER' has no vertex shader
    44: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Pass '' has no vertex shader
    45: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Setting to default shader.
    46: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Temporal Anti-aliasing' - Pass '' has no vertex shader
    47: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
    48: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
    49: [Unity] WARNING: Shader Unsupported: 'VR/SpatialMapping/Wireframe' - Pass '' has no vertex shader
    50: [Unity] WARNING: Shader Unsupported: 'VR/SpatialMapping/Wireframe' - Setting to default shader.
    51: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
    52: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
    53: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Pass '' has no vertex shader
    54: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Eye Adaptation' - Setting to default shader.
    55: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Depth Of Field' - Pass 'COC TEMPORAL FILTER' has no vertex shader
    56: [Unity] WARNING: Shader Unsupported: 'Hidden/Post FX/Temporal Anti-aliasing' - Pass '' has no vertex shader
    57: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
    58: [Unity] Shader error in 'Hidden/Post FX/Grain Generator': Internal error communicating with the shader compiler process
    59: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Pass '' has no vertex shader
    60: [Unity] WARNING: Shader Unsupported: 'Hidden/VR/BlitCopyFromTexArray' - Setting to default shader.
    61: [Unity] Player export failed. Reason: Shader error in 'Hidden/Post FX/Grain Generator': Internal error communicating with the shader compiler process
    62: ! build of 'default-webgl' failed. compile failed
    63: publishing finished successfully.
    64: Finished: FAILURE
     
  3. 4fthawaiian

    4fthawaiian

    Joined:
    Dec 18, 2013
    Posts:
    33
    I totally commented on this back in November - still completely broken 100% of the time for android and iOS. Please respond, as this is completely unacceptable.
     
  4. 4fthawaiian

    4fthawaiian

    Joined:
    Dec 18, 2013
    Posts:
    33
    and now it's spread to our other project - so I officially can't deliver builds for either one of our products. This is just awful.

    anyone home, Unity?

    For the record:

    [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number

    [Unity] Shader error in 'Standard': Internal error communicating with the shader compiler process

    [Unity] Player export failed. Reason: Shader error in 'Standard': Internal error communicating with the shader compiler process

    ! build of 'default-android' failed. compile failed

    Finished: FAILURE

    occurs consistently with any mobile builds on either of our products. this is now a production issue for us, as we can't generate QA builds, and thus can't test new changes and ship them.

    I've opened a support issue, responded here, even tweeted, and you guys are asleep at the wheel. Please respond.
     
  5. iamsidv

    iamsidv

    Joined:
    Jan 24, 2013
    Posts:
    17
    I too am getting the same error. Its not at all building for iOS now.

    Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
    156: [Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process.

    Unity version is 5.3.5f1.
     
  6. Koamr

    Koamr

    Joined:
    Jul 19, 2013
    Posts:
    6
    I am also experiencing this problem. Similarly like someone already mentioned -> it started failing after I added particle system to my project.
     
  7. ddsim

    ddsim

    Joined:
    Oct 6, 2016
    Posts:
    1
    same problem here, after changing from unity 5.5.1f to 5.6.1p4

    (tested with two different projects)
    nevermind. it was just a misguiding error in the log. above were other compileerrors.

    edit 2: unfortunately after fixing the other errors (which were because of some facebooksdk namespace errors after upgrading unity to 5.6) I still got errors..

    30929: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number

    30938: [Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process


    edit 3 (solution?)

    So I got 4 project that had a 100% build fail rate after upgrading to Unity 5.6.1 on cloud build. Always with the Sprites/Default shader error. Thanks to the post of "fisher-lv" I tried to include this shader to the "always included shaders" list in graphics settings. Now everything works fine again.


     
    Last edited: Jun 20, 2017
  8. cygnusprojects

    cygnusprojects

    Joined:
    Mar 13, 2011
    Posts:
    659
    Started a android cloud build and I'm facing the same error using 5.6.2f1:
    Player export failed. Reason: Shader error in 'Hidden/Post FX/Grain Generator': Internal error communicating with the shader compiler process
    Strange thing, this only happens on the android build and not with the Windows and Mac standalone builds.
     
  9. 4fthawaiian

    4fthawaiian

    Joined:
    Dec 18, 2013
    Posts:
    33
    Meh. Cloud build is broken. We used it in beta, and have tried to continue to use it. However, the support has been worse than terrible, and there seems to be no end in sight to this issue. We've moved to the wonderful unity plugin for Jenkins, and couldn't be happier. I suggest you do the same.
     
  10. Ludomade

    Ludomade

    Joined:
    Nov 11, 2014
    Posts:
    11
    Just got this error again too.
     
  11. cygnusprojects

    cygnusprojects

    Joined:
    Mar 13, 2011
    Posts:
    659
    Hmm, I'm subscribed to the Unity Plus service so I'm paying to use the cloud services. Will take it up with their support division as this isn't how it should be.
     
  12. jbassking

    jbassking

    Joined:
    Feb 27, 2014
    Posts:
    53
    I don't know if this will help anyone, but for me, anytime I run into this issue, I change the config setting for the cache. If the cache is set to library, I set it to none, and if it's set to none, I set it to library and then restart the build.
    Hope this helps.
     
  13. ckirby101

    ckirby101

    Joined:
    Aug 21, 2014
    Posts:
    10
    we are getting constant errors with cloud build..
     
  14. mark_isci

    mark_isci

    Joined:
    Oct 7, 2016
    Posts:
    1
  15. cygnusprojects

    cygnusprojects

    Joined:
    Mar 13, 2011
    Posts:
    659
    Have been in contact with their support division: Starting clean builds did resolve the issue for me. You can do this from your Cloud Build dashboard:
    • Next to the 'Start New Builds' button is a drop down arrow.
    • Select 'Build a combination of targets' from this list.
    • Toggle the targets you wish to build for.
    • Click 'Clean Build Selected' and your build will start.
    Takes longer to build but al least it works.
     
  16. faatal

    faatal

    Joined:
    Nov 21, 2012
    Posts:
    9
    Been getting several of these the last few days:

    Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
     
  17. Mazyod

    Mazyod

    Joined:
    Apr 21, 2014
    Posts:
    24
  18. Mazyod

    Mazyod

    Joined:
    Apr 21, 2014
    Posts:
    24
    Except when it fails, it goes to cooldown, even tho we got the plus
     
  19. faatal

    faatal

    Joined:
    Nov 21, 2012
    Posts:
    9
    And once today, but succeeded on next build.
     
  20. peterpunk

    peterpunk

    Joined:
    Nov 25, 2012
    Posts:
    8
    Broken here too, for cloud on Android & Ios builds. :-(
     
  21. ArtyomIsFlash

    ArtyomIsFlash

    Joined:
    Oct 13, 2014
    Posts:
    21
    I guess that's the problem with Unity Shader Compiler process. I faced the same problem with Lux terrain Standard shader on Unity 2017.1.0f3. But before everything was fine.

    UPD: BTW I wasn't even building - after I made some mods to the shader it errored out with this message in the console.
     
    BSG-Masterton likes this.
  22. AmbroseNilam

    AmbroseNilam

    Joined:
    Jun 27, 2017
    Posts:
    2
    Error still occurs on Latest Unity Version. Anyone have a solution?
    Also, are there still problem with GPGS? Tried to build with those and got library errors
     
  23. PhilMcJ

    PhilMcJ

    Unity Technologies

    Joined:
    May 29, 2014
    Posts:
    187
    For an update: developers from a couple of Unity teams have been tracing down the cause of this error, which turns out to be a specific crash that can happen in the shader compiler process itself. It should be possible to encounter this crash outside of Cloud Build as well, but Cloud Build's systems seem to be more prone to encountering it. (The overall rate of this error continues to be low in Cloud Build, but when it happens to a project, it does tend to occur repeatedly).

    An at-least-partial fix for this has been being tested, and is on its way into the Unity trunk now. We don't have an estimate for which patch and/or official releases will include it quite yet, but we will provide an update as soon as we know when it'll be available. In the meantime, rebuilding with library caching enabled will eventually succeed and get a project past this error, in the team's experience here.
     
    cygnusprojects likes this.
  24. SamuelGoldenbaum

    SamuelGoldenbaum

    Joined:
    May 21, 2017
    Posts:
    30
    Guys, we need a resolve for this. Critical that builds get done. Please update with relevant patch details.
     
  25. ObjectStudio

    ObjectStudio

    Joined:
    May 31, 2017
    Posts:
    1
    I was having the same problem despite building a 2D mobile game that uses no materials. It turns out that a material in one of my installed packages was using Mobile/Particles/Additive, apparently instigating the above error. Since our project needs no materials, I deleted it and was able to build our iOS build in Cloud Build (Android was fine for whatever reason).

    This isn't a solution to the problem, but if you're like us and experience this issue for seemingly no reason, you might try removing any deleting any materials you aren't using from your project, specifically those using the shader that's appearing in your error log.
     
  26. ArtyomIsFlash

    ArtyomIsFlash

    Joined:
    Oct 13, 2014
    Posts:
    21
    OK, I found a possible solution - kill Unity Shader Compiler in Task Manager. Worked for me.
     
  27. domdev

    domdev

    Joined:
    Feb 2, 2015
    Posts:
    288
    im getting this too in text mesh pro,, then I rebuild it again and works fine

    in 'TextMeshPro/Sprite': Internal error communicating with the shader compiler process
     
  28. Black_Stormy

    Black_Stormy

    Joined:
    Jan 20, 2013
    Posts:
    3
    I've had some unknown compile issues on cloud build recently, might not be related to this bug, but this explanation of it satisfies me. Thanks for the transparent feedback, it makes me more confident that you guys really know your stuff! (because I don't :p)
     
  29. sam-eller

    sam-eller

    Joined:
    Apr 26, 2017
    Posts:
    4
    For me, I had this error with the Skybox shader in the cloud build for iOS. All I had to do was change my camera in the scene to depth only, not skybox, and the error went away.
    Not the best fix for people who need skybox, but hey, its what fixed it.
     
  30. bererton

    bererton

    Joined:
    Jun 20, 2014
    Posts:
    34
    I also ran into this error on two builds. It's complaining about:
    [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
    276: [Unity] Shader error in 'Legacy Shaders/VertexLit': Internal error communicating with the shader compiler process

    However, I don't know what would be using the shader, I can't easily find it in my project, and our 2D game doesn't need any materials other than for the sprites we're using. Any ideas?
     
  31. domdev

    domdev

    Joined:
    Feb 2, 2015
    Posts:
    288
    so when was unity will gonna fix this? I'm in windows pc and im depending in unity cloud build for ios build.. :( it will took 3 to 4 hrs to make a build when error happens.. cause of the cooldown
     
  32. tridentcanadainc

    tridentcanadainc

    Joined:
    Mar 8, 2017
    Posts:
    10
    Getting this error as well:

    Code (CSharp):
    1. 9197: [Unity] Shader compiler: internal error compiling shader snippet type=0 platform=5: Protocol error - failed to read correct magic number
    and then:
    Code (CSharp):
    1. 9203: [Unity] Shader error in 'Sprites/Default': Internal error communicating with the shader compiler process
     
  33. PhilMcJ

    PhilMcJ

    Unity Technologies

    Joined:
    May 29, 2014
    Posts:
    187
    Update: the latest 2017.2 betas (after b8) have the shader compiler crash fix, and should be far less prone to getting this error. The backports are in progress; the fix didn't make it into 2017.1.1f1 but it is in the patch release cycle, so it should be in 2017.1.2. More info to come as versions are finalized and released.
     
  34. spiraloid

    spiraloid

    Joined:
    Aug 11, 2015
    Posts:
    7
    When is 2017.1.2 expected to release?

    Thanks!
     
  35. scheffield

    scheffield

    Joined:
    Aug 7, 2017
    Posts:
    2
    I get the following compilation Errors for shaders when compiling for OpenGLES30. Tried it with different Unity versions, with the newest 2017.2.0f1.

    "Assertion failed: Shader Compiler Socket Exception: Terminating shader compiler process, 0 retries left"
    and
    "Assertion failed: Shader compiler: internal error compiling shader snippet type=0 platform=9: Protocol error - failed to read correct magic number"

    I am not using Cloud Build. Could this be a hardware issue
     
  36. stevenwanhk

    stevenwanhk

    Joined:
    Jul 20, 2016
    Posts:
    100
    Same on 2017.2.0f3

    Assertion failed: Shader compiler: internal error compiling shader snippet type=1 platform=1: Protocol error - failed to read correct magic number

    Assertion failed: Shader Compiler Socket Exception: Terminating shader compiler process, 0 retries left

    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)

    Shader error in 'Sprites/Mask': undeclared identifier 'IN' at /Program Files/Unity2017.2/Editor/Data/CGIncludes/UnityCG.cginc(766) (on d3d11)

    Compiling Vertex program with ETC1_EXTERNAL_ALPHA PLUGIN_STEREOX
    Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME

    Assertion failed: Shader compiler: internal error compiling shader snippet type=1 platform=1: Protocol error - failed to read correct magic number
    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)

    Not using Unity Cloud
     
  37. Wothanar

    Wothanar

    Joined:
    Sep 2, 2016
    Posts:
    97
    i have a shader build error and cant compile locally its for a work and i need it can you help me to build and fix this shader and build error please?
     
  38. BenHymers

    BenHymers

    Joined:
    Dec 16, 2014
    Posts:
    25
    We get this too, on our in-house Team City build server, on Unity 2017.2.0p1. Shader is Nature/Terrain/Diffuse. Happened last time while building OSX 64 bit release standalone. Was building after a successful build for Win 64 bit development standalone.

    It's not a blocker for us since it's very rare, but this kind of random failure is intensely annoying, and would be even more so if it happened while we were waiting on an important build.

    Here's an excerpt from the log of the most recent failure:

    Shader compiler: exception while compiling shader snippet. Thread=1160 Type=0 platform=15. Source:

    <snip - shader source goes here>

    Shader Compiler Socket Exception: Terminating shader compiler process, 0 retries left

    (Filename: C:\buildslave\unity\build\Tools/UnityShaderCompiler/ShaderCompilerClient.cpp Line: 277)

    Shader compiler: internal error compiling shader snippet type=0 platform=15: Protocol error - failed to read correct magic number

    (Filename: C:\buildslave\unity\build\Tools/UnityShaderCompiler/ShaderCompilerClient.cpp Line: 894)

    Shader compiler: UnityShaderCompiler.exe compiler executable disappeared on thread 1160, restarting
    Launched and connected shader compiler UnityShaderCompiler.exe after 0.03 seconds
    Compiled shader 'Nature/Terrain/Diffuse' in 4.82s
    metal (total internal programs: 144, unique: 120)
    glcore (total internal programs: 143, unique: 96)
    Shader error in 'Nature/Terrain/Diffuse': Internal error communicating with the shader compiler process

    (Filename: Nature/Terrain/Diffuse Line: -1)
     
  39. RakivEldring

    RakivEldring

    Joined:
    Nov 2, 2017
    Posts:
    8
    This error occurred to us for the first time now.

    Continuous integration and default target builds work fine on Unity Cloud.

    Made a new target for branches (as a copy of Default) and it failed on the #1 build. Hopefully #2 works (no changes, only restart). Would be nice if this got solved for good. Inconsistency removes one advantage for CI and cloud builds.
     
  40. Lostlogic

    Lostlogic

    Joined:
    Sep 6, 2009
    Posts:
    691
    I get this error about every 30 minutes.

    Assertion failed: Shader Compiler Socket Exception: Terminating shader compiler process, 0 retries left
    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)
    Assertion failed: Shader compiler: internal error compiling shader snippet type=0 platform=15: Protocol error - failed to read correct magic number
    UnityEngine.GUIUtility:processEvent(Int32, IntPtr)
    Shader error in 'Standard': Internal error communicating with the shader compiler process
     
  41. rad1c

    rad1c

    Joined:
    Feb 26, 2016
    Posts:
    21
    2017.3.1, trying to change color grading from Neutral to Filmic:

    Shader error in 'Hidden/Post FX/Lut Generator': failed to open source file: 'ACES.cginc' at line 10 (on d3d11)

    Compiling Vertex program with TONEMAPPING_FILMIC
    Platform defines: UNITY_ENABLE_REFLECTION_BUFFERS UNITY_USE_DITHER_MASK_FOR_ALPHABLENDED_SHADOWS UNITY_PBS_USE_BRDF1 UNITY_SPECCUBE_BOX_PROJECTION UNITY_SPECCUBE_BLENDING UNITY_ENABLE_DETAIL_NORMALMAP SHADER_API_DESKTOP UNITY_LIGHT_PROBE_PROXY_VOLUME UNITY_LIGHTMAP_RGBM_ENCODING


    The only solution I found is, change back to Neutral, turn off Color Grading, quit Unity, wait 10-15seconds (so Windows throws it out from memory), restart Unity, turn Color Grading back on but don't you dare to change "Neutral" to Filmic ever again (same issue).


    [EDIT: Getting similar errors with Eye Adaptation as well. Same thing to do here, except, leave Eye Adapt. off, otherwise things go wild...]
     
    Last edited: Mar 18, 2018
  42. Nyarlytv

    Nyarlytv

    Joined:
    Jun 7, 2015
    Posts:
    1
    https://i.imgur.com/upiH0DS.png
    I'm having this a lot. instantiating tiles and doing Shader.Find to set the fog of war on each tile. Pretty sure it's because I'm instantiating lots of stuff and the shader.find just fails there...
    Just so you know...
     
  43. entropicjoey1

    entropicjoey1

    Joined:
    Jun 1, 2014
    Posts:
    20
    I was getting this error relentlessly, and I decided to build with development build checked, and it worked so I tested it after that unchecking development build and it works again, got this error deleting old assets from my project and this is the first thing that worked for me 2018.1.0f2
     
  44. jjxtra

    jjxtra

    Joined:
    Aug 30, 2013
    Posts:
    1,027
    Just got this error today on Unity 5.6.6...
     
  45. KrankyBoyGames

    KrankyBoyGames

    Joined:
    Mar 27, 2009
    Posts:
    733
    Seeing this error in 5.6.6f2. Frustrating.
     
  46. Wothanar

    Wothanar

    Joined:
    Sep 2, 2016
    Posts:
    97
    lol thats old man you should update your unity XD
     
  47. AmitSuri

    AmitSuri

    Joined:
    Sep 26, 2017
    Posts:
    21
    @Ryanc_unity getting this error on 2019.2.8f1 broken builds 100%
    FORWARD, Vertex Program: Internal error, unrecognized message from the shader compiler process. Please report a bug including this shader and the editor log.

    [Update]
    Found the reason why it happened.
    I uninstalled the following and the error is gone!
    "com.unity.2d.tilemap": "1.0.0",
    "com.unity.polybrush": "1.0.1",
    "com.unity.postprocessing": "2.1.7",
    "com.unity.probuilder": "4.0.5",
    "com.unity.shadergraph": "6.9.1",
    Looks like something is messy with one of those packages and shader compilation.

    Anyone having this problem. Just remove all unused packages from Unity and then try again.
     
    Last edited: Oct 11, 2019
  48. Gamezaur

    Gamezaur

    Joined:
    Oct 12, 2016
    Posts:
    12
    100% broken builds with Unity 2019.2.8.f1. These are desktop builds, not cloud builds.

    I tried removing a few packages but no luck so far :(
     
  49. avorobjev

    avorobjev

    Joined:
    Apr 3, 2014
    Posts:
    8
    I tried, it didn’t help me.
     
  50. Fillmore

    Fillmore

    Joined:
    Feb 14, 2018
    Posts:
    6
    Shader compiler: Compile Legacy Shaders/VertexLit - Pass 0, Vertex Program: Internal error, unrecognized message from the shader compiler process. Please report a bug including this shader and the editor log.
    UnityEditor.EditorApplication:Internal_CallGlobalEventHandler()

    +more

    Still happening in 2019.2.9f1