Strange lighting error in baked lightmap

Hey guys, this artifact looks like the one you get when you have a missing reflection probe and the material uses the skybox instead, but as you can see they use the same reflection probe






Whats going on?

 

So I havent been able to fix this, any ideas?

Anyother problem which is not completly related is that the mesh uses a lower prio probe even though the higher prio probe completely surrounds the mesh, as you can see here it applies 0.07 from the ourdoor reflection probe

 

@SpiriTx @Joachim_Ante

I know you guys lurk in this part of the forum so I hope its ok I ping you directly. I have huge problem with this scene

As you can see above the tiles missmatch

Here is a example with huge difference, same mesh, same material, same reflection probes



The mesh is configured for lightmaps using the UV2 generation function


Material


Light settings


So, I really need help with this, thanks.

 

Hey @frosted I reply here instead, better than kidnapping the other thread.

Thanks, will look into it further, but if it was a res problem it would be for all tiles I guess? Here it loos fine, same meshes used btw



This is at the default 40 res, we have other scenes with similar size with no problems. I'm at a loss

edit: There is a seam problem in above screen though, but that can be fixed with baking the tiles, a bit sad Unity cant handle that for us

 

@frosted I tested your resolution theory, here I bake at 100 res, problem remains

 

Did you check the import/lightmapping settings on the mesh (from the mesh import, not scene instance).

Also - object lightmap scale in scene instance.

 

Yeah 1.0 scale, uv2 generate, mesh import settings above btw

 

Did you ever fix this?

Here's some ideas.

Try another vanilla scene with nothing except one tile with one material, no specular maps and one directional/point light to illuminate the scene.

Step repeat those tiles across to cover say cover 10 / 20 tiles - no light probes no reflection probes.

Do a bake with same settings you have now? Is there a problem.

Some daft questions... that seem obvious but always catch people.

Are those tiles perfectly aligned and exactly the same colour/material?

 

The last picture from above is from a isolated scene, problem remains but the color shifting is different.
I will try your idea.

Yeah, same mesh and material, yeah, aligned perfect to whole meters

 

I did a quick test, with tiles and the only thing I could see to cause the inconsistent colors was moving the reflection probe? Enlighten settings set really low at about 2 to show it isn't a resolution problem

What do you think?

Spoiler

If that doesn't work maybe you could wetransfer the scene and I could have a peak.

 

The only other thing as mentioned by frosted is having an insufficient lightmap res.



I mean here, I had to set the lightmap size to something really small like 32 and lightmap res to '2' to even notice the edges.

But then my scene is much smaller than yours, comparatively it might be the same.

Another daft, question but is there any reason you are working in that modular tiling way, and not just making a single plane for the floor?

 

I tried at 100 res, no difference

Its a modular asset, I guess I could combine them with Meshbaker, but its not a perfect workflow and some negative aspects like lower resolution lightmap per mesh and occlusion will not be as good etc.

 

Btw, I also tried the built in cubes and they work like they should, no color missmatch so I lean towards something with the mesh, but I use uv2 generation in Unity so cant really understand what it could be

 

Right OK so replace the tile you are using with a single plane from unity and see if you still get colour problems.

Gameobject > 3d Object > plane

Then step and repeat in your scene. Make sure to hide your existing tiles by turning them off in the inspector window.

That will prove if it is your tile that is the problem then as opposed to anything else.

 

I removed all reflection probes also added some new floor tiles to the right.

No change to the old part of the scene, but the new tiles dont get the problem. It only has one light on it, can it be related to multiple lights? will test

 

Let's not jump ahead so quickly, keep one variable fixed so we know exactly what's the problem.

So the new tile doesn't show this problem right?

Now fill the rest of the scene with all these new tiles keeping the lights exactly the same and report back with your findings.

(And to clarify this new tile is just the standard unity plane with a single texture on it)

 

how you getting on buddy?

 

@AndersMalmgren dude how you get on?

 

Sorry, missed your reply somehow. I'm at boring dayjob will need to play more with this tonight, Though about replacing it all with default material keep everything else and see if problem remains.

Thats not the standard plane thats the same tiles that show the problem inside the hangar. I tried the standard plane inside the hangar didnt show any problem.

 

Well if it is the plane / meshes, you can send it to me and I can uv unwrap it properly then send it back FYI.

 

Thanks, I'll keep you posted. Strange thing is we got alot of Unity generated uv2s in our game that does work.

 

No lights, no reflection probe



