Cinematics not playing consistently. Do I have too many?

General Issues and Bug Reporting
, , ,
1

I’m experiencing an issue where specifically three of my cinematics decide to randomly not play - usually when I invite friends into my session and start the game.

There are three cylinders near the end of my game and they all have their own cinematic loop that rotates them at different speeds. I have many other cinematics playing that are working, but these sometimes fail to play and I haven’t figured out why.

I also have props later in the game being moved around with MoveTo() in verse and they’re not having any issues. Why are these specifically having issues?

Additional details:

The cylinders were chosen from Fortnite > Meshes > BasicShapes and their material is MI_Giallo_Noce_Marble_Tiles

My game has 11 cinematics set to always play on loop.

Also, possibly related, it has 50 different devices that call MoveTo() on different creative_props. 5 of those are looping from being called immediately after they end and the others are activated by triggers. I estimate ~34-39 of these going on at once during actual gameplay at max player count.

^All of those are working as expected

Edit: It might be worth noting that I have world partition (streaming) enabled

2

Small update.

I noticed when I set the spawn to the area around the cylinders, they rotate just fine. However, when I spawn at the intended start of my game and travel to the pillars they won’t work. This was all done in a solo session.

In the process of traveling to them, I pass by 7 other props with cinematics playing on loop that work just fine.

Unfortunately, this is game breaking in my case. Players will be unable to reach the end of the game without those cylinders rotating. Hopefully someone has an idea to solve this

Edit: When the cinematics aren’t playing, they seem perfectly still until I jump on them; it glitches and throws me off.

Edit2: It took quite a bit of testing to confirm this, since the issue wouldn’t always occur, but disabling world partition / streaming was what it took to prevent this issue.

1 Like