However, when the bake completes and is encoded, lighting on objects becomes warped and offset, as if it is being read from the wrong UVs in the atlas.
All the objects in the scene are modular and use instanced static meshes, the UVs are not overlapping and use a mostly consistent texel density.
very possible the ladder’s UVs are bad.
Did you make the light-map yourself or was it engine generated?
And it seems like the last block above the ladder is a separate mesh that’s got some light bleed to it. Hard to say without actually looking at it, but I would guess that’s the reason why it’s lighting beyond the wall maybe?
Start with the UV first.
Check the model after - make sure they intersect or are at exact zeroed-out coordinates.
That wouldn’t explain why it looks fine during the bake. The previews shown above that use the in-progress data are fine. CPU lighting bakes look fine (but less accurate than GPU bakes). UVs are made by me but packed by the engine for lightmaps. All the mesh positions are generated through code and they are exact and not overlapping.
That doesn"look fine" it looks better but there’s still a light bleed on the steps is there not?
There must be some issue with the geometry somewhere for light to bleed trough - or at the very least the UV is bad and overlapping, but you would get errors on that one.
What is the other side of cube thing / isolate that model.
Either way that would not explain why the lightmaps get offset after being encoded. There is definitely no UV issues on the mesh.
Unreal Engine would log a warning if there were overlapping lightmaps, and we would be seeing details repeated on the same tile, not the inter-tile offsets we see here.
The lighting issue on the CPU bake went away when I rebuilt with production quality. We can see clearly here it is not an issue with the UVs or meshes
CPU