Next test will be default material only

 

Default material no lights, no reflection probes




hmm, it seems it syncs with the system debugger view, but not sure






Some input from Unity would be very, very welcomed, thanks

 

Are you using a default plane for the tiles. . . If you are then the next test, is to remove all point/area lights and light the entire scene with just one directional light.

After you've done this post back with your results.

 

This time around its the mesh from the asset, give me a sec

 

Dude, we're trying to figure out if it is the mesh that is at fault here LOL.

 

This is interesting, I changed the uv2 on the windows (red arrow), cleared cache and rebaked, now the missmatch moved



System view

 

Stick with the plan otherwise you're just punching in the dark, hide all existing tiles and replace with unity's standard plane.

 

Default plane



Im pretty convinced this is a bug with the lightmap systems

 

OK and there is no reflection or light probes in the scene right.

So now please deselect all point/area lights and light the scene with only one directional light and post back with your results.

 

There is no lights or reflection probes in the scene

 

Just sent you pm.

 

Isnt this really strange, I baked with 4096 lightmap size, it ended up with one lightmap. But in the systems view I end up with alot of systems



And offcourse color missmatch

 

Tried using a custom custom light parameter for the walls, floor and cealing, setting sytem tag to 1. Didnt help, still lots of systems

 

@JamesArndt Hey James, I remembered you had a problem with systems? I'm now being hit by it too I think, did you ever get that sorted?

 

No not that I can recall. It was still an issue.

 

It's really annoying since it's only one atlas they should all go on the same, I hope unity will show some interest soon because I'm out of ideas

 

Yeah there was nothing I could do to be honest. No one was giving me a concrete answer on how to solve this. I halted work on that project as it required baked lightmaps and it was consuming too much time finding workarounds. I think the last thing I was doing was baking lighting to vertex colors in 3ds Max and trying to use that combined with a shadow "decal sheet". I was basically rendering different shapes for shadows for objects and then using those as decals.

Might be important to note this was a mobile project for Android so the lightmapping thing was a blocker issue on that project.

 

So I tried to bake it under 2018.1.3, low res didnt have time to wait for the bake so get some edge bleed, which I think will be fixed by a higher res bake. But the color miss match seems to be gone, so please what ever you are doing in 2018 back port to 2017.4.5 (LTS and all that). We cant move to 2018 right now. For example the shaders for this very asset break in 2018 so thats why I have to use default materials

 

Man I'm still amazed the light baking is still this broken. Even on low settings you shouldn't be seeing what I am seeing in this image. Massive UV shell seams everywhere with horrible bleeding across them. Setting the quality to low should produce a little bleeding and no massively sized UV shell seams. That's what a well done lightmapper should work like. This is really pitiful and from my perspective one of the weakest aspects of the Unity editor.

 

Since we are a VR game there is not alternative than stick with baked lightmaps for now too

 

That is interesting. @AndersMalmgren what do the system uv charts look like?

 

I thought that was always the case with low res bakes for a LM simulating true GI??

 

This is at 20 res, and I do think it looks a bit better in 2017.4.5 will test and compare tonight

 

Btw, there is no change in the system layout, so it still does not honor my system tag config, but the color miss match between systems is gone

 

I was wondering if you could bake in 2018 and drag the lightmap files into 2017 or is that wishful thinking?

 

Will not work sadly. Since LTS they should backport this? We will move to 2018 eventually, we have a new ballistics system that will use features in 2018, but we are not ready for the move until a few months from now. Would like to release this level in our next update :/

 

Yeah i know, obviously i wouldn't expect you to ship a game on a unity beta build, but i did wonder if you could simply drag and drop the lightmaps over. also do you just have two installs of unity running side by side, i always thought one would overwrite the other for some strange reason.

 

It only works when going from for example 2017.4.4 to 2017.4.5 and even then sometimes you get the famous "lightmaps need to be rebuilt"

2018.1.3 is not a beta build. But yeah, cant move now

 

Well it shouldn't be if the UV splits and charting were done in a very intelligent way. It's an issue of seams being produced by the automated splits the editor is doing per settings. My assumption is the settings should be optimized and intelligent by default and not produce massive seam splits in highly visible areas. This comes down to an algorithm and it's dependencies on pre-determined settings.

This is an issue with the model import settings for UV setup for lightmaps. It's not part of the GI baking phase...but the issue becomes much more apparent after and during baking because of the visible seam, light leaking over boundaries, etc.