Objects created in other software cannot be read well in Metasequoia or objects created in Metasequoia cannot be read in other software.
The used function is not supported
Confirm the applicable function for Import file or Export file.
Keep in mind that some data are lost in most cases when forms excluding MQO are used.
The problem of software version
As file forms are somewhat different in each software version, objects cannot sometimes be loaded well. Please try these things: do not use the new or old version or use the different file form. But notice that any measure sometimes cannot solve the problem.
The front and back of faces become irregular when objects created in other software are read.
The direction of faces is not defined in the file.
As some software or file formats regard faces as double-faced without the front and back, they export files in irregular direction. In that case, correct the front and back of faces with
Especially, it often becomes irregular when you load DXF or ROK.
The texturing are lost when I load in other software.
The used image format is not supported
If the image format (such as BMP, JPG) used by the texture is not supported the other software, the file will be ignored and a texture will be not shown when importing the software.
Please confirm which image format is supported in the other software before importing files.
Export in the form without UV mapping information
Some file forms cannot have UV mapping information. Use other forms in this case. See Export file to check availability of UV mapping with each form.
Form inapplicable to texture
Some file forms like DXF are not applicable to texture. Use other forms.
The number of vertices increases or directions of faces becomes irregular when the exported file is read in other software.
Because of normal of UV mapping method
In some forms, the number of vertices increases or faces become irregular when you export with a check in [UV mapping]. Do not check [UV mapping] if it is not necessary.
Objects become very large or small when exporting or importing
The unit of the length is different
When you export data from Metasequoia and import it in the other software, objects may be scaled large or small. This caused by the difference of the standard scaling.
You can convert the proper length with specifying [Scaling] factor at the time of exporting or importing. Please confirm how scaling is proper for the scaling.
I want to know the MQO/MQOZ file format
It is open to the public on the web site.
See the latest file format specification on the web site. And a plug-in SDK contains source code for reading MQO/MQOZ file.