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

making multiplane library

robystar

robystar

Messages
5,214
Hi,

Unless I do something wrong (which is quite possible) I have the following minor comment/suggestion:
When making a library for more than one plane (call it static aircraft lib) and include several aircraft in the bgl, I end up with names like static_aircraft.bgl001, static_aircraft.bgl002 etc. instead of the names of the planes when opening and adding them to the ADE LOM for placement in an airport scenery.
Of course I could afterwards change the name or go through Library Creator XML but it would be nice to be able to eliminate the extra step(s) if SAMM would only give the right name from the start but perhaps it is a peculiarity of the ADE LOM or my own stupidity?
 
Roby, I don't understand. A library operation creates a single bgl file named as you direct.

SAMM does not create files with the suffix .bgl001, .bgl002, etc . for any operation.

Don
 
Hi Don,

Guess I explained badly.
What I meant to say is that the program lacks the ability to include more than one mdl in a bgl.
When you are presented the choice of making a library with more than one model in the list and you check all of them, not one collective bgl is created including all the models but one bgl per aircraft. As I have named the library static_aircraft, you will have several bgl's with the name static-aircraft. Hence bgl001, bgl002 etc.
 
Last edited:
robystar said:
Hi Don,

Guess I explained badly.
What I meant to say is that the program lacks the ability to include more than one mdl in a bgl.
When you are presented the choice of making a library with more than one model in the list and you check all of them, not one collective bgl is created including all the models but one bgl per aircraft. As I have named the library static_aircraft, you will have several bgl's with the name static-aircraft. Hence bgl001, bgl002 etc.
Click to expand...


Hi Roby,

I just created a five aircraft library and it has one .bgl in the library\scenery folder with five aircraft on it.
Are you saying that the scenery folder SAMM created for your library has more than one .bgl?

Or are you saying that A.D.E. is listing them as numbered variants of your library.bgl?

In other words your library is named static_aircraft, does it result in a single static_aircraft.bgl in the library scenery folder which A.D.E. is listing by the library name plus the numbered suffix for each aircraft, hence static_aircraft.bgl001, static_aircraft.bgl002, etc?

Please confirm the contents of your static_aircraft\scenery folder.

Cheers
Gary
 
Gman said:
Or are you saying that A.D.E. is listing them as numbered variants of your library.bgl?
Click to expand...
This is what IS is doing. When SAMM creates a library it does not create the accompanying text file that IS uses to display the names of the models in its list, so IS shows...

[name of bgl]#1
[name of bgl]#2
[name of bgl]#3

etc.
 
It's on my list. Can you send me the format of the text file IS is looking for. (There are several such file formats used for a similar purpose.)

Don
 
Hello Don, Gary

Re:In other words your library is named static_aircraft, does it result in a single static_aircraft.bgl in the library scenery folder which A.D.E. is listing by the library name plus the numbered suffix for each aircraft, hence static_aircraft.bgl001, static_aircraft.bgl002, etc?
Correct.
Re: Please confirm the contents of your static_aircraft\scenery folder.
Sorry, I deleted them. I had 8 aircraft in it but lost track of what was what as, after adding the library to the LOM and opening it, they were numbered static_aircraft.bgl001, static_aircraft_bgl002, etc.
That is exactly the reason why I posed this question.
Easy enough to check (as if you did not have enough work already):
open SAMM, click on make library and a list of mdl's will show up. Select them all and give them the library name 'static_aircraft' and you will see what I mean in a jiffy. For your info, I use the ADE LOM as most of the times the static aircraft is airport scenery.
 
Last edited:
Here you go, Don. GUID in FS2004 format followed by mdl name.

Library description file for: iqaluit_objects.bgl
Automatically created by EZ-Scenery Manager

# Format for description files:
# GUID name
# GUID must consist of 32 hex digits. The format is identical to the one used in
# BGLCOMP (FS2004 SDK)

2347328ED3EA44FEA9DEB5FE11F29C44 iqaluit_first_air
2347328ED3EA44FEA9DEB5FE11F29C45 iqaluit_terminal
2347328ED3EA44FEA9DEB5FE11F29C46 iqaluit_fbo
2347328ED3EA44FEA9DEB5FE11F29C47 main_ramp_1
2347328ED3EA44FEA9DEB5FE11F29C48 main_ramp_2
2347328ED3EA44FEA9DEB5FE11F29C49 main_ramp_3
2347328ED3EA44FEA9DEB5FE11F29C4A main_ramp_4
2347328ED3EA44FEA9DEB5FE11F29C4B main_ramp_markings
2347328ED3EA44FEA9DEB5FE11F29C4C main_ramp_markings_2
2347328ED3EA44FEA9DEB5FE11F29C4D iqaluit_terminal_posts
2347328ED3EA44FEA9DEB5FE11F29C4E iqaluit_terminal_shelter
2347328ED3EA44FEA9DEB5FE11F29C4F flag_canada
2347328ED3EA44FEA9DEB5FE11F29C50 flag_nunavut
2347328ED3EA44FEA9DEB5FE11F29C51 iqaluit_terminal_extension
2347328ED3EA44FEA9DEB5FE11F29C52 iqaluit_kb-ch
2347328ED3EA44FEA9DEB5FE11F29C53 quonset
2347328ED3EA44FEA9DEB5FE11F29C54 rcmp_sign
2347328ED3EA44FEA9DEB5FE11F29C55 air_nunavut_sign
2347328ED3EA44FEA9DEB5FE11F29C56 Arrestor_cables
2347328ED3EA44FEA9DEB5FE11F29C57 runway_markings
 
Thanks. Looks doable. I'm away for a week starting this coming Thursday. Don't know If I'll get it done before then, but I'll try.

DOn
 
ONE .bgl , made FIVE different static objects with SAMM 1003 .Placed with IS . Great tool Don . Thanks .

Only problem in Select aircraft folder C:\ is not expanded and not all folders are present . Had to get them in external drive F:\ to select .
 
Last edited:
Thnaks, george.

Re the failure to open certain folders, SAMM checks whether each folder is, or contains, an aircraft folder (i.e., one that contains a file named aircraft.cfg) and doesn't bother to open any that aren't/don't.

Is this possibly the situation you saw?

Don
 
Geobas said:
Only problem in Select aircraft folder C:\ is not expanded and not all folders are present . Had to get them in external drive F:\ to select .
Click to expand...

Hi George,

I'm not understanding your issue.
For starters, which directory did you select at the top of the SAMM user interface?
*FS9
*FSX
*Other

If you selected Other, SAMM won't open either of the Flight Simulator directories automatically.

If you selected FS9 or FSX, SAMM may not be automatically opening it if you have it installed in a non-default location. (MSFS?)

However, you should have been able to expand any of the directories listed in the Select Aircraft Folder list by clicking on them, are you unable to do so?


Cheers
Gary
 
Don and Gary

FSX selected
Trouble was that l did not run SAMM as administrator . Everything is fine .
Thanks
 
l use Instant Scenery for placement of static objects .
with SAMM
Is there a way to have a distinguishable model name for each object ?
 
Last edited:
You must log in or register to reply here.
Back
Top