Shading issues appearing in build, but not in editor

This issue popped up last week after one of our weekly builds, and all subsequent builds after have been doing this. I will preface this with that I am still pretty new to Unity lighting, I have only really been messing around with it since the beginning of the year. I have learned quite a bit since then, but I still would consider myself a novice with it.


These are some of the shading issues present in our current builds


And here's those same areas in engine

This problem arose after building light with a Lightmap Resolution of 20, which was supposed to be for our launch build (worst possible timing). I have not been able to test if it goes away if I set it back to 1, since I don't do builds on our team, but we are planning on testing that today. We've tried rebuilding, I checked all the offending walls Mesh Renderer to see if maybe something was out of the ordinary. I'm sure there's more I can check, but I haven't been able to find anyone with a similar issue online (I honestly don't know how to describe the problem uniquely), and I don't know what else to check.

Here's the lighting settings the scene is using (had to stitch together the images) :

We are using Unity 2018.1.3f1, let me know if there's any other important info that I may have forgotten.

 

This has occurred in our project too. I believe they are generated.

 

Hey @Clell_Tickle, @Kevin-VFX,

Issues like this are usually caused by:

• incorrect normals
  • https://docs.unity3d.com/Manual/FBXImporter-Model.html - use import (if you have proper normals in your DCC app) or calculate
    
  • to verify you can:
    • switch to deferred and check out the normals scene view mode
    • use my script: VisualizeTangentSpace.cs
• incorrect UVs
  • https://docs.unity3d.com/Manual/LightingGiUvs.html
    
  • https://docs.unity3d.com/Manual/LightingGiUvs-GeneratingLightmappingUVs.html