takes recall which objects are active

[leith]

currently, an individual take (pt2 file) forgets what objects (rigids and skeletons) were active and tracking when the file was created. This makes it tedious to do batch processing as rigids and skeletons don't turn themselves on and off as you move from take to take. If we could save the knowledge of active objects, take for take, we could then actually use the "trajectorize all" function and move about data more freely.

[VincentG]

Dear Brad,

This is something we are looking into, and have created a feature tracking ticket for, unfortunately I don't have a timeline for when this maybe implemented with the Arena software.