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

FSXA Problems at default KABQ

I agree that the issue is autogenerated library objects. It is possible for the OBX files that ADE has the original data and these were updated with Accel. so the airport being loaded is the Accel version but the data being held in ADE is pre Accel. One solution would be to provide access to the stock scanners in ADE.... I need to take a look at that.
 
Hang on. It doesn't matter which version of FSX is installed, ADE, unlike AFX doesn't scan all scenery files at startup. ADE is installed with a pre-defined set of stock files.
 
The issue of black box objects has been discussed many times and what you need to do to fix this is also covered in the readme with the 1.6 installer. There is an article on moving data between versions: https://scruffyduck.screenstepslive...01-how-do-i-transfer-my-data-between-versions. The black boxes, as you found, appear if the objects are not in the LOM. The reason for them is to warn you that you do not have any information about them in ADE. The reason that they are not compiled is because it may be that the user compiling them does not have the object libraries. This may not sound much of an explanation but this issue has been debated a lot of times without a proper conclusion. I am sure there are other threads here on this and you really can't move or turn them since you don't know anything about their footprint.

Having said all that the next release of ADE will offer that users with black box objects in a project can compile them. This is really if you load a third party airport. HOWEVER the answer if they are your objects in your projects is to either update the database (if you moved versions) or add the libraries to the LOM. That way you get sizing information and a bunch of other stuff.
Thank you for your attention, Jon.

Having the ability to compile "black boxes" will greatly enhance an already wonderful product.

At the very least I do not think it should be an end-user responsibility to add default objects to the LOM. If it is, there needs to be documentation stating so.

I am confident you will address this so it is not end-user responsible.

Thanks to all for participating in the discussion.

cheers,
Lane
 
Jim,
not sure how you are getting them?
I have all 5 FSXP acceleration bgl's added to v1.61 and i still get black boxes at KABQ!!
as i said in a previous post v1.50 was ok, v1.55 and on isn't giving me or others the same..............
 
Last edited:
Some of the airports you guys will see with the small square black boxes are

EDDI
KRNO
KABQ
KEDW
TNCM

What these have in common, they were all enhanced with additional airport scenery per Acceleration. Some of the scenery is in the city bgl such as Albuquerque.bgl, some in the OBX bgl and some in both places.

There are also other airports that got small modifications such as Key West (KEYW). You have to look deep to find the problem but like the other airports most of the problem is the autogenerated scenery that has the additional model data at the bottom of the OBX files.
I can confirm that, now I think of it, when I was looking at KEYW a few weeks ago, I did have the problem of a few black boxes so I am sure Jim is on the right track when defining where this problem is happening.

Just added OBX26230 to my LOM and the holes at KEYW (terminal buildings) have been filled in and some nice large buildings close by as well!
 
Last edited:
I will look at this. The immediate solution will be to allow users to decide on a project by project basis whether to compile the black box objects or not. I agree that ADE should be able to provide stock objects but I would warn that this is not quite a simple as it seems. George is right that ADE does not scan on start up like AFX. However this is not an airport issue. AFX does not handle objects - it is scanning for airports only. Scanning AP files is one thing, scanning almost everything to find stock models files is rather different. These can be in AP files, OB files, NV files and all those special city files. And of course they are in the stock object library Bgl files as well.

There is also a difference between placement code and models. When ADE does a stock scan for an airport it looks for placement code and not models. That is why you are getting the black boxes. The biggest issue is OBX autogenerated objects. There are a large number of these and cluttering the LOM with them raises another set of issues. Anyway I appreciate the potential annoyance of black boxes arising from stock airports and I will revisit how ADE handles them.
 
I agree, I don't think ADE should automatically compile references to objects it doesn't know about. Currently I am using ADE to remove such references in a fairly large pack of freeware airports.
 
Right George. If ADE finds black box objects in a project it will ask you if you want to compile them or not for that specific project. It will do this the first time and then remember your choice. This is project specific so you can choose to compile them for project A but not for B, C or D.
 
