It’s interesting to see that no 2020 aircraft uses these FMS. To my knowledge these are limited currently to Pilatus PC-12/24 and Saab 340 - all exclusive to 2024.
Primus Epic 2.0 Integrated Avionics System
Added MF controller event handling for for COM, NAV, XPDR buttons.
Fixed a parameter error in the Autopilot.xml template.
Intercept and manual sequencing legs can now be deleted and the route amended after these legs.
Fixed FA legs from the runway being skipped in departures.
Fixed duplicate runway legs inserted into the flight plan with some SIDs.
Fixed VNAV target readout not displaying the target altitude for passing at-and-above constraints when descending in VPTH mode.
The AP now rejects invalid flight director coupling flags (L:XMLVAR_AUTOPILOT_LR).
Some settings will now persist between flights
Selecting to amend the flight plan route now scrolls to the amend route list item
When the active leg is being tracked by LNAV, it will now display as magenta, matching the map colours.
Fixed a bug where SIDs with no runway transitions were not shown after a departure runway was selected.
Fixed an issue where invalid airports were automatically entered on the flight plan page on power up.
Fix METAR date handling for systems that have date displayed as [Month] [Day]
instead of [Day] [Month]
Fixed PFD displaying incorrect wind data
Fixed errors in model behaviours due to incorrect tag names
Fix nav preview text overlap
Fixed various input fields not being editable via the TSC keyboard
Fixed various input fields not losing focus when the enter key is pressed
Fixed an issue where some facilities did not appear in the select object dialog, and improved the layout.
Fixed an issue where duplicate waypoints with discontinuities appear in the flight plan when amending the route.
Pressing the direct to button on the TSC now scrolls the flight plan to the direct to window.
Fixed handling of the enter button on the direct to random window.
Fixed incorrect procedure legs being removed when changing procedures.
Fixed erroneous transitions being displayed for SIDs and STARs with no transitions.
Fixed VECTORS approach transition selected by default and no de-selectable.
Fixed STAR/APPR/transition combinations that are not compatible with existing selections being shown.
Fixed the activate vectors button positioning and logic.
Fixed flight paths at the connection between STAR and approach transition.
Fixed merging of approach transition and final approach when the transition joins the FAF.
3 and 5 letter airport idents are now accepted as origin and destination.
Fixed destination fuel remaining unit on the flight management window.
Fixed an issue where the right-side TSC outer and inner knob functions were swapped when setting the transponder code.
UNS-1Ew SBAS-Flight Management System
When on flight plan menu page, the flight plan page button would not work.
Nav page would not show Estimated Time Enroute and Estimated Time of Arrival
Nav page would not update the TO leg’s distance to go
Nav data page would not show up to date nav data expiry
After emptying the flight plan, the arrival/departure pages will now remove old procedure information
Changing the arrival airport from the arrival page, will now remove any arrival procedure selected for that airport.
When an airport is inserted as the last leg of the flight plan, if no approach is selected it will be made the arrival airport
Fixed handling of heliport elevation in the waypoint ident page.
Fixed FA legs from the runway being skipped in departures.
Fixed duplicate runway legs inserted into the flight plan with some SIDs.
Fix CDI scaling label always displaying as Terminal
Fixed arrival page not updating data from the flight plan on it being loaded
Fix departure page not updating runways after inputting a runway
Fix not being able to select a departure if a departure with no transitions has already been selected
Fix power/dim overlay not displaying properly on the LIST page
5 Likes
Dornier SeaStar also uses Primus Epic 2, but it is MSFS 2024 exclusive, too.
1 Like
Matt told some time ago at least on the WT Discord that both avionics sets were silently added to MSFS 2020 on SU15 so addon creators can make use of them, even if no default aircraft utilizes these avionics actively
In short (from the WT Discord):
1 Like
It would be fantastic if the AN-225 got the UNS-1 if they now give this option.
1 Like
As the AN-225 still awaits proper porting to MSFS 24 that might be the case if iniBuilds would be so grateful.
However ini are a bit picky on what they do - MS would have to command them to add this option and thus it’s unlikely.
This is especially funny as Mike proves with the Albatross that MS does not specifically has to ask a developer of a first party aircraft to implement or change certain aspects and that the devs are free to change and add features.
MS does clearly not act as a gatekeeper in that case.
Doesn’t the Just Flight Avro Jet, Bae 146 v2, and Fokker F28 v2 use the UNS-1?
Yes, those are 2020 aircraft
I believe those are all custom UNS systems unrelated to the ones Asobo had created for 2024.
2 Likes
I was going to say, if WT had snuck them into SU15, how did these developers get it into their planes without prior notice it was available?
Of coarse those aircraft were released long before MSFS 2024 was announced.
But I do wonder if this new Asobo overhaul will have any effect on the existing aircraft that already use them.
BTW if the Saab 340 is an example, then the 2024 UNS-1 implementation is horrible.