Altair MotionView 2021.2 Release Notes


The Altair MotionView v2021.2 release provides several enhancements and bug fixes to MotionView:
  • New MotionView Interface (Beta)
  • CM Labs-Vortex Translator
  • Multi-Disciplinary Tools Enhancements
  • 1D Electronic Stability Program (ESP)
  • Vehicle Aerodynamic Forces
  • Altair Driver Updates
  • N-Post Shaker Updates
  • Tire Test Rig
  • Vehicle Example Models
  • 1D Traction Control Update
  • CD Tire Licensing Update
  • Model Files Removed from Installation Package
  • Other Enhancements
  • Resolved Issues

New MotionView Interface MVX (Beta)

Over the next several releases, MotionView will be transitioning to a new graphical user interface framework and interface. A beta version of the first release of the new interface (MVX) is now available via the Start menu (HyperWorks 2021.2 MV).

Figure 1.
For v2021.2, the new interface has been extended with the following features:
  • Move Tool for model repositioning.
  • Rigid Groups - Group rigid bodies that move together.
  • New interactive contexts for Points, Joints, and Markers.
  • Show/Hide/Isolate features.
  • Ability to change variable names.
  • Live animation during Static and Transient solutions with MotionSolve (experimental – use environment variable HW_MV_LIVE_ANIMATION = 1).

MVX supports all existing functionalities of MotionView. Both versions, MVX and MotionView (MotionView 2021.2 from the Start menu) co-exist and can be used interchangeably today. However, the new capabilities highlighted above are only available in MVX.

MVX is being released as a beta functionality to solicit early usage and feedback for improvement. The functionality may contain unidentified defects.

Translator to Vortex-Studio

