Kistler COPOptimisation name inconsistent with Codamotion ODIN 2.0 exports

Open3DMotionGroup / Open3DMotion

Other

5 stars 2 forks source link

Kistler COPOptimisation name inconsistent with Codamotion ODIN 2.0 exports #59

Closed drjrm closed 1 year ago

drjrm commented 1 year ago

Force calculations based on ODIN 2.0 exports would not receive the COP optimisation field because it was named differently in ODIN 2.0 as COPCorrection. Recommend renaming to the original COPCorrection.