We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

"Computed radius is NaN"

Home Forums Bug Reports and Feature Requests "Computed radius is NaN"

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #21922
    GlifTekGlifTek
    Licensee

    Error Message: “v3d.BufferGeometry.computeBoundingSphere(): Computed radius is NaN. The “position” attribute is likely to have NaN values. ”

    I have an animation with 36 Shape Keys.
    It plays, but does a very strange glitch, inverted shape at the beginning (and that’s where i get the messages).

    some of the position values were “-0” in the Y so i fixed those. still get the error.

    i found that it kept listing “ShapeKey36” over and over in the attributes of the console details so i deleted that shape key and channel…
    but then the errors started saying “Shapekey35″… soo… :unsure:

    what’s the best way to deal with this type?
    thnks.

    verge 2.17 pre2
    blender 2.81
    windows 8.1
    firefox latest

    #21927
    Yuri KovelenovYuri Kovelenov
    Developer

    Hi,

    so you are getting this error when you just do Sneak Peek, or you’re using some additional JavaScript code?

    3D Verger, the CEO
    LinkedIn | FB | Twitter | VK | 新浪微博

    #21944
    GlifTekGlifTek
    Licensee

    Hi,
    so you are getting this error when you just do Sneak Peek, or you’re using some additional JavaScript code?

    no additional JavaScript.
    I still get it in Sneak Peak.

    #21985
    Yuri KovelenovYuri Kovelenov
    Developer

    got a link to the project?

    3D Verger, the CEO
    LinkedIn | FB | Twitter | VK | 新浪微博

    #22461
    GlifTekGlifTek
    Licensee

    got a link to the project?

    i fixed it.
    i had some seriously messed up F curves.. had to set my default keyframe interpolation to be linear / vector.

    but let me tell you..
    you have the limited number of shape keys per object as 6 in the manual.

    i have over a dozen objects having over 36 shape keys each working fine in my Verge3D project.

    …is the number limit a barrier to having the ABSOLUTE option for Shape Keys work?
    things would be so much simpler if we could use the ABSOLUTE option.

    just wanted you to know about me being able to use 36 shape keys (or more, haven’t tested)…
    (not the stated 6+1 limit)

    #22467
    Yuri KovelenovYuri Kovelenov
    Developer

    interesting! are you sure each of those 36 shape key assigned to the same object actually work?

    Will think about absolute option!

    3D Verger, the CEO
    LinkedIn | FB | Twitter | VK | 新浪微博

    #22468
    GlifTekGlifTek
    Licensee

    Well let’s go back to this thread full circle…
    “ARCS” AS “PATH” IN PARAMETRIC MORPHING? (3D PIE CHART RADIAL GROWTH)

    After a month using material solutions to fake it, I came back to it and fixed it.
    Yes lol it’s working very well.

    One object with 22 parts, 36 shape keys… Then I separated the object into its separate 22 parts which kept the 36 shapes each…
    Which were changeable each.

    • This reply was modified 7 months, 1 week ago by GlifTekGlifTek.
    #22471
    GlifTekGlifTek
    Licensee

    What’s interesting, is I went to recreate it (with more refined detail) because of the perceived bug, and that attempt rendered imperfectly.

    So I went back to the saved buggy version and experimented, eventually correcting it.

    I’m going to try to fudge the new version to work, using what I did to the original.

    #22477
    Yuri KovelenovYuri Kovelenov
    Developer

    glad you worked it out! :good:

    3D Verger, the CEO
    LinkedIn | FB | Twitter | VK | 新浪微博

Viewing 9 posts - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.