Navdata Updates

[Jarryd Perry]

I have always been a big fan of iniBuilds and their products. The new A350 looks amazing! However, there’s one thing that’s putting me off from getting this and any future aircraft: the navdata problem.

What I can’t wrap my head around (correct me if I’m wrong here) is why, with the now-default A320, we still don’t have accurate navdata for waypoints, SIDs, and arrivals. To me, this defeats the purpose of even having the aircraft on the platform. I know it’s not an issue at every airport, and I understand it’s related to the plane using the default navdatabase.

But I just don’t understand why this isn’t being addressed. It’s all well and good to have the aircraft available, but what’s the point if we can’t operate it properly? surely it would be in Asobo best interest to sort this out especially for a default aircraft.  

[YoursTrulyJack]

I have to agree.

I'm only just learning (the hard way) that all of the iniBuilds Airbus' use the default navdata having tried to perform a flight between VHHH and ZSPD, whereby the data for the STAR (BK91A > ILS Z 35R) shows waypoints along it 6000nm miles away, bringing the EFOB to its knees and dragging the frame rate with it. Load the same route into the Fenix A320 and it is faultless; with Fenix using Navigraph's navdata. 

Whilst I haven't faced the same issue at other airports yet (barring VHHH initially but managed to fix this), it troubles me to think that, at any one time, I'm not using the reliable Navigraph navdata that I have installed and am instead relying on the "somewhat" reliable default navdata.

It's a big shame for me as the A330 was the aircraft I was looking forward to the most out of all the aircraft that came with the sim upon launch. With the A350 round the corner and very hotly anticipated by the community, myself included, I can't help but worry about the cost of the product vs its functionality when it comes to navdata.