gameagle / vsid Goto Github PK

white - suggestion but not set
orange - manual set, height deviates from SID
cyan - climb via
green - climb

• If a SID has been set (SID/RWY block) assume the RWY was set by controller and set it to green
• If the DEP ICAO has been set (ICAO/RWY) and a ground state or clearance flag has been set or flightplan is amended assume it was by controller and set it to green

If the engine type is set to "J" in config the SID is marked as manual (orange), e.g. TUBLU7S in EDDM

It can happen that with a click on a rwy in the rwyTag Item another rwy from that list is set. If the same entry is clicked several times the rwys might jump around.

Seems to be linked to the same problem we had with the initial climb menu.

If no config exists it could lead to multiple outputs in the chat, e.g. EDLW

We now are at a point where route altering is needed multiple times, therefor outsourcing this work into an extra file (flightplan.h/.cpp) would improve the code

E.g. 4 Points would be drawn like: 1 + 2, 2 + 3, 3 + 4, 4 + 1 for a rectangle

When a ICAO/RWY block has been set (RWY selected by atc) and a SID is entered after automatically the ICAO/RWY block is not removed

Providing a plugin pdf handbook

WTC, Type of engine, Number of engines, MTOW

Filter out VFR flightplans from SID checking

Possible IC: Get the requested flight level as initial climb

If a SID is disabled for LVP checking (-1) then no SID can be found because every SID is ignored.

Add a setting to be able to accept arrival runways as departure runways per airport basis (e.g. 25L in EDDF)

Reproduce:

1. Select a custom RWY via RWY dialog
2. Manually select a SID that matches that RWY from the menu
3. RWY is reset to the first RWY value

(e.g. EDDF/25L SOPRA8F is reset to SOPRA8F/25C)

Workaround:
Set the departure RWY again, this keeps the SID but changes the RWY

If we set a RWY for a VFR flightplan MANUAL is displayed as SID, should be "VFR" or nothing

As we now are able to allow arr as dep rwy the correct dep SID is displayed in yellow.
With a click on the SID it isn't set but rather the default SID is set instead

If a rwy has been set the autoselection of the SID should consider it.

What happens if no SID has been found?

To be able to use SIDs for SVFR or NVFR we need to allow manual selection of SIDs.
For this we have to populate valid departures although no waypoint is set in the flightplan

Implement a TagItem for RWY selection as follows

• get possible rwys from airport config
• (if able sort them by dep rwy first and arr rwy second, inactive rwys maybe in disabled look)
• color white: suggestion but not set (get suggestions possibly of ES default or from the possible found SID)
• color green: set in fpln (also in ICAO/RWY format) or if SID set (then we don't have ICAO/RWY blocks anymore - possible via now set dep RWY)
• color yellow: set in fpln but is not a dep rwy

If e.g. EDDF/25C is set and the check for a correct SID runs it could happen that a 07C rwy is matched and the wrong SID returned.

Could be linked to color coding. Complete check of the check process is needed.

If e.g. A45 is selected 060 is set as cleared altitude. This is send by sItemString which means the ES own value, which doesn't match the list that is being shown.

As the value technically is set correct because the send value by ES matches the set cleared altitude value in the flightplan maybe the internal list and adding popup elements have to be populated seperately

If a flightplan was filed wrong sometimes the SID cannot be extracted. A waypoint might exist somewhere in the flightplan, but not where it should be.

Possible scan for each waypoint in config if it exists somewhere in the flightplan.

For the option to use different SIDs only in specific times there is a need of

• checking the users system time (ES doesn't offer a time check)
• change it to UTC based on time zone
• change local time in airport config also to UTC based on the time zone (possibly needed in config)
• check if the user time is in config time boundaries

After those checks we can compare if a specific SID has to been used

Now the initial climb is 0, but it should be the set IC by atc

As a closed rwy is skipped during validation MANAUL is displayed for the SID, although there might be a valid SID.

Could be investigated if a suggestion should be made nontheless

The clmb value then shows a very large number. Possible check if no cleared altitude is set to ignore it

Change from only active RWY to a DEP and ARR Rwy config to be sure which RWY is the correct one to set.
Otherwise this results in possible SID assignements

If we have an initial climb stored internally set it again after a fpln reconnects and a SID is still entered

Especially for the rwy tagItem to color code the RWY and set the string only if the fpln was amended and not if e.g. Simbrief has this entry set in the fpln

A command is needed to be used to switch between LVO and Non-LVO

If somehow GRP LVP state could be accessed this could be used as well as long as GRP is loaded.

Parameter check for commands could be helpful, e.g. to don't have a case for every possible command but rather send messages by context.
This means e.g. if only ".vsid" is entered all possible commands that could follow should be displayed.
This could also be used for help texts if a command is not used properly

2 eng heavy is assigend SOBRA7P during 25C ops. Should be SOBRA8F

When we do not have a SID set the flightplaninfo IC is always empty (normal VFR flightplan) thus "----" is displayed although the setting of an IC / tempAlt is working

When only selecting a runwy or selecting a sid the matching rwy should be saved in the flightplaninfo.
By this we can check if a RWY does not match what the SID uses (color coding).

Save vSID settings in ES settings to be loaded at the next start

If a SID is in the flightplan which doesn't exist change color to red.
Could happen e.g. if outdated data in other plug-ins is used

Improvement would be to display "----" or "N/A". Maybe add a config option for this