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

suggestions?

Status
Not open for further replies.
Mace said:
I was looking for a way to click-n-drag to create an <ExclusionRectangle> with a ExcludeGenericBuildingObjects=TRUE for example.

I am not seeing this anywhere, but perhaps I am missing it?
Click to expand...
No, you are not missing it, it is on the to-do list. I thought you were meaning exclusion polygons which are available.

However, for generic airport buildings, all you need do is select and delete.

George
 
Last edited:
Mace said:
Good point about the stout beer? Yes for sure.

I was looking for a way to click-n-drag to create an <ExclusionRectangle> with a ExcludeGenericBuildingObjects=TRUE for example.

I am not seeing this anywhere, but perhaps I am missing it? I've been known to miss my share of obvious things.
Click to expand...

No there isn't but I come back to the question about what you would want to exclude that ADE has not already handled.

To explain how ADE works. If there are stock taxisigns then ADE creates an exclusion to over ride the stock signs. Thus all signs at the airport are now being generated by the ADE custom bgl. The same is true for library objects, generic buildings, widnsocks and fuel triggers. If they come from the stock airport then ADE has created an exclusion rectangle. Thus again all these items are now coming from the stock file. If you do not move or delete any of them then they look like stock but you can delete them all in ADE and you will end up with an airport without any buildings and other objects.

If you are looking to create an exclusion rectangle to remove them then you would be duplicating something that is already done. So to take your example about generic buildings - with ADE you do not need to do that it is already done.
 
I did not generate my airport using ADE. It began life as raw xml. It existed this way for many many months. I then imported it into ADE using the load xml function. It seems to me that when this is done, apparently ADE is not generating these ExclusionRectangles automatically, because it did not exclude any of the stock generic buildings at MHTG. Nor did it exclude any of the LibraryObjects. ??

Perhaps this would have been different had I started the airport from scratch using ADE, but you must realize that when I started this airport, ADE did not yet exist...
 
Perhaps this would have been different had I started the airport from scratch using ADE, but you must realize that when I started this airport, ADE did not yet exist...
Click to expand...

In that case you merge your XML with a Stock ADE XML.

I have converted many of my airports made prior to ADE with the merge technique. Open and save a Stock airport. Compile so you get the XML. Open your XML and add any thing you need into the stock ADE XML.

Remove any of your excludes and use the ones that ADE aready made. Do not use any of your scenery objects if they are already in the Stock ADE xml. Pay strict attention to the Tower scenery objects that may be nesting in the wrong place in your XML.

Once you have all your XML data in the ADE XML then reopen the ADE XML and save as a .ade. From this point on everything you have previously done is in the .ade saved file and will show on the grid properly.

Anyone that uses ADE can now open your upload and change gates, etc. if they want to and save. Nothing you have designed previously will be lost.
 
Last edited:
Mace said:
I did not generate my airport using ADE. It began life as raw xml. It existed this way for many many months. I then imported it into ADE using the load xml function. It seems to me that when this is done, apparently ADE is not generating these ExclusionRectangles automatically, because it did not exclude any of the stock generic buildings at MHTG. Nor did it exclude any of the LibraryObjects. ??

Perhaps this would have been different had I started the airport from scratch using ADE, but you must realize that when I started this airport, ADE did not yet exist...
Click to expand...

Rhett

That is a good point. However if you run Load Stock Data from the Tools menu it should add the buildings etc to your airport and automatically generate the exclusions for them. If it doesn't then there is a problem.
 
scruffyduck said:
Rhett

That is a good point. However if you run Load Stock Data from the Tools menu it should add the buildings etc to your airport and automatically generate the exclusions for them. If it doesn't then there is a problem.
Click to expand...

Ah, I see. I did not "Load Stock Data" because I assumed it would add this data to my airport. I didn't want that.

One thing, that you did, that I really, really like is the fact that ADE does not mess with my existing xml. I loaded my xml, with its custom exclusions, and ADE kept them intact. I thought that was wonderful. I have seen other design apps break xml. That's why I was concerned about co-mingling obx and apx type xml data the other week. That was the source of my concern. I see that this is unfounded with ADE.
 
jvile said:
Anyone that uses ADE can now open your upload and change gates, etc. if they want to and save. Nothing you have designed previously will be lost.
Click to expand...

This was 100% of my concern when I raised the issue of mixing obx and apx data (see above post). Not an issue with ADE I see. Good.
 
Mace said:
Ah, I see. I did not "Load Stock Data" because I assumed it would add this data to my airport. I didn't want that.

