Hello everyone,
Adding our findings to this thread as we believe we’ve managed to isolate a more specific and consistently reproducible version of this data layer bug, which started happening for us after the recent updates.
The core issue seems to be that data layers break after the first successful push. Any subsequent changes to a data layer’s contents (like moving a prop or adding a new one) cause those props to permanently disconnect from the data layer’s loading state in a live session.
Exact Steps to Reproduce the Bug
- Create a new Data Layer (e.g.,
DL_Test_01). - Place a few props from the Content Browser into your level and assign them to
DL_Test_01. - Launch a session by clicking Push Changes.
- Result: Everything works correctly. The props in
DL_Test_01are properly unloaded by default as expected. - End the session. Now, back in the editor, make a small change. Either move one of the props already in
DL_Test_01or add a new prop from the level to that same data layer. - Launch a new session by clicking Push Changes again.
- Result: The bug now appears. The props you modified or added will now be visible in the game, completely ignoring the fact that their data layer is unloaded. They seem to be permanently “stuck” on.
Temporary Solution / Workaround
Through testing, we found a temporary (but cumbersome) workaround:
Instead of modifying an existing Data Layer, you must create a completely new Data Layer to replace the existing one for any new prop you want to add or modify.
For example, if you need to add more props after your first push, do not add them to DL_Test_01. You must create DL_Test_02, add the new props to it (optionally pass the props from DL_Test_01 and remove it), and then push the changes. This seems to work correctly, but it is not a sustainable solution for large projects.
Hoping this helps.