Resolved Manual Evaluation doesn't work

I'm trying to achieve a visual style in my game and the animations are required to run at 24 fps, not at game time. Setting both the animator's and the rig's playable graphs to manual and evaluating them myself doesn't work though. Updating properties in editor or via script just resets the value to it's starting value. Is there anyway to manually tick the rigging?

 

I upgraded the package but manually evaluating the rig using the new method doesn't work. It updates for one frame then stops, even without the custom fps setup. The example script included doesn't work either.

 

To provide more information, my animation setup is made of two animators. A main one and the other has a subset of animations. The RigBuilder helps with combining the two animations. But doesn't work when manually evaluated.

The function I am using is updated at the specified frame rate (24)

Code (CSharp):

1.  
2. private void UpdateFPS(float time) {
3.     // Time is 1f / 24f
4.  
5.     // Weight changes and such
6.  
7.     mainAnimator.playableGraph.Evaluate(time);
8.     if (otherAnimator.runtimeAnimatorController)
9.         otherAnimator.playableGraph.Evaluate(time);
10.     rigBuilder.Evaluate(time);
11. }

All graphs are set to manual mode and the RigBuilder is disabled.

Without Manual Evaluation:
Link


With Manual Evaluation:
Link

 

As much as I wish it weren't true, creating a new playable graph doesn't work either. I've modified my code and used the example you provided in a new blank project. But, the same issue persists. The new project was made in Unity 2021.3.5f1 and I used version 1.2.0 of the package.

Just in case I have also included more footage of the issue.
(The footage was recorded using the example code)

 

I haven't used it extensively myself, but I was able to get manual evaluation working by sticking my playables in the Animation Rigging graph instead of making my own graph. That way there's only one graph so its Evaluate just works.

Also, I'm not sure if it's still the case, but when I first started using Playables there were some issues with setting the update mode to Manual and I was able to get better results by calling graph.Stop() instead.

 

Thanks for the tip Kybernetic!
Putting everything into one graph solved the problem.

Here is exactly what I did for those who stumble upon this problem.
A playable graph is created and I create two outputs, one for the main animator, and another for the subset of animations. The main is assigned to it's runtime controller, while the subset is left open for other animations set at runtime.

Thanks again, Simon and Kybernetic!

Code:

Code (CSharp):

1.     private void OnEnable() {
2.         playableGraph = PlayableGraph.Create(gameObject.name + ".HumanAnim");
3.         playableGraph.SetTimeUpdateMode(DirectorUpdateMode.Manual);
4.  
5.         // Create main playable
6.         var mainPlayable = AnimatorControllerPlayable.Create(playableGraph, mainController);
7.         var mainOutput = AnimationPlayableOutput.Create(playableGraph, "MainOutput", mainAnimator);
8.         mainOutput.SetSourcePlayable(mainPlayable);
9.      
10.         // Create subset playable
11.         subsetOutput = AnimationPlayableOutput.Create(playableGraph, "SubsetOutput", otherAnimator);
12.  
13.         // Add rigs
14.         rigBuilder.Build(playableGraph);
15.  
16.         FPSProxy.OnUpdate += UpdateFPS;
17.     }
18.  
19.     private void OnDisable() {
20.         FPSProxy.OnUpdate -= UpdateFPS;
21.  
22.         if (playableGraph.IsValid()) playableGraph.Destroy();
23.     }
24.  
25.     private void UpdateFPS(float time) {
26.         playableGraph.Evaluate(time);
27.         rigBuilder.SyncLayers();
28.     }
29.  

FYI: The RigBuilder is disabled, its just not in this snippet.

 

I'm trying something somewhat similar, in that I've got a lot of expensive Animators, and I'd like to only run a few of them every frame. I'd like to do this with playablegraphs, but haven't had any success. I've tried both rile-s's and simonbz 's snippets above, but it most definitely needs an Animator to not be disabled, and those Animators are definitely running at full tilt when enabled, as my framerate tanks as the number of Animators goes up even if I'm only calling Evaluate a few times a frame, and have all my UpdateModes set to manual. And in profiler, it's all DirectorUpdateAnimationBegin/End that's killing me.

Is there a step I'm I'm missing to ensure the Animator doesn't run? If I disable it, I get Tpose.

 

Why they didn't have designed the rig system to be ticked either manually or when the animator is updated ? Now I have to lose a whole day trying to make an obvious thing work