Hi Ben,
Sorry it's been a couple of days, but I have been putting it through MCX and thinking that I'd forgotten most of what I once knew.
I triple checked every part and texture, every textured poly, and did various deletions trying to see what caused the error.
I have eliminated everything I can think of, and can now say with confidence that:
...I can see the 3D view of the .fsc in full colour in MCX. A couple of bits are at weird angles, but I think this can be fixed by centering the axis to the compound parts, then resetting the axis.
Then I ask MCX to send off a bgl to FSX. It does something, but when I look in FSX, it's sent an mdl of 0Kb, not a bgl in sight.
That's where I'm at.
I think that Abacus are not replying because it's an _xtomdl error.
I put the facts up on FS Developer forum to see if anyone there has an idea.
As I mentioned there, I had once used a non-square image for texturing, and I got an animation error when no animation was present.
Maybe the MS error report is like their messages that "The device is working properly" when quite obviously, it's ^*#@ not, and that is why I'm asking Windows to check it.
![Rany :rant:](./images/smilies/076.gif)