Skip to main content
S
Sal-la
New Participant
December 7, 2017
Answered

Error "handle value is not a number"?

  • December 7, 2017
  • 3 replies
  • 6171 views

Hi! I'm getting this error all the time now when ever I try to do some changes to my scene and I have no idea what it is all about: "handle value is not a number. Error code: (Container.js:215)" and it's making me mad...!

      This topic has been closed for replies.
      Correct answer Jeff Almasol

      Hello all... The updated version of Character Animator, version 24.2, is now available in the Creative Cloud desktop app. It contains the fix (previously only available in the Beta build) for this issue. Thank you for your patience and help resolving it.

      3 replies

      Jeff Almasol
      Adobe Employee
      Jeff AlmasolCorrect answer
      Adobe Employee
      February 8, 2024

      Hello all... The updated version of Character Animator, version 24.2, is now available in the Creative Cloud desktop app. It contains the fix (previously only available in the Beta build) for this issue. Thank you for your patience and help resolving it.

      W
      wael5CE7
      New Participant
      February 14, 2024

      I have 24.2 and it's giving me this error constantly.  What should I do?

      Jeff Almasol
      Adobe Employee
      Jeff Almasol
      Adobe Employee
      February 15, 2024

      Hmm, sorry that 24.2 isn't completely solving the issue for you. Are you seeing this when you are opening a scene that contains a puppet that uses Dangle?

      Are you seeing it if you start a new project and use the Chloe template puppet (from the Home screen)?

      We might need to get a copy of the project that contains the scene/puppet causing the issue to diagnose further. If you'd like us to diagnose a specific project, can you archive the project folder as a .zip file, then send me a direct message with a shared link to the .zip file?

      Thanks.

      K
      kind_rebel98A2
      New Participant
      September 14, 2019

      After getting this annoying message, I searched and what I saw here, gave me a clue and I went back and deleted the dangles and added them back and it was fixed. So I suppose there is an issue with the dangle handles.

      alank99101739
      alank99101739
      Brainiac
      September 14, 2019
      I think there was a previous problem for dangles not over artwork or in the right mesh. You might have fixed it without realizing when creating again
      DanTull
      Adobe Employee
      DanTull
      Adobe Employee
      December 12, 2017

      I'd be curious to see this project. I have seen an error like this in a rather abusive use of the Physics behavior, but I have seen it occur in analytics just often enough that it makes me think there is some more mainstream use that hits it as well.

      If you'd be willing to share a project that is exhibiting the error more commonly, I'd be interested in doing a deeper diagnosis. If you're interested, I can contact you privately with contact information.

      Thanks -- Dan Tull

      alank99101739
      alank99101739
      Brainiac
      December 12, 2017

      I have my project up in Adobe Cloud, and am happy to share it with you. Just reach out to my email and I will work out if I can just share the whole project with you then email you directly instructions on the most likely way to trigger the problems I typically see.

      FriedMushroom
      FriedMushroom
      Inspiring
      May 1, 2018

      I stripped down a copy of your project to the smallest thing that still reproduces the error.

      It now has 1 scene, with a single puppet with 1 layer (a few groups down), 1 behavior (Physics, more specifically Dangle), and 2 handles (besides the origin).

      Since I only have the one behavior I also switched to duplicating a 1 frame take of a Physics parameter to undo/redo. The key part about that seems to just be that it makes the stage refresh rapidly.

      Two things are odd about the layer and handles that remain:

      1. The layer has several strands of hair that are separate from the main clump. Those are causing Auto mesh mode to choose a rectangular shape* instead of one that follows the outline of the layer's content. Rectangular meshes can also make the movement look strange.

      2. The dangle handles on this layer are not on the mesh.

      I think the second one is the part that is causing the error. When I move the two handles onto the mesh, the error stops happening.

      I'm going to get this filed as a bug, but wanted to post back since this information might help you and others avoid this issue.

      Thanks! -- DT

      * worth noting that I have mesh visualization enabled in the puppet panel. that pentagonal button on the far left of the toolbar toggles it, it can be quite handy.


      Yea.. I hope this bug is fixed soon because idk if I have the time or comprehension to be able to understand all that.

      The only thing I picked up was the possibility of dangle handles being outside of an objects meshing?

      For me this error mainly comes up if i delete a scene in a project, or certain audio tracks in a scene (which I would do if I duplicated a scene to be able to use performances from it with different audio). neither of these I’m not sure how would correlate with the error seeing as everything works fine originall.

      A different instance that just happened to me was after I recorded a mouse controlled eye gaze performance.

      Luckily there are numerous ways and work around to do most things, but I find myself getting very frustrated as well

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices