FSX .DAE file import problem last 2 MCX releases

[Dave_W]

This image is from the 4/9 release showing the object imported correctly on the Y-axis:

This image shows what happens in both the 4/18 and 4/21 versions. The object is mirror imaged on the negative side of the axis:

 

[arno]

Hi Dave,

I have updated to a newer version of the Assimp library that reads the COLLADA files. I didn't notice such issues with my COLLADA test objects, but I'll check again.

 

[Dave_W]

Thanks Arno,

FWIW, this object was made in SU 2017, then textured in Blender 2.82a and exported from it as a .DAE file.

Edit: never mind the Blender info, the same thing happens with the .dae straight from SU.

 

[DirectDani]

you should use blender 2.79b, very stable

 

[arno]

Hi,

I have restored the up axis to how it was before, so in the next development release you should get the orientation as it should be.

 

[Dave_W]

Thanks for your time Arno,

But, I don't see any difference with the 4/26 release.

Here are two more images that should show the problem more clearly:

4/9 release:

4/26 release:

Here is the SU 8 .dae file:

 

[Pyscen]

What I see is the X is the red line, Y is the green line, and the Z is the blue line in both images.

The difference is, the top image is labeled on the positive side of the line, except the Z. The Z in the first image and 2nd image is on the positive side of the line in both.

In the 2nd image, the X and Y are both labeled on the negative side of the line.

So, I'm misunderstanding how a model can be wrong in exporting.

 

[arno]

Hi,

This is how it looks on my machine:

But I said it would be fixed in the next development release and that one is not yet online. I will push it this morning.

 

[Dave_W]

Thanks Arno!

I thought that when you said the next release, that it was the one I downloaded yesterday.