Vortex-Studio is a real-time simulation and visualization software by CM-Labs, an APA partner. A MotionView to Vortex-Studio translator is now available. Using the translator, a MotionView model can be translated to Vortex-Studio to simulate and visualize a proven multi-body system in real time for human-in-loop testing and immersive training. (

Translation supports transfer of commonly used entities in MotionView such as Bodies, Rigid Joints, Joints, Linear Motions, and Bushings.
Entities Comments
Bodies Rigid body only. Flex body and NLFE body is not supported.
Graphics CurveGraphics, Outline, Spring, Tire graphics are not supported.
Joints CV Joint, Screw Joint are not supported.
Motion Linear only. Curves, Spline3D, and Expressions not supported.
SpringDampers Linear only. Curves, Spline3D, and Expressions not supported.
Bushings Linear only. Curves, Spline3D, and Expressions not supported.
Forces Linear only. Curves, Spline3D, and Expressions not supported.
Contacts Only a collision rule is defined in vortex. No other contact properties are translated.

To use the translator, load the preference file (File > Load > Preference File) CM Labs Vortex Studio Tools that will add a Vortex menu. The menu contains a Settings dialog that will help to associate Joystick actions to motions in the model and cameras on bodies.

Multi-Disciplinary Tools Enhancements

  • New paired versions of actuation features are introduced; namely twinrod, twinstrut, and twinactuator.
  • New attachment feature "rod2cylinder" is introduced to define a rod to cylinder connection made of two equivalent cylindrical joints with friction based on deformable curves.
  • Improvements in existing rod, strut, and actuator features to align their behavior with the new paired versions of actuation.
  • Improvements in cable feature and all related cable demo models.
  • A bug related to units' management has been fixed in "road4durability" feature of Automotive.
  • Loading of Compose feature (Plot FRF) for MotionSolve in Activate has been automated.
  • Improved solids2motion and meshes2motion features to support meta characters in component names.

1D Electronic Stability Program (ESP)

MotionView adds a new 1D Electronic Stability Program (ESP) controller for the Car/Small truck library. The ESP is a driver assist system that improves the vehicle’s stability through intervention in the braking system. By individual wheel braking ESP can control the yaw moment of the vehicle, thus its steering behavior.

To use the ESP controller, select the Electronic Stability Program (ESP) (with ABS) option in the ABS, ESP and TC for Full vehicle with Driver model menu while assembling your full car in the Assembly Wizard.

Figure 2.
In the ESP configuration, the braking system is modeled in MotionView while ESP ECU, ABS ECU, and Hydraulic Modulator are modelled in Altair Activate and exported as an FMU. The schematic below illustrates the interaction of the ESP system with the vehicle model.

Figure 3.

Aerodynamic Forces in Vehicle Models

MotionView adds the option to include Aerodynamic Forces in full vehicle models. The option is available in the Car/Small truck library in the Assembly Wizard.

Figure 4.

The aerodynamic parameters are entered in a TeimOrbit property file .aae including Environment parameter; Wind velocity; Side Forces; Drag, Lift, Yaw and Roll coefficients.

Altair Driver Updates

The vehicle models in MotionView uses by default the -X as forward direction and -Y as left direction. In previous releases the Altair Driver only accepted the default vehicle modeling coordinate system to simulate the events.

In this release, by specifying the Vehicle Orientation in the AltairDriver panel, the model can be simulated in any coordinate system. You need to provide the “Front” and “Left” directions of the vehicle to the Driver by specifying this on the user interface panel.

Figure 5.

N-Post Shaker

The N-post Shaker can now be used to simulate event with vehicles in any coordinate system. In previous releases, as for the Altair Driver, the vehicle could only have -X as forward direction and -Y as left direction.

In the N-post panel, now you will see the vehicle orientation option to enable different coordinate system setup. You need to provide the “Front” and “Left” directions of the vehicle to the event by specifying this in the user interface panel. Upon adding a new n-Post event, these directions are copied from the AltairDriver set-up. However, if this is changed in the Driver user interface panel after loading the n-Post event, you need to repeat the same change in the existing n-Post event’s panel as well.

Figure 6.

Tire Test Rig

MotionView adds a new Tire Test Rig to enable you to test the tires under various conditions of Lateral slip, Longitudinal slip, and vertical loads.

Figure 7.
The tire test rig can be added in the Assembly Wizard of Car/Small Truck. The events are added using the Task Wizard.

Figure 8.
In the three events available (Lateral slip, Longitudinal slip, and vertical loads), a combination of Loads, Slip angles, and Camber angles enables you to capture the main tire outputs with variable conditions. The events contain a Report to quickly visualize the results.

Figure 9.

New Vehicle Example Models

Two new examples have been added under the Example models:

Figure 10.
  • Electric Sport Bike: A motorcycle model parametrized to enable AltairDriver at any coordinate system, including an electrical powertrain.

    Figure 11.
  • Pickup Truck: A 4x4 vehicle with an IC engine and ABS control model.

    Figure 12.
In addition to the new examples, the 3-wheeler models (Auto Rickshaw, Three Wheeler (2+1), and Three Wheeler (1+2)) were updated to include better suspension parameters and graphics.

Figure 13.

1D Traction Control Update

In the 1D Traction Control, FWD and RWD had to be specified in the 1D Activate model before exporting the FMU. In this release, a switch was added in the Traction Control system in MotionView. By selecting FWD or RWD vehicle Traction, the controller is defined automatically to the desired setting. If the drive axle is switched after creating the model, then the proper value for traction control needs to be set inside the traction control Forms.

Traction Control for 4WD/AWD vehicles is not available in this release. This option will be considered for future releases.

Figure 14.
Known Issue
Traction Controller does not work for 4WD/AWD configuration vehicles. The option to add Traction Controller for such vehicles has been withdrawn.

CD Tire Licensing Update

CD-tire files can be used with Altair MotionSolve either by enabling the CD-Tire licensing with Altair licensing or using the CD-Tire standalone license.

With an Environment Variable you can now specify which license MotionSolve checks first.
Altair license file will be checked for CDTire license. If it fails, Flexlm licensing will be checked for CDTire’s own license.
ALTAIR_LICENSE_FOR_CDTIRE≠1 or not available
Flexlm licensing will be checked. If it fails, MotionSolve will exit the simulation.

Model Files Removed from Installation Package

To reduce the footprint size, the following tutorial model and demo model files are no longer included in the local installation. You can now find zipped tutorial model files and demo model files on Altair One via the Altair Community, Altair Marketplace, and Altair Connect sites. Altair recommends that you create an Altair One account and use it as your primary portal to access product documentation, a Knowledge Base, and customer support.

Tutorial Model Files
  • HyperWorks
  • HyperWorks Collaboration Tools
  • HyperWorks Desktop
  • MotionView

Other Enhancements

  • CAD graphics reading performance has been significantly improved.
  • The new SpringDamper graphic has options to control the display of the spring and the damper.
  • Graphics has a new attribute “hide_in_post” to avoid writing the graphics into a MotionSolve result H3D after the simulation.
  • Validity checks are now performed for properties of Beams and Polybeams.
  • Datasets attributes are now available for edit in Data Summary.
  • FlexTire file created during transfer of AutoTire to EDEM has been updated as per the latest form prescribed by Pratt-Miller/FlexTire.
  • The “Auto color” option in View Reports has been changed to “Use report colors”. Turning this option on uses the color specified in the report template while generating plots. The default is set to off since it is desirable to have unique colors for curves when overlaying results.

Resolved Issues

  • Spring graphics from older versions were hidden when the model was read in 2021.1.
  • Certain models took multiple clicks on “Fit” (the “f” key) to fit the model.
  • Certain specific models with CAD graphics built in v2019 had their components mismatched with bodies when reading in v2020 and later.
  • File for user defined spline not written to MotionSolve Py.
  • Export to Py fails when the model contains user defined Modal Force.
  • Load Export: Opening Meta file on runs with Polybeam results in an error.
  • Load Export: Incorrect tabulation of force values when multiple outputs are requested with a different reference frame.
  • Load Export: Missing output when multiple outputs are defined on the same body.
  • FMU: FMU panel did not identify the correct number of states.
  • FMU: Parametric expressions in FMU parameters are not correctly evaluated during export to MotionSolve.
  • Memory related application error is fixed for “Generate H3D from EDEM” tool. The tool now gives appropriate message if memory is insufficient.
  • Application error during copy operation in model containing components with special characters.
  • MotionView crash with model containing AutoDriver during export to MotionSolve when path exceeds a certain limit.
  • Nodes dialog is not active on the flexible body panel in Abaqus solver mode.
  • Using interactive HyperMesh in Import CAD/FE using HyperMesh gives an application error.
  • AutoTires now supports different Point Cloud Data (PCD) roads for each individual tires.
  • The friction transition velocity in the LeafSpring Builder now has better default values.
  • CD-Tire representing the rigid tire when using with PM-Flextire and EDEM was displaying the wrong error message.
  • If not specified a handling tire in the PM-Flextire, MotionView adds a default tire and issues are no longer displayed.
  • Setting Initial Conditions for vehicle models enhanced to support the AltairDriver in any coordinate system.