Question release virtual camera override immediately

When the timeline stops, it does not immediately switch to a regular virtual camera, but instead waits until OnPlayableDestroy to release. Is there any way to force an immediate release of the override?

May I know where OnPlayableDestroy is called specifically and if there is any detailed documentation available on it?

 

I think

OnPlayableDestroy

is called from the C++ layer so I can't help you a lot on detailed informations,
but it should be called when the PlayableGraph is destroyed (in a timeline scenario), which is when the PlayableDirector stops.
Notice that if you set wrapmode to Hold, the PlayableDirector won't stop playing after reaching the last frame. Set it to None if you want to stop the PlayableDirector after finished playing.

 

Thank you, I tested it and found that `OnPlayableDestroy` is called after Update and before LateUpdate. However, I still don't know how to trigger it immediately.

 

I could only give you some information, that the

OnPlayableDestroy

is called instantly if you directly call

playable.Destroy()

. So if you can find your playable, just destroy it.
This is my test code:

Code (CSharp):

1. using UnityEngine;
2. using UnityEngine.Playables;
3.  
4. public class TestDestroyPlayable : MonoBehaviour
5. {
6.     private void Test()
7.     {
8.         var graph = PlayableGraph.Create();
9.         var playable = ScriptPlayable<TestPlayableBehaviour>.Create(graph);
10.         Debug.Log("before destroy");
11.         playable.Destroy();
12.         Debug.Log("after destroy");
13.     }
14. }
15.  
16. public class TestPlayableBehaviour : PlayableBehaviour
17. {
18.     public override void OnPlayableDestroy(Playable playable)
19.     {
20.         base.OnPlayableDestroy(playable);
21.         Debug.Log("[OnPlayableDestroy] called.");
22.     }
23. }

The result is:


(I've also tested PlayableGraph.Destroy(), but it will postpone the desturction of the playable, making it be called after the "after destroy" Debug.Log)

 

Yes, that's correct. But it seems unsafe to directly call the playableGraph of the timeline since it manages itself. So, I moved the logic that needed to be handled into LateUpdate, and it worked out just as expected.