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

Died on step 1

Messages
1,043
Country
us-northcarolina
Hello,

I emailed the author of this application since at the time I had problems registering on this forum but I received no response so I will turn to you all to maybe get an idea to fix my problem.

I installed SAMM that seems great however I would love to get it to work, which would be even greater :)

I am attaching a few snapshots that will show the issue better than explaining it. I was trying to create a library named 'Test'.
I am not sure of what file should go where but I noticed the library xml file was created in the Samm 1000 folder and nothing is to be found under 'Libraries' except an empty folder named 'Test'.

I can compile the Test.xml manually using bglComp, install it in 'G:\Flight Simulator 9\Addon Scenery\Test\Scenery' and the texture under 'G:\Flight Simulator 9\Addon Scenery\Test\Texture' but when I try using it with Abacus I get the texture path error message. Though I can place the gray plane (no texture) in FS.

Thanks in advance for your help,
Patrick (aka Frenchie)

async


async
 
Last edited:
As I don't run FS9, I cannot attempt to assist you with your issue.

However, until other FS9 users can assist you, if you read through the posts by other FS9 users here in the SAMM forum, you may very well find the information you need.

If you are using Instant Scenery 2, the latest version is supposed to have addressed some texture handling issues between SAMM and IS2, so make sure you have the latest version installed.

Hope this helps
Gman
 
Thanks Gman, I did that and found no post referring to my problem. As mentioned I am using Abacus EZ-Scenery. I'll wait for some good soul to point me into the right direction to fix the issue.

Patrick (aka Frenchie)
 
Patrick, as you know from our private e-mail correspondence, I've been away from my development system for a couple of weeks.

First of all, from the error message shown in your first screenehot, it would seem that the static model was not successfully created. (I appreciate that there appears to be such a static model) Did you receive any error messages when you created it?

As for the file test.xml, I don't know where it came from. If you created a library, all the associated files would be in the library folder in a sub-folder bearing a name you specified.

I'm going to need further detail if I'm going to be able to help you further. Specifically, I need to know - step-by-step - what you did and how the system, responded. As well, it may be helpful if you sent me the aircraft associated with the problem or a link to it. As well, just to help narrow things down, please try it again with the version field blank. (A version designator is only necessary if you wish to have several "poses" of an aircraft without duplicating textures.)

Don
 
Hi Don, I'm running the forum and the app in parallel so I'll comment step by step as I am following the tutorial.

