Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content
Sierra Charlie Mike

Problem with flight path curves in ND at EDDF (PSA25S), A320 v1.2.5.0

Recommended Posts

Hello Gentlemen,

 

I'm having a problem with the curves of the flightpath drawn in the ND. The error occurs on the PSA 25S RNAV Transition of EDDF. I'm using the Version 1.2.5.0 A320/A321 and my P3D-Version is 4.4.16.27077. I'm using the current Navigraph cycle 1909. The whole route is EDDF ANEKI2A ANEKI Y163 PABLA DCT KOVAN T163 PSA PSA25S ILS25C EDDF. The waypoints of PSA 25S are: PSA CHA DF606 DF610 DF616 DF626 DF621 REDGO.

 

The following screenshots illustrates my problem.

 

 

Thanks in advance,

 

Stefan

 

 

 

Approaching CHA, notice the strange flight path drawn between DF606 and DF610

1.thumb.png.86b9785216a0545e1d714cab3b47dad8.png

 

CHA passed

2.thumb.png.b476810f7fabef85e2260612e940b13c.png

 

Approaching DF606

3.thumb.png.4b83d53f4dfe2dfa8005ee593a5b352b.png

 

DF606 passed, approaching DF610

4.thumb.png.e3a50a6bfc665fa1e004ad051ff8f63d.png

 

5.thumb.png.e22b5565acc92c37d28a07dd226e5f14.png

 

Approaching DF616

7.thumb.png.4e9574678c89b5461c276253daf26ab6.png

 

Approaching DF626

8.thumb.png.0e38f78c14b18f39c14e3346ecd27546.png

 

9.thumb.png.e8b9d9967f5dca1731a89cf110f6ff30.png

 

Flight path

10.thumb.png.3febc68671a1a8edef3c4380b9cedc96.png

6.png

Share this post


Link to post

Hello Stephan, and welcome to the forums!

 

I just entered the route you were kind enough to provide and flew it, and I didn't see any issue.  I'm using Navigraph 1909 as well.  Below is my screen shot.

 

Are you sure that you selected Navigraph in the Airbus Configurator?

 

Screenshot - 9_2_2019 , 1_43_00 PM.png

Share this post


Link to post

So I just noticed that on my system, it's using different approach waypoints than it should be.

 

I'll have to investigate this a little further.

 

Share this post


Link to post

What I see has nothing to do with the PSA25S transition, unfortunately no screenshots of the FMC were attached.

But I can assure you that the Airbus normally displays and uses the transitions correctly.

Were the entries in the FMC correct?

Dave didn't use the transition, by the way, but a PSA STAR.

 

Wolfgang

Share this post


Link to post

Just an update on this.  We found a little issue when researching the OPs situation, and the reason that some of the arrival/approach is missing (see my post above regarding different waypoints) is that this occurs if the CHA transision is selected in the MCDU.  We're looking into this, but it works fine if you don't select a transition that is already part of the flightplan/arrival/approach.

 

Regarding the OPs situation, I flew the same route without any issues (so long as speed is not too high, I used 210 kts as this is what is used in real life).  OP is going to check that he has Navigraph selected in the Airbus Configurator, and that or his speed may have been the issue.

 

Best wishes!

 

 

2 hours ago, Hoffie3000 said:

What I see has nothing to do with the PSA25S transition, unfortunately no screenshots of the FMC were attached.

But I can assure you that the Airbus normally displays and uses the transitions correctly.

Were the entries in the FMC correct?

Dave didn't use the transition, by the way, but a PSA STAR.

 

Wolfgang

 

I did, but that is what created the issue in my route.  We're looking into this.

 

Share this post


Link to post

New Test with a different, but not pleasing outcome: 

 

At first ich checked my Navigation Data Source and it was set to NavDatapro instead of Navigraph:

1.thumb.png.835e77ce92189a3df4b7eed6d9eb9d96.png

 

So I switched it to Navigraph:

2.thumb.png.5661da0efb3fddbce8a29010cf096d46.png

 

I checked the active nav database in the MCDU:

1585682917_Prepar3D2019-09-0315-29-13-17.thumb.png.7bd4572fc4d3a9c9092d3c2c57d54b64.png 

 

I inserted the whole route into in the MCDU and selected the approach for ILS25C with the PSA25S STAR/RNAV transition:

560432301_Prepar3D2019-09-0315-43-59-33.thumb.png.e4d4d35626c82b4614ae1f37e8cc85d4.png

 

I checked the waypoints of PSA25S:

1867726875_Prepar3D2019-09-0315-49-40-00.thumb.png.3b53b8298472413c62805ba30c2c139c.png

843619039_Prepar3D2019-09-0315-50-05-58.thumb.png.f2279c33be97d03275c266181f1b37b9.png

 

For me, the waypoints were OK and I inserted it into the flight plan:

379318151_Prepar3D2019-09-0315-51-33-18.thumb.png.1673b6c73a7ec0691aa257ea2f53288f.png

 

And here the descent and the approach:

