• 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.

Interface with SAMM

G

gadgets

Resource contributor
Messages
9,388
Country
ca-britishcolumbia
Arno, it's becoming clear from the early experience with SAMM that FS9 static aircraft models in FSX "just don't cut it". While transparency and lighting don't seem to be a problem, the issue of FSX not texturing FS9 models at a distance is likely to be a major annoyance.

What can I do in SAMM, or is there anything you easily do in MCX, that would make the process of MCX making SAMM's FS9 output FSX-compatible more streamlined - especially for novice users?

Don
 
Hi Don,

In the texture list in the model do you use the type TEXTURE_AIRCRAFT or TEXTURE_BUILDING? I think it might be a problem of the type TEXTURE_AIRCRAFT that they do not show in a distance.

Else I think I could add some command line options to do a quick conversion with ModelConverterX. So then you could call the conversion from FS2004 to FSX directly from SAMM.
 
Thanks, Arno. You may have "put you finger on it". At one point, I did substitute TEXTURE_BUILDING for TEXTURE_AIRCRAFT, but it seems to have disappeared from the model generation code. It's still in the listing code, however, which is why I hadn't recognized the issue before. Come to think of it, I did notice some transparency in a model someone sent me a few days ago - that would be a possible result of using TEXTURE_AIRCRAFT.

I'll fix it and let you know if there's still a probem in this regard.

Else I think I could add some command line options to do a quick conversion with ModelConverterX. So then you could call the conversion from FS2004 to FSX directly from SAMM.
Click to expand...
That would be great. It would save users from having to fiddle with two utilities.

Thanks again,
Don
 
Arno, just to let you know, I re-instated the code that changes TEXTURE_AIRCRAFT to TEXTURE_BUILDING. Static model now retain their textures all the way out until they disappear.

Thanks for that little "boost".

DOn
 
Hi Don,

Glad to hear hear that works.

I'll keep the command line options on my todo list though.
 
You must log in or register to reply here.
Back
Top