Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Some learning questions about Motionview

q1:How to batch import points created in Hypermesh into Motionview? I know there was a tool called MD_Tools before, but it doesn't seem to work for me. I'm using the 2025 version

q2:How to output points from an MDL and then import them into another MDL file？

q3:Does the bearing in the mechanical tool expansion package not work in XML format solution?

q4:does the PY file solver have more constraints? I recently encountered a problem where I can solve in XML format and then use Py files to solve. However, for the same file, PY will report an error and display a conflict in the ID of a certain ENTITY

q5:How to output a subsystem in Motionview and then import the generated subsystem into another MDL file?

Find more posts tagged with

MotionView/MotionSolve

Accepted answers

GTT Adam

Hi @Jin1,

Q1: The batch import of points can either be taken care of using the Data Summary Tool or by clever export/import tactics.

The Data Summary Tool allows for the import of a Excel-style spreadsheet which can assign locations to existing points (Green, below).
From HyperMesh, you can export the geometry as a parasolid, and then use the snap points from the parasolid after it has been imported to MotionView to locate your points.
Additionally, you can enable the Panels (View » Panels) and use the Points (Parametric) Tool to import a CSV file of point locations (Blue, below).

Q2: You can copy all the points you want to export, paste them into a new system, export the system as a MDL Definition, then import the MDL Definition into your new MDL. Alternatively, you can store them as a System Entity (Right click on system) and that system will then be available in your Entity Browser for quick import into any MDL going forward.

Q3: The Machinery Tools Extension must be used with the Python Solver

Q4: That is not something that I have ever seen. Please create a Support Ticket and attach the model which is causing this issue for more in-depth help.

Q5: See Q2.

Hope this helps!

Adam Reid

All comments