Likely improper reset notifications sent out of the biped. Unfortunately CS is a stagnant tool in the sense that plenty of bugs still exist in it, and it has not been actively developed for years. Since an improper reset notification cannot be distinguished from a proper one, tyFlow doesn't know that it shouldn't update and I have no way of filtering such messages manually (usually they exist in the form of a generic REFMSG_CHANGE message sent through the max pipeline...so tyFlow can't decipher when one is sent improperly, compared to a proper change triggered by user input).
You can set the simulation reset mode to manual from the editor right click menu to at least disable auto re-caching when a change notification is received.
You can set the simulation reset mode to manual from the editor right click menu to at least disable auto re-caching when a change notification is received.