Timeline not playing at start of scene (2018.3.14f1)

Hi everyone!

I'm wondering if anyone have experienced something similar to this case.
We have a main scene on which we have a set of timelines that are played depending from where it was called, i.e. at first, timeline1 is played, after going to a 2nd scene and come back to main scene timeline2 is played and so on. Everything was working correctly, however after adding more functionality on the main scene (textures, video, mainly) the scene stops and no timeline is played. The game is not frozen as the navigation panel we have works correctly (it only has buttons to exit, go to website and restart scene), however the timeline does not play.

Our first clue was cpu/memory issues, we check the profiler and started to reduce textures, shaders and disabling components added afterwards, reducing significantly but with the same problem.

We exported the game to a newer version but the issue persists.
The problem occurs in editor and exported game for windows and macos tested in different machines.

Does anyone have experienced something similar or could give us an insight on what the problem could be?

Thanks a lot in advance for your invaluable help!

 

Did you check the play on awake option in playable director?

 

Thanks for your response jin-archipin, yes, I checked with a single timeline and play on awake enabled, however, as we are deciding which timeline to play depending on the scene, we play them manually, as:

Code (CSharp):

1.  
2. void Start()
3.     {
4.         PlayableDirector current = timelines[currentTimeline];
5.         current.Play();
6.     }

so, we need to have the play on awake option disabled to avoid playing them all

 

I have no idea then.. If I were you, I will make a debug playable track and put the track on every timelines to check if the timeline is working fine.

 

Thanks for your answers! I forgot an important thing to mention. In the editor, if we play the main scene directly, the timeline works perfectly. The problem only occurs when we call the main scene from another (i.e an introductory scene). This flow worked correctly in the past, were we specify through a script which timeline to play before loading the main scene (we have verified that the timeline is being called correclty, it just don't play).
Just to mention, the profiler looks like this at the beginning of the main scene with a spike when loading everything. It have reduced significantly the amount of things loaded.

 

Yes, all the playable directors are in the same scene, but only one is played at a time. We have found that if we call the main scene at first (not calling from the introductory scene) it has load correctly; just to remark, the introductory scene has one button which loads the main scene after playing a timeline-cinemachine animation, could it be problem of memory or garbage collection after moving scenes?

 

I'm having a similar issue. I have a timeline set up in a scene. When I play that scene directly, the timeline starts (it starts via a script). If I play another scene, and load the scene with the timeline using SceneManager.LoadScene the timeline never plays. I tried all sorts of things. Setting it to play on awake and then enabling the playable director; tried using PlayableDirector.Evaluate(); tried using PlayableDirector.Pause() and then PlayableDirector.Play()... Nothing works. I can see the timeline in the editor is played when I open it while the scene is still running (the play button in the timeline window is highlighted) but it's stuck on frame 0. If I press play (which actually stops it) and then press play again, it starts playing.
I'm using 2018.2.6f1.
Please help, this is driving me crazy.

 

I just tried setting the update method to "GameTime" instead of "DSPClock" and it plays. I can use it as a workaround for now, but I would prefer to use "DSPClock" if possible.

 

Ohhh, thanks for the input!! and sorry for the late response, we haven't realized anything about DSP Clock and GameTime update methods, I guess we use the default one. We are not sure about that.

On the other hand, we have tried the suggestion of Loading Scene A, Load Scene B, Load Scene A (where A has the timelines) and have found that actually, when switching from Scene B to Scene A, the freeze occurs, so we start improving the Scene B objects in order to generate less resource consumption, however we still have the issue.

An approach we have been researching is the scene/assets preload to not load everything in the main scene at once, but we still can't figure out how to do it (we are kind of new in this matter). Do you think this could be a valid option to solve the issue? and what path could we follow if most of the objects we load are in the timelines?

Thanks again for your appreciated help!
Regards!