Reducing the visual data of flexbodies in MotionView

Christopher_Fadanelli
Christopher_Fadanelli
Altair Employee
edited September 17 in Altair HyperWorks

For models that include multiple and large flexbodies. When animating the H3D file, it contains additional flexbody data (features & spiders).  This uses resources  (animations take longer to process) and makes the display rather cluttered. To reduce the impact the flexbodies h3d has on the resultant animation size, use the MODEL card in Optistruct FEM during CMS to limit the model data that goes into H3D for output. The CMS modeshapes will be calculated based on the full model but the data written to FlexH3D for visualization will be based on what is specified in the MODEL card. This has to be done during the CMS run before you start the MotionSolve run. MotionSolve's post processor will then use the data from FlexH3D for generating the animation h3d.

 
MODEL
I/O Options and Subcase Information Entry
The MODEL command can be used in the I/O Options section to request output of only a subset of the model and related results for H3D and OUTPUT results files as well as for CMS superelements.
Format
MODEL =
elset
,
gridset
,
rigidset