Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Bug WebGL Build stuck on Hidden/Shader Graph/FallbackError (Unity 2022.3.20f1.)

Discussion in 'Editor & General Support' started by rendrop, Feb 25, 2024.

  1. rendrop


    May 26, 2019
    I'm trying to build a WebGL application using Unity 2022.3.20f1.

    There are actually 2 applications on the project that is an integral part of each other.
    One is on Windows platform which I have no problem building the player. This uses HDRP rendering pipeline and is on a different branch.

    The other one is a WebGL application that share the same assets but uses built-in rendering pipeline.
    I have disabled the HDRP asset on graphic settings, etc and Unity allows me to build into WebGL platform.

    However, when I tried to build it got stuck on compiling shader variant of Hidden/Shader Graph/FallbackError (1/1 vp)

    Even when I have waited a day it is still stuck there.
    Also, when I press cancel it got stuck on the compiling shader variant and I had to end the Unity process.
    When I checked, the editor log is 8gb in size.

    ps: I have the editor log that is not 8gb in size. however, I cannot upload the editor log since it's 18mb, can I provide a Google Drive link into the editor log?

    Thank you!
  2. CodeSmile


    Apr 10, 2014
    I can imagine that one way or another something references something else that ends up referencing something that requires HDRP. And HDRP is not supported for WebGL.

    It's not a good idea to have separate render pipelines in the same project, at least not until 2023.3+ (I believe selectively changing render pipelines is something Unity's working on). But unless you want to upgrade and try it out I feel like these two applications ought to be separate projects that share assets, ideally by using a "shared content" package.

    Also for WebGL you want to be using the URP renderer, not built-in, as its far more efficient.