Adding Airports to Scenery Library.

[wbunnell]

Adding, The Airport folder, for each set of static aircraft you make, to Scenery Library, is a lot of adding.
Is there a Simpler way to do this?

 

[gadgets]

What is "the Airport folder"? Perhaps you could be a little more specific as to what you want to do.

Don

 

[wbunnell]

What is "the Airport folder"? Perhaps you could be a little more specific as to what you want to do.
Don

Each Airport that you make creates a folder.Each Airport that you make, creates a folder for that airport, in the "STATIC AIRCRAFT LIBRARY"
Unless you Static Aircraft Maker is different from mine!

 

[gadgets]

Bill, are you sure it's SAMM you are referring to. SAMM "knows" nothing about airports - at least my version doesn't.

Don

 

[hcornea]

Don, I'm guessing he is referring to the library bgl files that SAMM makes being each in a separate folder.

Can they not just be placed into a single folder, and that scenery folder activated in FSX?

 

[gadgets]

Don, I'm guessing he is referring to the library bgl files that SAMM makes being each in a separate folder.

Can they not just be placed into a single folder, and that scenery folder activated in FSX?

The library creation tool allows the user to specify both the aircraft to be included in a given library and where that library is to be saved. What more is it (in detail) you think SAMM should be doing?

Don

 

[hcornea]

Well I guess you (as the user) could just tell it to put the models in the one folder.

That would seem to solve the problem.

 

[Gman]

I tried to help Bill get this sorted in his earlier thread, and this seems to be a continuation of the confusion between SAMM static aircraft library .bgl's and the Instant Scenery 2 scenery .bgl's Bill is saving for each location.

SAMM and Instant Scenery 2 are two separate programs, one creates static aircraft library .bgl's, the other places the items from the various library .bgl's into location specific IS2 scenery .bgl's. The .bgls created by SAMM and IS2 have nothing in common other than they both get placed somewhere in a sub-folder called "scenery". The screenshot may have been more useful if it showed what is inside the airport folders, but it is really not relevant.

In answer to Bill's question of whether there is an easier way, yes, make a single folder called Instant Scenery airports, log it into the Flight Simulator Scenery Library, and place all of the Instant Scenery 2 airport scenery .bgl's into the scenery sub-folder of that folder. If the IS2 bgl's are named for the airports, they need not be placed in separate named folders. When you go to save an item in IS2, you have the option to select which .bgl to save it to, if all of your airport .bgl's are saved in the same folder, they will all be listed together for you to select from.

Hope this helps.

 

[n4gix]

The real "key" is to simply pay attention to what you are saving, and where.

Don't just push the Save button and expect it to magically teleport itself to where it's supposed to go...

 

[hcornea]

The real "key" is to simply pay attention to what you are saving, and where.

Don't just push the Save button and expect it to magically teleport itself to where it's supposed to go...

What?


Actually the same is true of operating systems in General.

My wife (a Mac user) relies on Spotlight to find everything she saves randomly on the computer.

 

[scruffyduck]

Happens to me all the time Save something to a folder - I am sure I know which one. Go and check and it is not there - how did that happen

 

[gadgets]

wbunnel, yesterday you posted

Quote:
Originally Posted by gadgets
What is "the Airport folder"? Perhaps you could be a little more specific as to what you want to do.
Don

Each Airport that you make creates a folder.Each Airport that you make, creates a folder for that airport, in the "STATIC AIRCRAFT LIBRARY"
Unless you Static Aircraft Maker is different from mine!

to which I replied

Bill, are you sure it's SAMM you are referring to. SAMM "knows" nothing about airports - at least my version doesn't.

Don

You haven't responded since, but you do seem to have struck a nerve or two elsewhere.

I hadn't noticed the attachment to your second post. SAMM doesn't create airports. I don't see how SAMM could have created the folder "STATIC AIRCRAFT LIBRARY" or any of the folders shown in it.

Perhaps - as someone suggested - those folders contain SAMM-generated library files. If so, as I noted in another post in this forum yesterday, SAMM allows you to place as few or as many static aircraft in a library as you wish and to organize those libraries as you wish. (But, it does seem unusual that you would create a library for each airport - unless each airport is to be unique in its static aircraft complement - and even then separate libraries are not necessary.)

Or, perhaps, they contain the scenery .bgl files generated by IS 2 (or whatever other placement software you are using). In that case, SAMM is not involved.

Bottom line, SAMM currently contains all the flexibility I think you need to save files in whatever configuration you want. If you feel additional functionality would be useful, please provide sufficient information related to SAMM that I can at least envisage what you are asking for.

Don

 

[Gman]

Hi Don,

This thread seems to be a continuation of wbunnell's earlier thread(s) where he was describing the loss of various aircraft placed with IS2 at his airbases, and the apparent ability, and/or inability to "see" the various static aircraft libraries in the IS2 object selection pane:
http://www.fsdeveloper.com/forum/showthread.php?t=22939
http://www.fsdeveloper.com/forum/showthread.php?t=22960

While I enjoy a firm grasp of using IS2 and SAMM, I must admit complete confusion over the issues which he described.

At the time I tried to help him differentiate between the static aircraft libraries he was creating with SAMM, and the static aircraft he was placing with IS2, but I was never able to establish a cooperative effort, nor could I ascertain a clear idea of what he was trying to accomplish, or whether any of my suggestions had been successful in any way.

In hindsight, I am surprised he was not describing the sort of texture issues experienced by the other FS9 users, yet perhaps that was part of his problems.

I have just had no luck in getting him to play along with the troubleshooting process, and could only offer basic guidelines for establishing a storage location for SAMM static aircraft libraries, and a separate storage location for his IS2 airbase scenery .bgl's.

IS2 and EZ Scenery are awesome programs, but if you don't pay CLOSE attention to which location specific .bgl you are saving an object to, it can get really ugly in a hurry, and I suspect a lot of wbunnell's issues may be related to placing objects in the default .bgl. (the last one used by IS2 or EZS)

I can only recommend that after opening FS9 (or FSX) at a particular location, a user should immediately open IS2 and select or create the appropriate scenery .bgl for that location, otherwise it can, and will be a tedius process to open each IS2 .bgl to figure out which one an object or static aircraft was mistakenly saved to.
(I am speaking from experience on that )

Considering the long list of airbases shown in his screenshot, wbunnell must be having some success with whatever scheme he has worked out, but he has yet to clearly articulate what he is doing, and doesn't provide follow-up to questions asked of him.

Since I don't run FS9 I can't do much more, I hope he gets it all sorted out at some point.

 

[gadgets]

All we can do is try to help, Gary.

BTW, the only time the choice between FS9 and FSX is relevant is in designating the aircraft folder. Once the aircraft model is accessed, the remaining operation is independent of FS.

Don