Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Voting for the Unity Awards are OPEN! We’re looking to celebrate creators across games, industry, film, and many more categories. Cast your vote now for all categories
    Dismiss Notice
  3. Dismiss Notice

Corrupted lightmaps and Reflection Probes on clean build with Unity 2018.1 (.1f2 and .4f1)

Discussion in 'Global Illumination' started by Leos924, Jun 13, 2018.

  1. Leos924

    Leos924

    Joined:
    Feb 14, 2015
    Posts:
    11
    I have a serious problem with lighting on a VR project I'm working on

    On Unity Editor I have baked my scene with Progressive, Enlighten and None, getting results like this:

    correct_lighting.PNG

    No errors besides the evident change of light in the back wall
    So, when I make a build and run it, I see results like this:

    2018-06-12 (1).png

    ( On other less severe cases it seems like the reflections show the directionality of the lightmaps, but in this case I did a bake without directionality )

    It looks totally like data corruption but the thing is that this has happened using 2 Unity Versions ( As I state in the title of this post ) and 4 different builds with totally different lightmapping settings
    My guess is that this has to do with the build process only and to be more specific, with how Unity saves Textures

    Has anyone solved something like this sort of issue?

    If this helps for anything the specs of the computers where I have ran my build are:

    Development Environment:

    Graphics Card: NVIDIA GTX 1080Ti
    CPU: Intel i7-7700K
    RAM: 24 GB Kingston HyperX
    HDD: Toshiba 2GB​

    Production Environment:

    Graphics Card: NVIDIA GTX 1050
    CPU: Intel i7-7700
    RAM 8GB Kingston HyperX
    HDD Kingston SSD 120GB
    Edit 1

    It seems the problem has to be with the size of the resources files ( Issue 779405 ) because I tested by deleting unused assets ( In case Unity stills saves them even if they are not in the Resources folder ) and using Crunch compression with almost all of the textures ( Ensuring that the build size would be reduced ) and voilá the problem was fixed on the test scene

    2018-06-13 (1).png

    I'll just have to reorganize my scenes and see if this is really the solution

    ( Maybe this post should be more suitable for another category of the forum )
     
    Last edited: Jun 13, 2018
  2. Orthac

    Orthac

    Joined:
    Aug 9, 2017
    Posts:
    2
    i have the same problem after i put reflections probes in the scene.
     
  3. Leos924

    Leos924

    Joined:
    Feb 14, 2015
    Posts:
    11
    Your problem seems unrelated to this, I solved this by reducing the resources files to less than 4GB each ( 32 bit limit )
    If I remember correctly, probes corruption is usually because your rig does not support the default compression algorithm, try changing "Environment" > "Environment Reflections" > "Compression" from the "Lighting" window
    Also, try disabling HDR from your probes and rebaking

    If that's not it, try posting a new thread for your specific issue and include as many details as you can