• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

XtoMDL acting up

R

Robertium

Messages
73
Country
mexico
Hi everyone. You may have seen my previous posts wherein I had a lot of trouble getting MCX to work properly and linking exporters and etc. Well, I seem to have solved most of those problems UNTIL NOW. I was able to export some more models out of MCX and use them in the game, but unfortunately today I tried exporting something and XtoMDL gave me a bunch of errors.

2018-05-14.png
Of course, without XtoMDL's work nothing else can happen properly. Is this a problem with XtoMDL itself? If so, how can I fix it, or where can I redownload it?
 
tgibson

tgibson

Resource contributor
Messages
11,338
Country
us-california
With everything in a Program Files folder, you may be having permission problems?
 
=rk=

=rk=

Resource contributor
Messages
4,477
Country
us-washington
It's pretty difficult for XtoMdl to be broken. To me it looks like your string buffer length is too big, which probably means your model file name is too long. It doesn't look too bad but I'd try shortening it. "String buffer" loosely means a changeable field of characters, so if it's not the model name, then it is likely some other identifying field of characters, like the GUID, that is too big.
 
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
The name doesn't look that long, so it could also be the model us too complex. How many polygons does it have?
 
R

Robertium

Messages
73
Country
mexico
2018-05-15.png
Yeah..... I imagine this one is far too complex. I downloaded this one DIRECTLY off Sketchup 3d Warehouse and exported to DAE without any editing. I'm going to see if I can reduce the amount of polygons by sharpening/removing some sides,,,,
 
=rk=

=rk=

Resource contributor
Messages
4,477
Country
us-washington
The model is not at all too complex, you can easily compile 5x that number of poly's, even 10. Please, click the "Set new GUID" button and try again. How did you get a number field like that anyway? Pretty certain that is the current problem. You will probably want to consolidate all the many small textures into one, or a few..
 
R

Robertium

Messages
73
Country
mexico
I'm not sure if it's the GUID. I tried exporting a very simple model (32 tris and one texture) and it exported fine (with the same GUID). I'm probably going to have to make this model simpler,
2018-05-17.png

2018-05-17 (1).png
 
arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,883
Country
netherlands
No, 600 polygons is not complex at all.

I see you use an old version of MCX, maybe try the latest development release first.
 
You must log in or register to reply here.
Top