System is running with Windows 7-64 bit
TEST #1:
- I set the shortcut to run in normal mode (not admin and no compatibility selected)
- Start app
- Select aircraft: G:\Flight Simulator 9\Aircraft\c172 (MS aircraft)
- Select title: Cessna Skyhawk 172SP
- Static model name: Cessna Skyhawk 172SP
- Version: left blank
- Animation included: Auto (by default)
- Other options: Create texture for each folder checked (by default)
- Click button 'Save .mdl file'
- Get msg saying files were created in the model folder
- At this point I am unsure what to do. I am studying the instructions but still not sure if I HAVE TO 'Save .bgl file' or if I can skip directly to 'Make library' since it'll be used later in an object placer? In other words will the bgl be generated if I skip save and click directly on Make Library?
Anyway, to be on the safe side for this test I will click on Save .bgl file.
- I fill in the information for the placement of the ojbect
- I click on Compile scenery object and select the output path in the popup window. The folder selected is 'G:\Flight Simulator 9\Addon Scenery\MyObjects'. It already has Scenery and Texture subfolders
-A window opens showing 'Unable to compile "Cessna Skyhawk 172SP". The system cannot find the file specified' (same I had in the screenshots)
- I close that window and go check the folders. Under Models it seems everything went fine as I see a texture folder(with bmp's in it) and 2 mdl and 1 xml (placement)
- I go check MyObjects folder and nothing has been created under there

For test purpose I will now attempt to create a library
- Same settings
- I click on the Make Library button
- I get a Selection popup window showing a single aircraft (Cessna Skyhawk 172SP
- I select it
- I type the Library Name: 'Skyhawk'
- I check Save library to an Add-on Scenery folder
- It unchecks itself (I always have to check it twice)
- I click on Save Library .bgl button
- In the popup I select the path 'G:\Flight Simulator 9\Addon Scenery\MyObjects'
- I click on 'Ok'
- A popup window appears saying: 'Unable to compile "Cessna Skyhawk 172SP". The system cannot find the file specified'
- I verify that nothing was created in the output folder I selected, it didn't
- I verify the SAMM folder. A 'Skyhawk' folder was created under Libraries but it is empty. And the file 'Skyhawk.xml' was created directly in the Samm1000 folder.
- End of test

TEST #2:
- I set the shortcut to run in Administrator mode (no compatibility selected)
- Same settings and selections
- Click Save .mdl file
- confirm to overwrite
- From that point on the test went the same way as TEST #1

TEST #3:
- I set the shortcut to run in Administrator mode and Windows XP Service pack 2 compatibility mode
- Same settings and selections
- From that point on the test went the same way as TEST #2


First of all, from the error message shown in your first screenehot, it would seem that the static model was not successfully created. (I appreciate that there appears to be such a static model) Did you receive any error messages when you created it?
I receive no error message at all except as you can see in the screenshot it says a file could not be found.

As for the file test.xml, I don't know where it came from. If you created a library, all the associated files would be in the library folder in a sub-folder bearing a name you specified.
As you can see in the tests I just conducted the library xml file is created under the root of Samm1000, this time it was 'Skyhawk.xml' and the 'Libraries' subfolder remains absolutely empty.

I'm going to need further detail if I'm going to be able to help you further. Specifically, I need to know - step-by-step - what you did and how the system, responded. As well, it may be helpful if you sent me the aircraft associated with the problem or a link to it. As well, just to help narrow things down, please try it again with the version field blank. (A version designator is only necessary if you wish to have several "poses" of an aircraft without duplicating textures.)
I am at your disposition to run any needed test and to provide all necessary files or screenshots. The aircraft used during the test is the Cessna Skyhawk 172SP found in the default aircrafts that came with FS9.

I hope the fix is simple, like a small step I missed maybe. Anyway, for now ball is on your side and I look forward to reading back from you.
 
Last edited:
Save .mdl saves the static model to the Models folder. Save .bgl placed single, previously-saved models. Make Library creates a library of previously-saved models that may be placed with other object placement programs. The latter two are totally independent of each other.

Create texture for each folder checked (by default)
Unless you are creating multiple versions of the model, this need not be checked (but shouldn't create any problems if it is.)

As you can see in the tests I just conducted the library xml file is created under the root of Samm1000, this time it was 'Skyhawk.xml' and the 'Libraries' subfolder remains absolutely empty.
That's strange. You said earlier you named the model "Cessna Skyhawk 172SP". All the associated files should be in a folder of that name and, except for the texture files, be named similarly.

I have just followed the procedure you outlined using the default C-172 without difficulty.

Since I don't have access to the compiler code, I can't determine at this point whether the compiler is "complaining" about the static model or the destination scenery folder. Since you are getting the same error message in both cases, my guess would be the static model file. Please repeat test 1 without checking any options and send me the xml file from the Models\Cessna Skyhawk 172SP folder.

Juist before sending this I reviewed once again your initial e-mail. I notice that the .mdl files and texture folder are in your Models folder, not a dedicated sub-folder in Models. This explains the error message (since SAMM will look for the files/folder in a dedicated sub-folder.) What I can't explain is why there is no dedicated subfolder. Please also do a search for a folder named "Cessna Skyhawk 172SP" and tell me all the places where you find it.

Don
 
Since I don't have access to the compiler code, I can't determine at this point whether the compiler is "complaining" about the static model or the destination scenery folder. Since you are getting the same error message in both cases, my guess would be the static model file. Please repeat test 1 without checking any options and send me the xml file from the Models\Cessna Skyhawk 172SP folder.
I don't know, I agree with you, my feeling is that it is complaining about the static model file. I will test again but first I am going to uninstall Samm and reinstall it since I recall having a bit of a hard time installing the update so maybe something went wrong at that point.

BINGO You pointed me in the right direction by mentioning the word 'compiler'. I remember the first time I installed the update from SAMM1008.zip I had the UAC complaining. This time again it did. Dragging the files from the open zip to the Samm folder copied some files but for some unknown reason the system refused to copy the compiler itself :confused: thus I was missing the file bglcomp.exe in the Samm folder. Once I copied all files one at a time (with no UAC complaint, go figure) everything fell in place and your program worked like a charm.

Don, I really appreciate your kindness in helping me figuring out the issue I had with Samm. It was not Samm's fault (:eek: eyes turning to Microsoft now) and I am very excited about the opportunity to use this program .

Questions remain:
  • Why is Samm creating the files Cessna Skyhawk 172SP.BGL and Cessna Skyhawk 172SP.xml in the root folder when creating a library? Don't they belong to G:\Samm 1000\Libraries\Cessna Skyhawk 172SP? Does the same happen on your system and what O.S. are you using?

  • When I created the bgl using your placement tool it worked fine yet the aircraft doesn't show in F.S. But I do not personally care about it since I will be using Abacus as a placement tool.

  • When using Abacus I am getting error messages regarding the texture path. F.S. is looking for the texture of the plane I am flying (c172) in the aircraft\plane\texture folder but with the static model name "Cessna Skyhawk 172SP" so actually aircraft\Cessna Skyhawk 172SP\texture which of course it can't find. This doesn't occur if I am flying an aircraft other than the static model. Next F.S. looks in the F.S.\texture path and doesn't find the texture either. I remember reading a post about this issue so I'll be looking for it again.

  • - A static model placed with Abacus does show in F.S. however with no texture applied to it. Here again I remember reading about that so I will doing some research.

  • - A thought now rather than an issue. The texture files are found in 4 different places, i.e. for C172:
    G:\Flight Simulator 9\Aircraft\c172\Texture
    G:\Samm 1000\Models\Cessna Skyhawk 172SP\texture\Cessna Skyhawk 172SP
    G:\Samm 1000\Libraries\Cessna Skyhawk 172SP\texture\Cessna Skyhawk 172SP
    G:\Flight Simulator 9\Addon Scenery\MyObjects\texture\Cessna Skyhawk 172SP
    Isn't there a way to get rid of some of those? I suppose it is safe to delete those from the Samm folders once the model has been created?

Again Don, I thank you very much for the time you are spending helping me.
 
Last edited:
Why is Samm creating the files Cessna Skyhawk 172SP.BGL and Cessna Skyhawk 172SP.xml in the root folder when creating a library? Don't they belong to G:\Samm 1000\Libraries\Cessna Skyhawk 172SP? Does the same happen on your system and what O.S. are you using?
I don't know. Perhaps it's got something to do with the faulty initial installation. Given the successful compile and your final question, I presume the files are now being saved in the correct location.

When I created the bgl using your placement tool it worked fine yet the aircraft doesn't show in F.S. But I do not personally care about it since I will be using Abacus as a placement tool.

When using Abacus I am getting error messages regarding the texture path. F.S. is looking for the texture of the plane I am flying (c172) in the aircraft\plane\texture folder but with the static model name "Cessna Skyhawk 172SP" so actually aircraft\Cessna Skyhawk 172SP\texture which of course it can't find. This doesn't occur if I am flying an aircraft other than the static model. Next F.S. looks in the F.S.\texture path and doesn't find the texture either. I remember reading a post about this issue so I'll be looking for it again.

- A static model placed with Abacus does show in F.S. however with no texture applied to it. Here again I remember reading about that so I will doing some research
If, by "Abacus", you mean Instant Scenery 2, these are known problems fixed in part with a recently released update. There's lots of discussion about these problems in the forum. If it's not IS2, then you should ask the author of the placement tool.

- A thought now rather than an issue. The texture files are found in 4 different places, i.e. for C172:
G:\Flight Simulator 9\Aircraft\c172\Texture
G:\Samm 1000\Models\Cessna Skyhawk 172SP\texture\Cessna Skyhawk 172SP
G:\Samm 1000\Libraries\Cessna Skyhawk 172SP\texture\Cessna Skyhawk 172SP
G:\Flight Simulator 9\Addon Scenery\MyObjects\texture\Cessna Skyhawk 172SP
Isn't there a way to get rid of some of those? I suppose it is safe to delete those from the Samm folders once the model has been created?
The first will be required if you ever want to use the stock C172 as a flyable or AI aircraft. The last is the textrure for the static aircraft. If you are finished placing this model, you can delete the others; you can always recreate them if neeeded.

Don
 
I don't know. Perhaps it's got something to do with the faulty initial installation. Given the successful compile and your final question, I presume the files are now being saved in the correct location.
Yes indeed the model goes to Models and the library goes to Libraries however I still get a copy of the library xml and bgl files in the root directory.

If, by "Abacus", you mean Instant Scenery 2, these are known problems fixed in part with a recently released update. There's lots of discussion about these problems in the forum. If it's not IS2, then you should ask the author of the placement tool.
It's Abacus EZ scenery, I believe it's a different placement tool. I just spent hours reading those posts and testing many different solutions. I do not believe the issue comes from the placement tool, nor do I believe your program is doing something wrong. I think at the end I figured out a way to fix several problems mayyyybe :) I will expose my thought in a new thread.

The first will be required if you ever want to use the stock C172 as a flyable or AI aircraft. The last is the textrure for the static aircraft. If you are finished placing this model, you can delete the others; you can always recreate them if neeeded.
Glad you confirm my thought.

I believe we can close this thread and I thank you very much for all your inputs.
 
Last edited:
however I still get a copy of the library xml and bgl files in the root directory
That's a temporary copy made necessary by the way the compiler works. It can be deleted (and I'll probably do that in the next version.)

It's Abacus EZ scenery, I believe it's a different placement tool. I just spent hours reading those posts and testing many different solutions. I do not believe the issue comes from the placement tool, nor do I believe your program is doing something wrong. I think at the end I figured out a way to fix several problems mayyyybe I will expose my thought in a new thread.
Many placement tools don't "know" how to handle texture files in a subfolder of a scenery \texture folder. (This is not a capability that is normally used by scenery developers but is legitimate in FS.) IS 2 didn't until a few weeks ago and, apparently, neither does EZ Scenery. A test version of SAMM i released before going away allows you to place the textures in the main texture folder (see this thread) and, thus, to avoid this shortcoming in those placement tools.

I plan to re-release the test version as SAMM 1.0.09 shortly.

Don
 
In an ideal world all developers would get together and develop standards but that's a nice dream and an impossibility so we have to deal with what we have and try to accomodate.
 
Back
Top