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

WhisPlacer: modifying/moving default objects

B

Bob Keeshan

Messages
377
Country
unitedstates
So, I downloaded Whisplacer .9 and started working with it. A question I have is that if I want to modify the default objects in the obx files in FSX, how do I modify just the area I want without having to modify/replace the entire stock obx file?

I load the stock file, which gives me all the objects in that grid, but how do I isolate and work with only the airport objects that I want to either move, delete, or add without impacting the other objects in the grid?

Thanks.
 
Hi Bob,

I don't think it is a good idea to modify the default files. I think it is better to make an exclude and save the objects you want to move as a separate BGL file.

You could still load the default BGL file to start with of course, but I would not overwrite it when you moved the objects.

Not sure if WhisPlacer has an option to filter all the objects though.
 
arno said:
Hi Bob,

I don't think it is a good idea to modify the default files. I think it is better to make an exclude and save the objects you want to move as a separate BGL file.

You could still load the default BGL file to start with of course, but I would not overwrite it when you moved the objects.

Not sure if WhisPlacer has an option to filter all the objects though.
Click to expand...

Arno,

Thanks for the tip. Practically speaking how would I do this? Load the default BGL file, delete all the objects except what I'm working with, and save as?

Does Whisplacer allow you to use a .jpg to help align the objects? As you can tell, I'm a Whisplacer novice. I've gotten comfortable with SBuilderX for the most part, but I'd like to be able to add/revise the generic buildings, which SBuilderX doesn't allow (as far as I know).
 
meshman

I don't seem to be able to show any type library model.mdl with whisplacer. Many airports not only have generic buildings and global scenery objects but they also have library model.mdl's.

Is this a limitation of whisplacer or I am not adding something to the export properly. Many Airport model scenery Terminal's are in the city bgl and whisplacer can't export these bgl's.
 
Hi Jim,

Are you talking about the terminal buildings at the default airport? These are MDL files made especially for that airport, not building made with the XML GenericBuilding command.

I could view those with WhisPlacer by opening the OB file in which they are contained. But maybe you are talking about some other objects :).
 
Arno

I have no problem viewing all the buildings, Termianls, etc. if I open a OBX bgl. However, many many airports in the FSX scenery database did not nest the airport buildings/Main Terminals in the OBXxxxxx.bgl.

If you look at KMSP or KDTW for example all those airport buildings are nested in the proper NAMC scenery folders using the city name bgl.

Whisplacer will identify all the building model.mdl's properly as seen in the picture but nothing shows on the Grid. These model.mdl's will not export either.

The KMSP 0202/OBX2316 shows no buildings/Terminals for KMSP in Whisplacer except for a couple out buildings.


 
Last edited:
Hi Jim,

jvile said:
If you look at KMSP or KDTW for example all those airport buildings are nested in the proper NAMC scenery folders using the city name bgl.

Whisplacer will identify all the building model.mdl's properly as seen in the picture but nothing shows on the Grid. These model.mdl's will not export either.
Click to expand...

Those BGL files in the NAMC folder are just the object library. So they do not contain any placement. The objects should be placed by calling their GUID in another BGL file (probably the OB or AP one).
 
Thanks Arno

I should have realized that the city bgl's are only the object library. In my hast to try and find some of these sceneryobjects that the city bgl calls I failed to see what I was actually looking at.

This maybe common knowledge for others but there are multiple OBX bgl's for a single APX bgl.

I cannot get whisplacer to show all the Buildings and Terminals on the Grid for certain airports when I finally discovered what FSX is doing.

I will use KMSP as an example. That airport is in 0202/APX23160. Now when you open the APX you see in Whisplacer the sceneryobjects on the Guid, How you see them of course is based on options ticked.

Now you would think that all the additional library model and generic buildings would be in OBX23160 but when you open it with Whisplacer many buildings and the Main 2 Airliner Terminals do not show on the Grid.

As stated earlier the NAMC\Scenery folder has a minneap.bgl. The NAMC\Texture folder has all the .dds textures. The mystery is where are the SceneryObjects that are called.

I found them in the OBX23161.bgl. Notice this OBX has a 1 as the last digit which pairs with the OBX23160.

So if you want to see all the airport scenery of KMSP you have to open 3 different bgl's (APX23160, OBX23160 and OBX23161). The other problem is for some reason Whisplacer does bot understand the SceneyObjects in the OBX23161 and on the Grid you only get a + with a very small box around it. You can click on it and get some data but Whisplacer does not understand the SceneryObject. Not sure at this point why.

The last digit 0 vs 1 is a pattern thoughout all the scenery folder\dir#.

If a city bgl exsit in the Area letter folder (i.e. NAME, NAMC, NAMW, EURE, EURW, etc.) then there problably is a OBX ending in a 1 that is a companion to the OBX ending in a 0.

Another example is Detroit which has a NAMC\Scenery detroit.bgl.

0302
APX25160
OBX25160
OBX25161

If this has already been discovered then my post will give credit to the finder but a search did not yeild anything.
 
Last edited:
jvile said:
If a city bgl exsit in the Area letter folder (i.e. NAME, NAMC, NAMW, EURE, EURW, etc.) then there problably is a OBX ending in a 1 that is a companion to the OBX ending in a 0.
Click to expand...

Good catch Jim, did not yet know that. That makes sense. The OBX that ends with 0 places the generic objects and the geo-locked objects that it contains itself. The OBX ending at 1 then places the specific objects that are contained in the libraries in the NAMC folder.
 
meshman said:
But I like what it offers and wonder if at some time in the future there might be a seperate sub-form with Lamont Clark's input?
Click to expand...

I have been thinking about that, I will ask if he wants a special subforum here to support his tool.
 
You must log in or register to reply here.
Back
Top