It's about the file format covered by Magics. 

Magics' data conversion is performed by a separate module called MatConvert.  

Solid data or mesh data (hereinafter referred to as "3D data") is retrieved. 

It is converted through MatConvert to hand over STL data consisting of facet data to Magics.

When a user calls solid or polygonal data directly from Magics, the appearance of a shape consisting of facet data eventually occurs.

It can be seen that it is converted into an STL format containing only information and loaded into Magics. If you bring up STL data right away,

Converting is not done and it is called right away.

Name

* It can be seen that MatConvert is separately installed when Magics is installed. 

* File formats that can be imported directly from Magics.

* This is modeling data that was worked on UG-NX with sample data and appeared in the Inventor World Cup.

* MatConvert execution window 

Magics can immediately retrieve various CAD file format specifications as described above.

STL is loaded without going through Convert, but other files are exported by MatConvert.

The above window is the MatConvert execution window that appears only when data other than STL data is retrieved. 

Here, you can check what you are going to do while converting the file to STL, which is facet data, and retrieve it right away.  

Simple fixing is also possible.

* If you send it from UG-NX to STL and load it directly from Magics,

As you can see from the comparison above and below, STL basically does not have color information.

When converting from Magics, color information was taken and the color information was applied to STL's facet data.

And if cad data is retrieved immediately, there is a high probability that a triangle intersecting an overlapping triangle will occur.

It's not a big variable in 3D printing, but it can cause errors during slicing.

Fixing is recommended to be perfect because it can affect the shape itself.