Data Layer object destruction broken and invisible collision issues

Summary

Since the Update 37.10 when Unloading and then Loading Data Layers, some props stay invisible and now cause weird Invisible Collision hitching or are visible but have no collision anymore.

This can also happen when some objects in the data layer get destroyed by players. Instead of the usual animation the object plays no destruction animation, turns invisible and also collision stays even if its invisible

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

Connect a data layer to a lot of props, unload and load these props, after a few unload / loads some props stay ā€œunloadedā€ but now have invisible collisions and some loaded props now stop having the destruction animation and also stay invisible

Expected Result

Normal Load / Unloading of Data layers, no props to stay ā€œunloadedā€ / Invisible and cause weird Invisible Collision hitching.

Observed Result

Some props in the data layer stay ā€œunloadedā€ and cause weird Invisible Collision issues and some loaded props now stop having the destruction animation and also stay invisible

Platform(s)

all

Island Code

3304-3441-2030

Video

Video showing the loaded props that now have issues with destruction animation and leave invisible collision:

Additional Notes

This bugreport also mentioned this but was closed due to not being able to reproduce the issue again, but probably very related and is still happening in the current version to me

Its happening very regularly in the provided map code as the game is basically about destroying props and the zones reload very frequently. What I already found out is it is mostly the same props and buildings in a certain data layer that break all the time while others are never breaking in the data layer.

If needed i can try to find a broken lobby and collect more video footage or send logs

I can confirm issues. In our map when we unload a data layer and reload to reset a zone after a fight NONE of the actors appear. They are invisible, but the collision is partially there. This is GAME BREAKING for us. CRITICAL.

Solution for us was to delete The LOAD level sequence and recreate them. It appears sequences created before 37.00 are not happy with new version.

2 Likes

For yours all did not load? On my side its only a certain amount of objects that do not seem to load correctly

Also my current guess for when stuff is getting stuck in a bugged state is when unloading and loading too close together some objects might get stuck.

Next thing I will try is space unload and load more far apart in the sequence!

how far apart in time are your unload an load sequence?

Ok for anyone encountering the problem here is a fix. In my case the unloading adn the loading of the data layer was to close together so when loading again some parts of the unloading might have not finished yet and it got stuck

The fix: At least 2 or 3 second between loading and unloading and the issue is fixed

@Flak I think this one can be closed as it was just an issue of loading and unloading to close together :slight_smile:

Hello! This is happening to me too, this is present in my published game and is critical as it made players leave my game cause they were ā€œstuckā€. It’s happening randomly. It never did that before so please fix it asap!!! I even recorded you a video.

I’ll try that, thank you so much in advance! <3

1 Like

I use separate sequences for load and unload. In Verse I space them 2 seconds apart.

Not sure I agree. If I spread the load and unload to 15 seconds it was still happening for us. And it was a little random. As I stated earlier deleting all the Load Sequences and recreating them worked for us.

1 Like

It happened to me when I had a ton of players (14), I’m not sure if it’s due to someone’s bad wifi or not.

FORT-977692 has been added to our ā€˜To Do’ list. Someone’s been assigned this task.

2 Likes

It’s happening again for my map and made leave 4 players at once. Please fix that it’s impacting my map a lot as I load mini-maps using data layers.

@ZeroShotBob Hello, have you ever got the bug after removing/adding back the level sequencers? I did literally delete them, published and the bug is still happening. Did you also put new sequencers devices?

For us the issue was the data layer would not display after the first iteration. First was good, second or more would not appear.

We unload unused layers and that seems to be okay.

I just deleted the level sequence for adding the data layer.

So once I recreated them I had to put them back in the Cine Seq Device.

What I did:

  • Removed the sequence from the Cine Seq Device. Saved and Closed UEFN.
  • Restarted UEFN
  • deleted the Level Seq.
  • Updated redirectors. Saved and Closed UEFN
  • Recreated all the sequences (new names) and re-added back to the Cine Seq Dev.
1 Like

All my data layers are unloaded by default too! Problem is, in my case, it’s completely happening randomly. My map depends on it and I do load/unload a map after each map vote. What are redirectors? But I’ll test all that, I just hope they will this issue soon.

Right click on a folder in the Content Browser. You will see some options concerning redirectors. When you move or rename assets it keeps some sort of reference to its original name and location and keeps the name tied up in memory. Fixing these redirectors makes the map cleaner.

1 Like