Is there a different way to create Data Layers in 5.1 vs 5.0. I created a fresh scene w 5.0 and created data layers with no issues. I then created a new scene in 5.1 and I can not create data layers. Not sure if the process is different or if they do not work in 5.1? Anyone else have issues like that?
1 Like
Hey there @alxmedia! Is the option to create the data layer greyed out? If you can create the data layer here, you can then create a data layer asset for it by right clicking in the content browser as well. Then you can link them inside the Data Layer Outliner by selecting the layer you created in your outliner and going into itās details and select the Data level asset you had created.
2 Likes
yes this behavior changed from 5.0 to 5.1. now you have to create and assign data layer assets before being able to use them like SupportiveEntity stated. My guess would be that this is going to be worked on in future versionsā¦
As this thread is titled ādata layers broken in 5.1ā, I might add that Iām experiencing a lot of level crashing on load (in editor) when using data layers (Iām also using packed level instances and datasmith scenes in my level at the same time and havenāt figured out yet what the cause for this isā¦ but since it regularly kills my levels I thought a warning might be in order.
Hey there @akaChrisV! Welcome to the community! Iāve been tracking that there are some data layer issues occurring in 5.1 such as crashing when an undefined layer is swapped on/off or any assets added to it. Are you also experiencing crashes related to the Data Layers during transfers?
Iāve had an assortment of issues with switching my scene to Data Layers / WP in UE5.1. Most notably:
- Loading Level works fine (e.g. swapping between multiple levels) until after Engine Restart where level crashes on load (in editor)
- Creating a packed level instance of static meshes which originate from a datasmith scene and are part of a data layer, unreal becomes unresponsive - eventually crashing.
These occur with all data layers created and assigned, so no unassigned data layers were present. The map crashing on load issue is hard to track since an engine restart is required and multiple changes occurred in between.
Oh yeah thatās way beyond what I have come across, but I have seen a significant rise in issues with the Data layers/WP in general this build. I did a bit of digging in the source to see if I could find exactly where the issue stemmed from (why itās a nullptr since it should be passing it clearly across every time) but there were more changes to Data Layers than I thought so Iād definitely just leave a full report on the matter since you can replicate most of the issues. I canāt formally replicate almost any of them myself besides the unassigned data layer bug.
Thanks for all of your insight on this, itāll help me get some solid information in the future.
Linking to outdated docs does not actually help 
, I have just started to learn the data layers and I watched some videos and it seemed clear and handy. Now with 5.1 having to manually create asset for every single data layer does not make sense 
Also why the very handy menu option āAdd selected actors to new data layerā (which docs claim is there) was removed? Once set up data layers can be useful but currently it is near unusably complicated and slow. Please fix this i.e. make it to work the same as in 5.0 
It seems there are many other issues with data layers in 5.1 as well (based on what I have read here and elsewhere) so I think I will stay away from them and wait for fix before starting to learn them for real.
2 Likes
Hey there @AnttiNu! Sorry about that, at the time I was unaware of exactly how much had changed with Data layers from 5.03 to 5.1 outside of needing the assignment. Unfortunately some of the changes have caused a couple of issues in the original workflow and some of them had been noted. I agree with the recommendation to hold a bit until they are clear for sure.
Ok, thanks, then I will wait, now I know I was not doing something wrong
1 Like
Hi! There is āLayersā that is no longer functional in the Open World Template (possibly just due to WP being on). The new Data Layers window is I think what we are looking for here! Under Window > World Partition > Data Layers, you can right click and create a new data layer right in the window per the old workflow, then select all your actors and add them to the selected data layer.
3 Likes
Oh man. Having to create and assign data layer assets makes using Data Layers really slow and cumbersome to use now. It was easy to use in (5.0.3). I use layers all the time to quickly group and hide stuff as I put a scene together but itās just a pain to use now. Also once a data layer asset is assigned, using the right click āRename Selected Data Layerā does nothing since the name is coming from the new data layer asset that is assigned.
Exactly. And it is still broken in 5.1.1 so it is unusable. Luckily I donāt need that large areas now but Iām sure all World Partition users are āthankingā Epic for this new āfeatureā
I get crashes whenever I try to load my level with data layers referenced. My only workaround for this is to load the level as the startup level for the editor. When I do that, there is no crash.
just wanted to point out that the system works pretty well here (5.1.1). i didnāt use the system before. but with 5.1.1 you just need to create a data layer asset, then add you stuff to it
For me, Iām missing the āRuntimeā settings in the Data Layers Details panel, and I canāt seem to unload Actors at runtime from the Level Blueprint using the Set Data Layer Runtime State node. I made a bug report regarding this. I guess weāll seeā¦
In the meantime, does anyone know how to make Actors actually unload? I have some Actors in my scene that I want to specifically hide / not-have in-game (until some condition triggers). Think the Dark World in the Valley of the Ancient demo.
Maybe Iām using them wrong; let me know if soā¦ but since thereās other DL-related bugs hanging around, Iām hoping one of you knows this is indeed brokenā¦?
1 Like
Yes that is the only way now but to me that is clear bug. In 5.0, you could easily create new data layer from selected actors, now you first need to create the layer, then create the asset for it and THEN you can move actors to it.
And that you need to do for EVERY layer, that cannot be the workflow by design.
Or if it is, then I would like to see someone explaining the logic behind that as there is none 
I have a problem where I created a datalayer to setup a race to get spawned in, but now when I go a x distance from where I spawn i lose all actors and theyre gone and im stuck as a cameraā¦ like why? cant figure it out. doesnt matter if I activate the datalayer or not
or when i open the datalayer(via a triggerbox) I get respawned where I started and then does the same thing
Hi DEVs, as an old 4.26 chaos beginner, after many years of learning, I write something again. First of all thanks for the great work on the UE and the many further developments.
But letās get to the point after creating a data layer and a data layer asset.
Simply right-click on the data layer in the content browser, on edit and you can change the data layer type to runtime. Have fun
Same thing here. I donāt have the Runtime settings in the editor, and Unloading node does nothing. Can you share the link to the reported bug?
1 Like