CTD when I am selecting airways

[JughedJones 197]

Hey everyone. 

 

I just updated to the latest version and I've noticed a problem, wondering if anybody else has had this. 

 

I was getting a flight ready from KSEA to KBOI and when selecting an airway in the FMS I got booted to desktop. 

 

Thinking this was a random occurrence, I tried it again. Same thing happened. I noticed that it was when I tried to go to the 9th page of airways each time.  

 

I'll try a different flight and see if it goes better, but I wanted to see if this was a known issue.

 

Brian 

[JughedJones 197]

Nothing?

 

Not even a view huh?  Either that means it's a ridiculously common problem or.. I'm not sure..,

 

[Jazzfan 57]

Hi Jughed,

I haven't seen/heard of this problem before? Could you post your exact route, so I can give it a try?

regards, Craig.

[JughedJones 197]

Sure Craig, sorry for the delay, it was from KSEA to KBOI

 

KSEA SID BKE V4 HOVEL V444 PAYET V4 EMETT V444 NICPE DCT KBOI

 

Using FS2crew with the new updates. 

 

Thanks!

 

 

 

 

 

[calebrw 9]

Okay, I just had a CTD (I've never had one before w/ the Majestic Q400) while trying to recreate what you did.

 

Here is what I did:

1. Load FSX (SP2)
2. Load Q400 at KSEA (default runway, clear weather, etc.)
3. Start FMS and wait for check, which is fine.
4. Click FPL and enter KSEA in space 1, BKE in space 2 and click LIST.
5. I was able to enter the V4 airway.
6. I was looking for HOVEL by clicking NEXT and after about the 4th or 5th page, I got a CTD.

Looks like a contact to Majestic is in order: http://majesticsoftware.com/mjc8q400/support.html

 

Best,

 

 - Caleb

[Jazzfan 57]

Hi Jughed,

I tested this last night, following the same steps as calebrw, with the same result. Using the stock navdata, scrolling to page 9 of the airways list, crashes the sim. I'm going to try it again with the updated navdata. Will post the results here.

regards, Craig

[Jazzfan 57]

   After updating the navdata, the airways list page 9 still causes a crash. I tested some of the other 'list' functions, (vor, ndb, intersection, airports) and I was able to scroll through all of those (up to 15) pages without one crash.

 

   regards, Craig.

[pete_auau 1,152]

Ok  same  here  got to page  8  went  to try to get to page 9 ctd, 

[spesimen 135]

i think there is something odd going on with the airway stuff, i haven't had a crash but i have noticed on a few occasions that the waypoints it lists for the airways are incorrect. there are several random waypoints sprinkled in the list with the real ones. adding them to the flightplan usually resulted in just the correct points being added, so i think it's some issue with the page that displays them while you select, which maybe is related to what you are seeing somehow..

 

regards

-andy crosby

[calebrw 9]

Did anyone report this to Majestic yet?

[crosswind 825]

Brian,

 

I am just checking in on this.....and was able to confirm the CTD using the default DB.  Will look into this and see what the culprit may be.

Thanks

[wolke85 150]

Default DB ...? - is this the data which is delivered with the A/C so to speak?

And if so: Does this CTD also appear to happen when using the latest Navigraph data for instance?

[Jazzfan 57]

I have used both the default nav database and airac 0414, using q400 v10083, and v1009, with the same result. I'm led to believe it isn't the nav data per se.

Majestic will sort it out, rather quickly, I would think.

    On the topic of bugs, has anyone encountered the 'Elevator Asymmetry' caution panel light?

regards, Craig

Edited May 19, 2014 by Jazzfan

[wolke85 150]

I have used both the default nav database and airac 0414, using q400 v10083, and v1009, with the same result. I'm led to believe it isn't the nav data per se.

Majestic will sort it out, rather quickly, I would think.

    On the topic of bugs, has anyone encountered the 'Elevator Asymmetry' caution panel light?

regards, Craig

 

Thank You very much for Your reply Craig!

Well then let's see what Majestioc will come up with regarding the "DB-crash-issue".

Cheers, Christoph