Search Unity

Bug Time + Tiling and Offset node on a Lit material will cause the bake to be stuck on Preparing Bake

Discussion in 'Global Illumination' started by pontushero, May 2, 2023.

  1. pontushero

    pontushero

    Joined:
    Oct 18, 2018
    Posts:
    3
    Hi,

    After having updated to 2022.2.16 (URP) my lighting cannot be baked in scenes that have a material made from a shader graph that have a scrolling texture connected to the base color coupled with a Mesh Renderer that have "Contribute Global Illumination".

    Before finding the culprit I have tested these things that doesn't change the outcome: removing Library folder, Generate Shader Includes, Upgrading to 2022.2.17, Switching to Progressive CPU (instead of GPU), Clean GI Cache, Material's Global Illumination "None" instead of "Baked", made a test scene with a new shader graph and material.

    The lightmapper gets stuck at 5% "Preparing Bake" and the remaining time keeps increasing indefinetely.

    There are no logs in the console and the editor log shows a lot of these outputs going circular:
    [PathTracer] Material rendered (update) albedo/emissive for material hash: 4d4332c5e45ef111062d412a08724e0d -> e83ac6778ed7f2821d794c187fb8508b, size: 8x8.
    [PathTracer] Material rendered (update) albedo/emissive for material hash: e83ac6778ed7f2821d794c187fb8508b -> fdea0f6eac0db213aee618c5bb8ea8d3, size: 8x8.
    [PathTracer] Material rendered (update) albedo/emissive for material hash: fdea0f6eac0db213aee618c5bb8ea8d3 -> d71d87c18bddc095f2a841d1fbd34e54, size: 8x8.
    [PathTracer] Material rendered (update) albedo/emissive for material hash: d71d87c18bddc095f2a841d1fbd34e54 -> e14dd91803f48ad418d9227e6ad0ba0d, size: 8x8.
     
  2. Pema-Malling

    Pema-Malling

    Unity Technologies

    Joined:
    Jul 3, 2020
    Posts:
    324
    pontushero likes this.
  3. HanzoRev

    HanzoRev

    Joined:
    Aug 4, 2022
    Posts:
    1
  4. Pema-Malling

    Pema-Malling

    Unity Technologies

    Joined:
    Jul 3, 2020
    Posts:
    324
    There was a mixup with this bug causing the info on the issue tracker to be incorrect. The issue should be fixed on these upcoming versions:
    2021.3.28f1
    2022.3.2f1
    2023.1.0b21
    2023.2.0a19