1480781001_Prepar3D2019-09-0316-52-22-49.thumb.png.3d9d76a73b84c0a683908e2fb27eedef.png

1334908458_Prepar3D2019-09-0316-54-07-46.thumb.png.500ee2ee82663712eccfa1d4229bbd78.png

75803767_Prepar3D2019-09-0316-57-22-41.thumb.png.75d07532f1d0d57c2f6c3303285ece4f.png

161670685_Prepar3D2019-09-0316-58-03-21.thumb.png.6edaee843ef6dc6fc2cd6028da0a96ff.png

1718004136_Prepar3D2019-09-0316-59-03-30.thumb.png.e90d719463ec39dd05ab0f0481184779.png

 

While passing DF610, the aircraft turned left instead of turning right:

1645032122_Prepar3D2019-09-0317-00-08-51.thumb.png.e88ba1b3c32473fd88bac923111b48a2.png 

465756309_Prepar3D2019-09-0317-00-46-44.thumb.png.24c803782365a614732b33d5f97ac765.png

 

And it performed a full 360 degree left turn around DF610:

1558727575_Prepar3D2019-09-0317-01-30-28.thumb.png.c1b10a7d8e9c59672563037f3a64ae72.png

1175524529_Prepar3D2019-09-0317-02-45-18.thumb.png.973f5c669ed34849446f4fc74362affd.png

414983298_Prepar3D2019-09-0317-03-33-95.thumb.png.6f984f4aa6bb88afcba41ac795b3fa39.png

 

After that it turned right to DF616:

448190723_Prepar3D2019-09-0317-03-49-81.thumb.png.76c1fe81fc3d3ee071b98602d5da1111.png

255524081_Prepar3D2019-09-0317-05-11-49.thumb.png.c4f6fc126f5912fc1852823a6e23612d.png

 

After it passed DF616, it turned right to DF626 as expected:

1525127673_Prepar3D2019-09-0317-08-45-31.thumb.png.81034315edbd7098adc3e1acf46e732c.png

 

But then it made an unexpected right turn:

19203590_Prepar3D2019-09-0317-09-18-28.thumb.png.903a9984c551fd96c8b0a49d365809d8.png

1446916722_Prepar3D2019-09-0317-09-26-79.thumb.png.61dd5ad7faa00f947f0204a37112d63b.png

 

And then a left turn again to DF621:

295731064_Prepar3D2019-09-0317-09-32-24.thumb.png.5332e7fe055963ee25546a840a33855d.png

161941985_Prepar3D2019-09-0317-10-21-25.thumb.png.1571167cd60dc58a001232bac8fca36e.png

1437110638_Prepar3D2019-09-0317-12-59-59.thumb.png.c3735a3b8b6a7b6ee721ee23c7ffbf28.png

3.thumb.png.e05e9aa26500e626b9b58124204bae4a.png

Share this post


Link to post

Thanks for the detailed report. It is being looked at. Do note that issue like this are not unheard of in the real aircraft.

See the image attached... that's a 320 being rather confused. We have got a very nice collection of those

IMG_0522.jpg

  • Like 1

Share this post


Link to post

Note only Airbus, but also Boeings have those problems (beside others ;) )

real nd error 737.jpg

  • Like 1

Share this post


Link to post
3 hours ago, Sierra Charlie Mike said:

Wow! Thank you Mathjis. I did not know that the real Airbus has issues like that. 

 

Yeah, not just Airbus either, but Boeing and other aircraft.  It's sometimes not perfect in the sim or in real life, and when this occurs it is resolved by using the Direct To function or just using the heading mode.

 

2 hours ago, Sierra Charlie Mike said:

🙂 I guess calculating the expected or planned flight path in real time, is a very complicated task.

 

It is VERY complex code!  The Beta Team and Devs have been looking and talking about for the past 24 hours and we wanted to be sure we all understood the issue, especially since we found the second issue while looking at this. 

 

We can't give you an update on when this will be resolved, but we're actively pursuing it and will have it resolved in one of the future updates.

 

Many thanks for pointing this out to us my friend!

 

Best wishes!

 

  • Like 1

Share this post


Link to post
vor 18 Stunden , DaveCT2003 sagte:

It is VERY complex code!  The Beta Team and Devs have been looking and talking about for the past 24 hours and we wanted to be sure we all understood the issue, especially since we found the second issue while looking at this. 

 

I'm a software developer myself and know those situations of reproducing, locating and fixing bugs. Especially when they occur in a production system ;)

 

vor 18 Stunden , DaveCT2003 sagte:

We can't give you an update on when this will be resolved, but we're actively pursuing it and will have it resolved in one of the future updates.

 

Yes, ok. I'm able to use the DIR-function or select a heading to fly around it. I have a gut feeling that I made a mistake or have an error in my setup ... if I solve the problem I will send you a message.

 

vor 18 Stunden , DaveCT2003 sagte:

Many thanks for pointing this out to us my friend!

 

You're welcome!

 

 

Best wishes,

Stefan

  • Like 1

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...