Right George. If ADE finds black box objects in a project it will ask you if you want to compile them or not for that specific project. It will do this the first time and then remember your choice. This is project specific so you can choose to compile them for project A but not for B, C or D.
Jon, forgive my lack of understanding about these matters but this is teaching me a lot about how FSX and ADE work.
It seems that you are saying that ADE recognises that it hasn't found some FSX objects and so it will only display them as black boxes but that you will be able to allow the user to get ADE to go and look for the data in order to provide a fully populated compilation file. This would seem to be the ideal solution assuming that no other problems arise from doing so.
 
There isn't a scan Jim. The initial database has already been created by Jon.
 
Jon, forgive my lack of understanding about these matters but this is teaching me a lot about how FSX and ADE work.
It seems that you are saying that ADE recognises that it hasn't found some FSX objects and so it will only display them as black boxes but that you will be able to allow the user to get ADE to go and look for the data in order to provide a fully populated compilation file. This would seem to be the ideal solution assuming that no other problems arise from doing so.

When ADE loads a project it loads the placement data for the library objects. Placement data is what it says - it tells us what the object is (using the GUID) and the coordinates it should be placed at. (there are some other bits as well but they are not relevant right now). At the point of load ADE knows the reference to the object (GUID) and where to put it.

It doesn't know about the size of the object, its name and so on because that information is not stored with the placement data. That information is stored in the Model (mdl file). Model files are often in libraries and not associated with the placement data. The data about size etc is what is needed to turn a black box object into the normal yellow shape in the diplay. Without it we have a black box. There are a couple of data files in ADE that store this extra information about the model. This is what you see in the Library Object Manager (LOM). ADE does not store the models themselves just some extra data about them. It gets this because we scan a clean stock version of FS looking for library objects and when we find them we add data about them to the LOM. Guaranteeing that all the objects in a stock version of FS are found and collected is not that easy particularly with FSX. There are several releases of FSX and the Acceleration Pack with different libraries and different objects. So it is possible to get black boxes with stock airports.

So why don't we just load all the objects? Well this may (and did when we shipped a wrong version of the database) lead to some users having objects in the LOM that they don't have on their computer. Now we have the reverse problem to the black box - perhaps it should be a red box! This is an object that a user finds in the LOM and places at an airport. Then when they compile it they don't see it - because they don't have the libraries. My experience is that it is worse to have objects in the LOM that a user does not have than to have black boxes.

A long explanation of why ADE does not just ship with every possible stock object from all the possible versions of FSX. FS9 and P3D are not so bad since ADE runs separately for them.

I think the bottom line here is that if you get a black box then ADE can't tell you what library it came from. Some black boxes are stock objects and we could handle that by having a background database that has all the objects but is not loaded into the LOM (this actually exists but it appears to be out of date which might be why the current thread started). Then ADE could say - you don't have this object in your LOM but I know where it is.

And just when you thought it was safe to come out of the cupboard we have to consider the black boxes that are for objects coming from third party libraries - and unless we created a database of all guids for all objects in every library created then we are not going to be able to say - I know where that one comes from.......................

I suspect I just made it all a lot more confusing but this is something I have been wrestling with since the earliest version of ADE that supported scenery objects.
 
this is now very confusing!!!
i did not have this problem with v1.50,
Jim sees the objects ok at KABQ in v1.61 and I'm not,
so what can the difference be if I'm not seeing them and Jim is and we both have the 5 FSXP bgl's in the LOM
i wonder what else i have missing in v1.61, very strange
 
Yes Jim,
not a yellow box in sight
black boxes at Reno as well
i cant get my head around why v1.50 is ok!!!
 
and this is my stock EDDI



There is nothing in my LOM about Berlin or its companion OBX.

There must be more then one scenery database since my V1.61 does not show black boxes. I can only tell you that all my acceleration enhanced airports including OBX autogenerated objects are somewhere in ADE since Jon has to add them as per George. But then again both Jon and George also see black boxes.
 
Last edited:
cant get access to your pic Jim
I've also not added the extra bgl's don't see why i have to
most odd!!
 
Try this one and see if the pic shows

fsscr011.jpg
 
Back
Top