Hello all,

 

HyperView proposes a default reader for unv, whose support is described in the online help below:

https://help.altair.com/hwdesktop/hwx/topics/pre_processing/interfacing/hv_interfacing_unv_files_r.htm?zoom_highlight=unv+hyperview

 

That said, this article is intended to collect and document some limitations that were encountered by some users, and the work-arounds that were identified.

 

If you face any unexpected behavior with the unv reader, please comment this article or submit a support request with the reference to this knowledge base article.

 

 

About results in local system

Some users reported that the vector/tensor results expressed in elemental system were incorrect. To get the expected results, please:

- convert the UNV model file (including the information about the local displacement coordinate system of the nodes is located) to a supported fem format (Nastran, OptiStruct, ...)

- load in HyperView the converted model as Model file and the unv result file as Result File