The .x file format is very old legacy, and Microsoft no longer supports it. Why do you need it now?

>>The .x file format is very old legacy, and Microsoft no longer supports it. Why do you need it now?


well considering you have a exporter for it, why not the importer so that anyone can reimport these files to do modifications on older models or new models created with it!

If you output to a non-mqo/mqoz file and then load it again, it will not be in the same state as the original. A reload workflow is not appropriate, and the original mqo/mqoz files should remain.

In any case, the x file format is too old and should no longer be handled in the modern era. However, if you must read x files, please use an external file converter. I don't know the details, but there are several free conversion online services.

>If you output to a non-mqo/mqoz file and then load it again, it will not be in the same state as the original. A reload workflow is not appropriate, and the original mqo/mqoz files should remain.
>
>In any case, the x file format is too old and should no longer be handled in the modern era. However, if you must read x files, please use an external file converter. I don't know the details, but there are several free conversion online services.



If that is true then what was the point of creating any other importer for metsaquioa?

>If that is true then what was the point of creating any other importer for metsaquioa?

I don't understand your question. What kind of answer do you expect?

>>If that is true then what was the point of creating any other importer for metsaquioa?
>
>I don't understand your question. What kind of answer do you expect?

the .x format maybe old but its still supported by some people in the industry.

>the .x format maybe old but its still supported by some people in the industry.

I don't know what industry you're in, but I believe it is risky in every respect to continue to use an industrial system that relies on old technology and does not support modern formats.
However, if you must do so, as already mentioned, an external converter can solve the problem right now. Have you considered that option?

>>>the .x format maybe old but its still supported by some people in the industry.
>>
>>I don't know what industry you're in, but I believe it is risky in every respect to continue to use an industrial system that relies on old technology and does not support modern formats.
>>However, if you must do so, as already mentioned, an external converter can solve the problem right now. Have you considered that option?


No matter , I found a number of free solutions that don’t involve online conversions! It’s a shame there is no .x importer for your software. Life find a way!