Missing waypoints in STAR
Posted: Fri May 17, 2024 5:01 am
Hello
I have a problem, on multiple airports with complex STARs. Specifically seems to be with Point merge systems. Problem is proven at ENBR, ENGM and ENVA specifally, but suspect it is on all airports with point merge arrivals.
Specifc example:
ENBR, 17, PESUR3N arrival. Goes PESUR BR627 BR624 LUTIV BR623 BR622 BR621 BR620 GILVA
In the aircraft, PESUR3N for 17 goes BR627 BR624 GILVA. This is a huge problem flying the aircraft under ATC on VATSIM, and has been a major flaw in default FMS for a long time. Asobo does not seem to care about this problem.
When I bought the aircraft in Marketplace, there was nowhere it stated use of default navdata/FMS. It said the product uses Navigraph, and that it featured "Customized systems of the Airbus A340-300, simulating its basic cockpit functionalities"
You state Simbrief implementation, and mention Navigraph navdata. I expect the aircraft to be able to fly a full STAR according to Navigraph navdata.
Is there any solutions for this problem?
I have a problem, on multiple airports with complex STARs. Specifically seems to be with Point merge systems. Problem is proven at ENBR, ENGM and ENVA specifally, but suspect it is on all airports with point merge arrivals.
Specifc example:
ENBR, 17, PESUR3N arrival. Goes PESUR BR627 BR624 LUTIV BR623 BR622 BR621 BR620 GILVA
In the aircraft, PESUR3N for 17 goes BR627 BR624 GILVA. This is a huge problem flying the aircraft under ATC on VATSIM, and has been a major flaw in default FMS for a long time. Asobo does not seem to care about this problem.
When I bought the aircraft in Marketplace, there was nowhere it stated use of default navdata/FMS. It said the product uses Navigraph, and that it featured "Customized systems of the Airbus A340-300, simulating its basic cockpit functionalities"
You state Simbrief implementation, and mention Navigraph navdata. I expect the aircraft to be able to fly a full STAR according to Navigraph navdata.
Is there any solutions for this problem?