Hi everyone,
I have a blueprint actor composited by few staticmeshcomponents and if I build static lighting it all works well.
BUT if I change a little the rotations and translation of the staticmeshcomponents directly from the detail panel of the posed actor, and rebuild the lightmaps, the next time I’ll reload the level some object have invalidated lightmaps.
As you can see there are 3 objects with componenttowrold transform different from the transfom in instancecached datas, so it invalidates them.
The stranger thing is that if I immediately rebuild the lightmaps the editor discover that another object is broken…
After lightmaps rebuilding it all goes ok, the preview show correct lightmaps, but it is sufficient that I reload the level or rebuild again the lightmaps that I’ll go back to square one with 3 broken objects.
The craziest things are:
the result is not always the same
it seems you have to move components with children and grandsons to brake it
sometimes while I rotate a single component it invalidates the lightmaps of OTHER non-moving components of the same BP
Please fix this!
Here is the link of the project I used for this test case…
Well it seems to me that this is just a bug. It’s not really the same as 428978 because you do not spawn the objects.
Simple workaround would be to set the correct relative space in the blueprint and not in the already placed blueprint. Ofc you would have to create an instance of this blueprint (or duplicate it) for every position.
Second way is to set the positions via construction script and expose the variables. This should work, I have just tested it without exposed variables.
IIRC this has already been resolved in 4.13. You can check this for yourself in the 4.13 previews that are currently available in the Epic Games Launcher.
Thanks Tim!
But we have to release the game in 2 weeks and we cannot afford a migration to 4.13preview, can you tell me which commits fixed this bug? We’ll try to cherry pick them.
Thanks
Thanks Tim!
But we have to release the game in 2 weeks and we cannot afford a migration to 4.13preview, can you tell me which commits fixed this bug? We’ll try to cherry pick them.
Thanks
Unfortunately, I don’t know the specific commits. This was something that was reported in something I was investigating and when I checked in 4.13 it was already fixed. I didn’t see any specific tickets in our JIRA system either, which makes it near impossible for me to know what changes were made without doing a regression. Sorry.
Hi Tim, I am on 4.13 and am getting the same problem when adding instance transforms to an instanced static mesh component through blueprint construction script. Whenever I set an instance transform’s rotation value in the construction script (even though the rotation value is exactly the same), the lightbake will more often than not invalidate on reloading the level - although I’ve found edge cases where everything is fine. Very frustrating!
if you have a specific set of steps that can reliably reproduce it I can check. When I used test asset provided by the OP the issue did not reproduce with that content or content that used on my own.
didn’t mean to necro this thread, but i’m still having this issue in 4.15. i’m using spline mesh components that have “set start and end points/tangents” nodes to match spline point locations in the constructor. this seems to be pretty standard, but lighting gets discarded, even though all mesh components are set to static. any other way to trouble shoot this?