One thing, that you did, that I really, really like is the fact that ADE does not mess with my existing xml. I loaded my xml, with its custom exclusions, and ADE kept them intact. I thought that was wonderful. I have seen other design apps break xml. That's why I was concerned about co-mingling obx and apx type xml data the other week. That was the source of my concern. I see that this is unfounded with ADE.
Click to expand...

We will add the custom exclusions but we are concerned that users may just duplicate what ADE has already done - I guessthat will be down to education :D
 
I've also shifted to Jim's method for updating airports I've done before in ADE. It is pretty much how I used to use SGX, but more automated.

scott s.
.
 
Ian Broadbent said:
How about capability to add road traffic? Couldnt see this in the manual. :)

Ian
Click to expand...

Well the Add Vector tools includes the type Freeway and the tag Freeway Traffic. I think that may be what you are looking for?
 
Ian Broadbent said:
Tried it but didnt get any moving traffic moving traffic :(

Ian
Click to expand...

Right well maybe one of the others can comment - I would no know why it doesn't work as that is the only tag I am aware of that covers moving traffic
 
Ian Broadbent said:
No problem, it would be nice, to get traffic moving ;) I can always sort it in SbuilderX hehe
Click to expand...

Make sure you have your traffic slider turned up a little in your FSX display settings...traffic tab.

I use FSX_KML for road traffic at the present time, so I can't comment on the ADE implementation of this.
 
scruffyduck said:
We will add the custom exclusions but we are concerned that users may just duplicate what ADE has already done - I guessthat will be down to education :D
Click to expand...

Jon

Let me get this straight in my mind. You are saying that ADE generates its own ExclusionRectangles. You are NOT referring the the <DeleteAirport> command are you? We're talking ExclusionRectangles here, yes?
 
Mace said:
Jon

Let me get this straight in my mind. You are saying that ADE generates its own ExclusionRectangles. You are NOT referring the the <DeleteAirport> command are you? We're talking ExclusionRectangles here, yes?
Click to expand...

Rhett - we are talking about exclusion rectangles. ADE generates the exclusion rectangles needed to exclude the library objects, generic buildings, windsocks and fuel triggers from the stock airport.
 
scruffyduck said:
Rhett - we are talking about exclusion rectangles. ADE generates the exclusion rectangles needed to exclude the library objects, generic buildings, windsocks and fuel triggers from the stock airport.
Click to expand...

Ok, then that naturally leads to my question, and suggestion. :)

Q: Why does ADE create these exclusions automatically? Is there some advantage to doing this?

S: Allow the user the option of disabling this automatic creation, or at least the ability to see and delete these items in the GUI. As it is right now, I'd have to decom it and take it out manually...unless there is some view item I'm missing.

I have had many occasions where I kept some of the stock GenericBuildings. I've also had situations where I kept some of the other objects (like triggers).

I can see where some users may get confused about having stock items in place. Perhaps this was the reason for the design choice to have ADE create these automatically?
 
Mace said:
I can see where some users may get confused about having stock items in place. Perhaps this was the reason for the design choice to have ADE create these automatically?
Click to expand...

There is nothing to be confused about. Forget the automatic exclusions, the user doesn't need to know about these. The stock items will still remain until the user decides either to delete or move them.

George
 
Q: Why does ADE create these exclusions automatically? Is there some advantage to doing this?
Click to expand...

Of course - what you see in ADE is what you get in FSX.

S: Allow the user the option of disabling this automatic creation, or at least the ability to see and delete these items in the GUI. As it is right now, I'd have to decom it and take it out manually...unless there is some view item I'm missing.
Click to expand...

We all do things differently, of course but that would, in my view anyway, cause confusion. If ADE did not do that then users would have (a) to delete the stock object in ADE and (b) create an exclusion for it. Why do that?

I have had many occasions where I kept some of the stock GenericBuildings. I've also had situations where I kept some of the other objects (like triggers).
Click to expand...

Which is eactly what happens in ADE - leave all the stock buildings and objects in the ADE project and they all appear in FSX. Delete, modify or move any of them and that happens in FSX

So I go back to my original question - why would you want it to work any other way if it saves you the trouble of having to generate your own excludes when they are already done for you.

As George say - just ignore them. If you delete an exclude that ADE makes without removing the object it is excluding you are just duplicating the object in FSX with no advantage.

Sorry but I am still lost as to what you want to do that this approach is stopping or making more difficult
 
Status
Not open for further replies.
Back
Top