Can confirm, happening in my maps too. This is VERY game-breaking and I hope this get’s fixed asap as we can’t update our maps until this is fixed. It does seem to work in versions uploaded before the update but not any after this update.
Can confirm on a case with a tagged trigger and attached static meshes, also showed up with a base blueprint and attached glass prop walls. This is an absolutely game breaking bug, genuinely unacceptable this is a feature that cannot break
Pre published game is working fine, however private codes also manifest the same issues
Yea this bug is extremely game-breaking, completely broke almost everything in my map. Hopefully they revert / fix whatever was changed in this update!
we hot fixed ours to not use it as we know by now that we can’t wait for Epic to fix it before it completely kills the game, but it was: 5473-5965-0108
This is my island ,it doesn’t have any issues atm as it’s an older version (before the new season) , but in the live session and new private version everything is broken so i can’t update it , a lot of powers i have is basicaly an empty blue print and child player references attached to it that teleports to players , but they do not teleport proberly
One thing i noticed , if i deattached the child actors , reattached and i didn’t push changes , the problem is solved , but if i pushed changes , everything is broken again
I can not replicate this in a brand new map despite that we tested at length to fix this in our maps. The idea being that a blueprint is made, the in code you would add the editable for it:
and something would be parented to that blueprint in the Outliner
Can anybody replicate this for Epic? I’m still working on it but I’m unsure of how to replicate. Maybe it has to be in a previously made and published map?
Actually, as it turns out you can see it not working because our “nuke” BP is not moving with the storm, so we couldn’t fix everything which should allow you to see the problem happening.
I’ve done a LOT of testing now and I think this has to do with render distance. Which is WEIRD, because I can see the prop from a distance, but it doesn’t move with the parent. When a prop is parented (or any device too I think) and it’s far away from the player then it doesn’t get calculated to move, or the server doesn’t tell the player side to move it. If it’s close enough within some value to the player, it both renders AND moves. So.. something has changed on the server side that it is determining that it does not need to tell things to move, and definitely not the children?
I can not get this to replicate when I have all props and devices close to the player no matter the parent/child/child relationship between the props and devices going on and I can’t make it happen on an empty map for testing.
Hopefully that helps because we all need this fixed ASAP….
