# Data layers always visible on older projects **URL:** \ **Category:** Issues and Bug Reporting\ **Tags:** fortnite-creative, unreal-editor-for-fortnite, closed, fortnite\ **Created:** [November 7, 2024, 12:30am UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759 "2024-11-07T00:30:20Z")\ **Posts on this page:** 10\ **Page:** 2
**Author:** ![LazraelAkari](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@LazraelAkari](https://forums.unrealengine.com/u/LazraelAkari)\ **Post date:** [June 7, 2025, 8:05am UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/25 "2025-06-07T08:05:39Z")
Still experiencing this issue. ---
**Author:** ![QuestBoxFN](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/questboxfn/32/1059609_2.png) [@QuestBoxFN](https://forums.unrealengine.com/u/QuestBoxFN)\ **Post date:** [June 16, 2025, 5:47pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/26 "2025-06-16T17:47:42Z")
Really hoping for this to be pulled back in - without fixing this, memory management for map creation is extremely limited ---
**Author:** ![\_lvin\_fv](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@\_lvin\_fv](https://forums.unrealengine.com/u/_lvin_fv)\ **Post date:** [June 16, 2025, 5:52pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/27 "2025-06-16T17:52:27Z")
This bug is still present months later. Please address it, Epic Games. ---
**Author:** ![zkz-nito](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@zkz-nito](https://forums.unrealengine.com/u/zkz-nito)\ **Post date:** [July 3, 2025, 12:02pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/28 "2025-07-03T12:02:42Z")
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. ---
**Author:** ![QuestBoxFN](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/questboxfn/32/1059609_2.png) [@QuestBoxFN](https://forums.unrealengine.com/u/QuestBoxFN)\ **Post date:** [July 10, 2025, 2:42pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/29 "2025-07-10T14:42:57Z")
Bumping! This is not a small issue and really limits what can be done in the engine.. ---
**Author:** ![zkz-nito](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@zkz-nito](https://forums.unrealengine.com/u/zkz-nito)\ **Post date:** [July 11, 2025, 5:46pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/30 "2025-07-11T17:46:41Z")
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. ---
**Author:** ![theBuildozer](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@theBuildozer](https://forums.unrealengine.com/u/theBuildozer)\ **Post date:** [July 12, 2025, 11:01am UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/31 "2025-07-12T11:01:52Z")
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? ---
**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/997076_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\ **Post date:** [August 4, 2025, 11:43pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/32 "2025-08-04T23:43:41Z")
FORT-827943 has been ‘Closed’. The issue reported is not caused by a bug in the tool. ---
**Author:** ![iFlone](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/iflone/32/1031293_2.png) [@iFlone](https://forums.unrealengine.com/u/iFlone)\ **Post date:** [October 12, 2025, 6:05pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/33 "2025-10-12T18:05:06Z")
Encountering the issue too. If you judge this is not a « bug » give us a solution Epic. My old data layers works fine but the new ones arent in game so i cannot do anything. **Found a fix:** For anyone having this issue later, make sure your props aren’t attached to a blueprint actor. In my case since some props were attached to one, they were always visible no matter what and the spatially loaded + data layers options in the details panel were grayed out for each of them. ---
**Author:** ![Kev11985](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Kev11985](https://forums.unrealengine.com/u/Kev11985)\ **Post date:** [November 23, 2025, 2:17pm UTC](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759/34 "2025-11-23T14:17:41Z")
I’ve been using Data Layers for the first time and I initially had this same error. However it seems that changing the Mobility of the actors you want to add to the data layer to either “stationary” or “movable” seems to have fixed the issue for me. [Previous page](https://forums.unrealengine.com/t/data-layers-always-visible-on-older-projects/2108759.md?page=1)