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

[SOLVED] Menu Distance Request

6maynew

6maynew

Messages
139
Country
unitedkingdom
Hi Jeffery

Would it be possible to add a distance option to the XML file to enable the menu options further than 12km? I know there could be overlaps from different airports at a greater distance but having that flexibility would be excellent.

Thanks in advance
 
Last edited:
Hi,

What would be an example for this? To activate airport lighting from a distance? You are right, the radius was chosen to avoid overlaps from nearby airports.
 
Yes mainly to activate lighting before the approach if its current state is off. Perhaps a workaround for overlapping airports is to put a new menu entry in to choose a nearby airport when there is more than one in range?
 
6maynew said:
Yes mainly to activate lighting before the approach if its current state is off. Perhaps a workaround for overlapping airports is to put a new menu entry in to choose a nearby airport when there is more than one in range?
Click to expand...

Unfortunately, the SODE xml's are not bound to a specific ICAO airport, so a distinction cannot be made which object belongs to which airport.
What I can offer is to have individual objects (TriggerableVisibility) ignore the 12km filter. If you name the SimObjects properly (for instance 'EGLL Runway Lights'), it can be easily identified in the list. Max distance however will be 24km (radius of simbubble)
 
That'll be great, thanks!

Will this include separation planes too?

Along the lines of sep planes, you mentioned before that the PAPIs can't be triggered by wind direction, but they can be triggered in the menu. Is there a reason for this?
 
6maynew said:
Along the lines of sep planes, you mentioned before that the PAPIs can't be triggered by wind direction, but they can be triggered in the menu. Is there a reason for this?
Click to expand...

Triggerable visibility and conditional visibilty are handled seperately in the code and are combined in the final evaluation stage. However, whilst the separation plane is a member of the conditional visibility group, it is handled differently in the code compared to other conditional visibility variables. Sep Plane objects are injected once and then manipulated via a SimVar, whereas other conditional visibility objects are injected/removed entirely when the condition changes.

It is a design limitation within my engine where you can't have combined conditions where one of them is a separation plane...

I'll take note of this and look again if there is a possibility to overcome this limitation.

Edit:

SODE is not as dumb as I thought ;-)
Some minor changes were needed to enable sep planes and "standard" variables to be combined in a ConditionalVisibility statement.
So for PAPI systems for example, they can be automatically "turned-off/on" (->removed) depending on the available standard conditions such as wind direction.

Also, the trigger distance filter can be ignored via an additional XML attribute IgnoreRadiusFilter="Yes" within the TriggerableVisibility element.

All this is available in the next V1.3.3 release.
 
Last edited:
Yes thank you greatly! I've yet to implement it but I'm also interested in the single-object multi-placement too so all in all a good update!
 
You must log in or register to reply here.
Back
Top