P3D v4.2

Maddog version 103

FS2Crew enabled.

In the FMC when you select the SID (In this case KDFW - AKUNA6) the sim freezes and eventually get the message that the sim has to close.  You can select the runway but not the SID.

 

Anyone else have this problem?

Yes and just submitted a ticket on this.

Mark,

We have seen this during Beta Testing, but thus far have not been able to identify the cause.  I've personally experienced this 3 or 4 times, then rebooted the sim and entered ALL the information in the same way and not had a problem, then gone back and done it several more times and still didn't have the problem.

Rest assured that we're still trying to find it, but since it can't be duplicated each time it's going to be tough.  Note:  There are other aircraft which have the same issue. Thankfully none of these issues happen very regularly.

By all means let us know about them though, and the more detailed information is very useful.

Thanks again!

 

Edited February 25, 20188 yr by DaveCT2003

So far, I've reproduced this CTD by trying to select a SID before selecting a departure runway. If I select a runway first, no CTD.

Submitted a ticket on this but haven't gotten a confirmation email as yet.

Can you give the airport and departure, as well as the Route? Also which AIRAC?

1 hour ago, DaveCT2003 said:

Can you give the airport and departure, as well as the Route? Also which AIRAC?

Remember I was talking about this right before release?  It's something new I think.  I wasn't getting any CTDs out of it (I guess my sim is better than yours ) but I was getting really odd behaviors.  I posted a video of it in a bug report I think.  I'd say for now to be safe SID and STAR select the runway entry first.

5 hours ago, DaveCT2003 said:

Can you give the airport and departure, as well as the Route? Also which AIRAC?

AIRAC is 1802, and airport departure is KBOS BLZZR4. Route is PATSS NELIE KEWR

5 hours ago, RudiJG1 said:

AIRAC is 1802, and airport departure is KBOS BLZZR4. Route is PATSS NELIE KEWR

Do you recall which Runway you were using?

1 minute ago, DaveCT2003 said:

Do you recall which Runway you were using?

I believe it was 04R, Dave

10 hours ago, thibodba57 said:

Remember I was talking about this right before release?  It's something new I think.  I wasn't getting any CTDs out of it (I guess my sim is better than yours ) but I was getting really odd behaviors.  I posted a video of it in a bug report I think.  I'd say for now to be safe SID and STAR select the runway entry first.

Yeah, I had two bug reports for this, the first going back to Week #2.  Soratic.

It's certainly not the typical NavData/CDU causing a Zero Sum Error (that would have been easy to fix!).  In fact, now I'm thinking it's not the NavData/CDU at all.  I have a few theories, I'll share them with Davide and the team.

Thanks for chiming in brother!

 

1 minute ago, RudiJG1 said:

I believe it was 04R, Dave

Thanks my friend.

 

By the way, just some background... I don't believe 04R is a normal departure runway at Boston. In fact, I'm as sure of this as I can be without checking the charts.

Not that you can't use it... just providing some background info.

 

Okay, two of us tested this at different Runways. No CTD for either of us, but we did find a Bug.  Can you spot it in the video linked below?  This helps us to narrow down what is going on with the intermittent FMS/CDU related CTDs - which aren't repeatable if you reload the sim.

Anyway, thanks for providing the info, we're working it!

VIDEO LINK: https://www.dropbox.com/s/6h4fisxp6hofi8c/KBOS Test Video.mov?dl=0

 

 

1 hour ago, DaveCT2003 said:

Okay, two of us tested this at different Runways. No CTD for either of us, but we did find a Bug.  Can you spot it in the video linked below?  This helps us to narrow down what is going on with the intermittent FMS/CDU related CTDs - which aren't repeatable if you reload the sim.

Anyway, thanks for providing the info, we're working it!

That was actually the bug I reported in my video, its a vicous loop if you don't select the runway first. I want to say it was even worse if you executed it like you did the second time without rectifying the issue.

36 minutes ago, thibodba57 said:

That was actually the bug I reported in my video, its a vicous loop if you don't select the runway first. I want to say it was even worse if you executed it like you did the second time without rectifying the issue.

Roger that!  Works fine for the other runways, so looks like it's a NavData Issue.  When I get a chance, I'll open it up and look for an error.

The CTD I think is not related to the bug in the video.  I'm sneaking up on a theory for that one.