UNS1 hard locks when loading a route between YSSY/YBBN

Melon

UNS1 hard locks when loading a route between Sydney and Brisbane. Both when attempting to import the file, and when entering it manually. When entering in manually it locks up instantly you select Arrival from the Menu page. I was able to enter origin, the route and the destination and select the departure, just not anything to do with the arrival. Have repeated this 4 times now to make sure, even attempted a YSSY/YBBN on its own and just selecting the departure and arrival, and it still hard locked the moment you select arrival. Tried YSSY/YBCG and that worked fine as you'd expect. Lastly I tried it again with the 'Modern' FMS and it worked fine as well with no lockups.

YSSY/16L KEVIN7 OLSEM Y193 BANDA H252 GOMOL GOMO3A YBBN/19L

Would upload the .rte but can't.

With regards to Brisbane I have Orbx Brisbane installed and AIRAC 2403 Rev.5 (the latest as of this post, and reinstalled fresh for testing).

Have tried the same YSSY/YBBN combo with just Departure and Arrival and no routing in the Fokker 28 with the Garmin and it worked fine.

I'd say something seems wrong with the NavData itself, but the fact that it works in the alternate configuration and in a different aircraft kind of puts that to bed so my best guess is something funky in the UNS1 with regards to reading Brisbanes NavaData. I've done about half a dozen flights so far to other airports with 3rd party scenery, and this is the only one that has caused an issue so far, and its kind of important to my regular routes.

Mark

@Melon Thank you for reporting this. I have been able to reproduce this with and without Orbx's YBBN installed, so it looks like the issue is either within the Navdata or with the UNS-1 (I suspect the former as it's not an issue we have had reported at any other airports). The issue seems to be specific to YBBN, so it's not related to that specific YSSY-YBBN flight plan.

We'll get this properly investigated and pass on our findings to the UNS-1 development team. If there's something we can do to fix this on our end, we'll include a fix in an update to the 146.

Mark - Just Flight

Melon

@Mark Thanks. It's a weird one, I'm curious what it would be. I wonder if its because of how some of Brisbanes approaches are named.

Melon

Just to let you know @Mark it seems like you can depart Brisbane just fine using the UNS1 9based on the flight I did last night), its only arrivals that cause the issue.

Mark

Yes, that is the behaviour I am seeing too, so it must be something specific to the YBBN arrivals in the Navdata that the UNS-1 doesn't like. This is all logged on our internal bugs tracker and the UNS-1 development team has been made aware of it, so hopefully, we should be able to get some answers and a fix implemented soon.

Mark - Just Flight