This page includes sections for:

Bugs, Issues, and Feature Requests

We're in the process of updating our bug and feature request trackers, in the meantime, we'll summarize any significant bugs and issues associated with 3.0 on this page. A full list of bugs can be found on the old bug tracker on Simtk. You can also report bugs and make feature requests here:

  • No critical bugs have been reported

OpenSim 3.0 Updates

If we discover critical bugs or make important updates, we will update the latest version of our software, OpenSim 3.0 on Simtk. Updates will be posted with the naming convention "_u1", "_u2", etc. Updates are summarized below:

Update u1

Date: October 20, 2012

Fix: We changed "pose" behavior in the GUI, so that setting the model in any pose restores velocities, muscle activations, and other states to the model default. This update primarily affects people running forward simulations with no explicit initial states file specified.

Description of Issue: In 2.4, setting and changing poses only affected the model coordinates. So if you played to the middle of a simulation, then selected “Pose->Default”, the model coordinates would go to defaults, but no other states would change. These states weren’t used anywhere, though, since forward simulations always started from the model default state (if no initial states file was specified). In 3.0, we changed forward behavior so that if no file is specified, the simulation starts from the current state of the model. This created potential confusion and thus problems for the old pose functionality. If you load a motion or generate a simulation, play to mid-motion, then choose Pose -> Default, you would get a state that combines the default coordinates with the other states from that frame of the motion. Thus Setting Pose -> Default would give you different results if you load a model fresh vs. loading a model, then loading a states file or generating a simulation.

Fix Details: With the fix, you can always use Pose -> Default to get back the full default state of the model (as if loading it fresh). You can also still do things like generate a simulation, go to the middle of the resulting motion, and rerun forward to pickup and continue the simulation from where you left off.