As we do not have a "non-rnav" or an rnav equipment code in the flightplan equipment, non-rnav SIDs need to be assigned manually right now.
To get info about RNAV capability we need to check the PBN in the remarks.
As the remark field is not reliable for Vatsim purpose, we should assume all aircraft are RNAV capable (as most of the pilots on Vatsim are), except when the filed PBN without RNAV capability.
In the config all SIDs should be RNAV SIDs by default and NON-RNAV need to be marked ("non-rnav"=1). Assigned only for NON-RNAV aircraft by the plugin.
As we do not have a "non-rnav" or an rnav equipment code in the flightplan equipment, non-rnav SIDs need to be assigned manually right now.
To get info about RNAV capability we need to check the PBN in the remarks.
As the remark field is not reliable for Vatsim purpose, we should assume all aircraft are RNAV capable (as most of the pilots on Vatsim are), except when the filed PBN without RNAV capability.
In the config all SIDs should be RNAV SIDs by default and NON-RNAV need to be marked ("non-rnav"=1). Assigned only for NON-RNAV aircraft by the plugin.
https://support.foreflight.com/hc/en-us/articles/360049193173-ICAO-Equipment-Guide
Beside that we could create a settings file where we list all aircraft that are usually non-rnav (e.g. Concord) and PBN need to be filed if rnav.
We could also check for the FAA codes.
As this feature requires to check the PBN, we could add the PBN codes to the already existing "Equipment" setting.