If the attached an8 file is opened and switched to Sequence Mode or Scene Mode, Anim8or crashes. Oddly, if the figure (and object) are imported into another an8 project, the figure can be added to a sequence and work as long as the figure is not modified. If an attempt is made to alter the figure, Anim8or will crash.

This file was created by a prototype SMD file importer (similar to the BVH importer) that I am writing. This crashing behavior occurs regardless of whether the object is added to the skeleton. A bare skeleton causes the same behavior.

Oddly, if the figure (and object) are imported into another an8 project, the figure can be added to a sequence and work as long as the figure is not modified. If an attempt is made to alter the figure, Anim8or will crash.

Seems to be not directly related to the zero framerate. So you might not be completely out of the woods yet. (I have not checked this part)

With fixing the framerate issue, you can switch to the Sequence or Scene Mode without Anim8or crashing, but if the figure is clicked while in Skinning mode, then changed to Sequence or Scene Mode, Anim8or crashes.

Can anyone see anything wrong with the bone weighting section of the an8 file?

No clue for the why at this side. (Although I seems to vague remember some similar (general)issue.)

Anyway. Confirming this one for 1129, although at this end its the returning to Figure mode that triggers the crash. [XP]- Load example file. (with the framerate{0} part fixed.)- Switch to Figure mode.- just in case: Flat-view + "Flat Outline" enabled.- Activate Multi-Bone Skin.- Click Mesh.- Switch to other mode, and back to Figure mode.* Crash.

The crash is definitely caused by the 0 fps frame rate. Anim8or divides the frame number by the frame rate using integer arithmetic, and dividing by integer 0 crashes. I'll fix Anim8or to prevent setting the frame rate to 0.

Mmm. To me that kinda reads as only the first issue is picked up.So just in case, there a actually 2 unrelated issues here. Msg 5 being a run down on issue 2. (which can also be triggered by just using a simple Mesh-Object inside the Figure editor.)