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

SAMM is unable to find aircraft folder

you asked that I open SAMM.ini and check for a line that reads "Path to FSX.cfg= path on your system". I did check and the FSX.cfg file is located where the path says it should be located; i.e., C:\Users\KRNMR\AppData\Roaming\Microsoft\FSX\
 

gadgets

Resource contributor
Yes I did. But I didn't expect you to respond with proof. I was surprised, that's all

So, it would seem the inability to locate aircraft folders is now behind us. The short directory tree is still a mystery and without further information uis likely to remain so.
 
Sorry, got carried away and thought sending you a pic would be helpful, SAMM is now able to access the Simobjects folder, there is one caveat however and that is that I need to run it as administrator, the old double click just gives me a truncated file tree and no path to the Simobjects folder
 
The last Release of SAMM don't find my Flight Simulator 2004 (FS9) folder (c:\program files (86)\microsoft games\flight simulator 9

So, SAMM don't find any aircraft...
 

gadgets

Resource contributor
SAMM examines the system registry to determine which versions of Flightsim are installed. If SAMM doesn't find FS9 then FS9 has not been install in the usual manner.

You can tell SAMM where is FS9 by adding the following line to SAMMJ.ini
"Path to FS9=" fully-qualified path to the folder containing FS9.exe .

SAMM must not be running when you do this.

If SAMM.ini does not exist, then create a text file containing that single line, save it as SAMM.ini and start SAMM again.
 
SAMM examines the system registry to determine which versions of Flightsim are installed. If SAMM doesn't find FS9 then FS9 has not been install in the usual manner.

You can tell SAMM where is FS9 by adding the following line to SAMMJ.ini
"Path to FS9=" fully-qualified path to the folder containing FS9.exe .

SAMM must not be running when you do this.

If SAMM.ini does not exist, then create a text file containing that single line, save it as SAMM.ini and start SAMM again.
Other soft like AIFP find my FS9.

My FS9 is installed in the usual manner : "c:\Program Files (86)\Microsoft Games\Flight Simulator 9" (defaut installation)

My fs9.cfg is also in the correct place (defaut installation).

I don't have this problem with old SAMM version (But I dont have them anymore)
 

gadgets

Resource contributor
If AIFP can find your FS9, so can SAMM. They both use identical software for that purpose.

SAMM don't find my Flight Simulator 2004 (FS9) folder (c:\program files (86)\microsoft games\flight simulator 9
What makes you believe SAMM hasn't found FS9? Are you getting same message that tells you?

I note that FS9 is installed on your C: drive. If SAMM is on some other drive, you may have to run as administrator to access programs on the C: Drive.
 

gadgets

Resource contributor
So presumably there was an error message that you didn't tell me about initially. When you report issues, its always best to include as much relevant information as is available.
 
Top