Hello,
I’m currently utilizing the UNS-1 on a number of projects, and upon first inspection i’ve come up with a number of questions/failures:
We’re on the same page with this. EFB Sync is particularly important.
Assuming this is about MSFS2024 rather than the tagged MSFS2020… Make sure you are using WTUns1v2 to get the MSFS2024 version of the avionics that includes EFB sync i.e. Pages\VCockpit\Instruments\NavSystems\WTUns1v2\WTUns1.html. The EFB and EFB sync is intended to be the common interface for loading flightplans. VNAV is not included.
Further docs: Working Title UNS 1LW Overview | MSFS Avionics Frameworks and Instruments
EFB Sync doesn’t seem to be functioning…
Are you saying it isn’t working in the v1 UNS (included for MSFS2020 backwards compat), or the v2 UNS (should be used in MSFS2024 aircraft, as in my message above)? It is not intended to work in the backwards compatible v1 instrument, as there’s no such thing as EFB sync in MSFS2020.
V2 (FS2024 Gauge) does not seem to be working with EFB Sync. For example, it does not function on the Saab, which uses the UNSv2 Gauge.
Please ask UNS-1 questions at Working Title’s Discord. They created the Instrument, and have a dedicated channel for the FMS.
The Saab 340 is unfortunately not using the v2 UNS. The version is shown on the boot screen (WT 0.1.1).
If the UNS v2 is used you will see WT2.0.x on this screen, and it will have EFB sync:
See this post for how to make sure you’re using the v2 in your aircraft: UNS-1 FMS: Questions - #3 by tracernz
I doubt Saab use v2 version sound like use v1 version
While yes, we do have a channel for UNS-1 feedback, I would kindly ask that folks not be rerouted to our Discord from here. This is an official support source, while our Discord is very much not.
Thanks,
Matt
We’ll send them to the Support Thread on the User Forum then. I created one just like G1000NXi, G3000, G3X etc., after AAU1. Trying to help the team here stay focused on Dev questions. A lot of end user/player questions end up here by accident. 
