Still experiencing this issue.
1 Like
Really hoping for this to be pulled back in - without fixing this, memory management for map creation is extremely limited
This bug is still present months later. Please address it, Epic Games.
2 Likes
also experiencing this bug, any one find a workaround for it?
not a solution, a very temporary work around seems to be âsavingâ the data layers and map file in the content browser and then launching the session. As soon as you add or move any prop though it seems like it requires saving all those files again. Havenât found a solution yet that âfixesâ the issue.
Bumping!
This is not a small issue and really limits what can be done in the engine..
2 Likes
Found that deleting the intermediate upload files help work around this issue a bit as well - \AppData\Local\UnrealEditorFortnite\Intermediate\ValkyrieUploadTemp something for others to try if they run into this bug. - specifically the bug weâre seeing is that data layer assets are loading in client and seem to disregard datalayer settings - this work around doesnât fix the issue completely, eventually things start to break again, biggest challenge is these assets will show up in published maps if youâre not careful.
Having the same issue with my old map: the new data layers get with time broken, cinematic sequence devices just do not load/unload the objects within a data layer. When will this be solved?
FORT-827943 has been âClosedâ. The issue reported is not caused by a bug in the tool.