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

FSX Texture Errors in SAMM2

I am new to SAMM but not new to Airport Design. This is my first use of SAMM to add static aircraft to my ADE stuff. The Utility looks and feels excellent. but I have a significant problem when placing a static aircraft in ADE. Having followed the manual precisely I have found that I get Error messages when FSX tries to present the airport in "Free Flight" mode. FSX appears to be looking for texture files that are not there, although they have been upload to addon scenery and activated. On screen the model is shown black but in the correct location. I do not know what is happening. I use several third party static models in ADE and this has never happen before. Can anybody help.
 

gadgets

Resource contributor
The "black" models and error messages suggests the textures have not been placed where Flightsim expects to find them. Did you copy the textures yourself or did you let SAMM do it for you. The textures should be in appropriately-named (i.e., named for the static aircraft to which the textures apply) sub-folders in the add-on texture folder, not in the add-on texture folder itself.

Don
 
SAMM2 placed the textures into the AddOn Scenery folder of my choice. So the folder has the "scenery" and the "texture" files and has been activated within FSX
 
Sorry Don I should have said. The model I am trying out on is the default FSX boeing 737-800 with a default livery. I am doing this only to get used to your software. I also found that I can only run SAMM2 as "Administrator" is this normal for Windows 10?
 

gadgets

Resource contributor
I can only run SAMM2 as "Administrator" is this normal for Windows 10?
If you mean that you must select "Run as Administrator", then that's because Win 10 UAC won't allow SAMM to access the files where you have stored them.

SAMM2 placed the textures into the AddOn Scenery folder of my choice. So the folder has the "scenery" and the "texture" files and has been activated within FSX
Without being at your console, I really can't be more specific than saying the problem is due to the textures not being where Flightsim expects to find them. If you open the .bgl containing the static aircraft with a hex editor (e.g. HxD, freeware), you will be able to see the relative path to the textures.

SAMM2 placed the textures into the AddOn Scenery folder of my choice.
No sure what this means. There is no independent "texture-copy" function in SAMM. If you mean you created the library with "Save textures to the main texture folder" checked, try it again without that checked. That's a special purpose control.

Are you using the latest version of SAMM?

The stock 737 converts and displays without such issues on my system.

Don
 
I used the save "textures to the main texture folder" option. I am using the version of SAMM i downloaded yesterday. I will try your suggestion and let you know.
I really appreciate your help.
Mike
 
OK Don, all is well I placed the model without checking "save textures to main folder" and it worked. Thanks for your help and for your great utility.
Mike
 

gadgets

Resource contributor
Mike, there was in fact an issue with "Save textures to the main texture folder". It was a subtle one and, apparently, escaped detection until you tried it.

I have just posted Development Release 2.2.08(a) at http://stuff4fs.com. Depending on the setting of "No Automatic Updates" in your SAMM.ini, the update should automatically be detected the next time you run SAMM. If not, go to the website, navigate to the SAMM page and click the Development Release menu item.

Don
 
Top