Blackbird Sims / Milviz Forum Archive

KA 350i version 1.2.0 in P3Dv5HF1 -- I am getting a lockup with the faulting module being reported as proline2.dll.

Is it possible that this is some problem with navigraph data that the dll isn't handling?

I flew all over the U.S. with no problem (many flights, many legs etc), but now I've flown down into Mexico and encountered a crash that I can reproduce...flying from MMCT to MMUN, I didn't even get off the ground, but I had entered the data into the FMS. I did this a couple of times to see if it repeated, and it did. I also had a crash with MMMD to MMCT, but it crashed in-flight one time, and on the tarmac another time.

Would event viewer logs or similar help you pinpoint this? Or is it something that may go away with the next navigraph cycle?

I just thought of one thing. MMCT and MMUN are close together...and I didn't have any waypoint at all between the two. Is it possible that the FMC wants a waypoint somewhere in there?

I'll have to fly that again and test with a waypoint inserted.

It is possible that there is some issue with navigraph data that causes it to crash at that specific area. Does it crash if you try anything else in Mexico or just this specific airport?

Slayer wrote: ↑

Mon Jan 11, 2021 11:58 am

It is possible that there is some issue with navigraph data that causes it to crash at that specific area. Does it crash if you try anything else in Mexico or just this specific airport?

I'll try some other flights in Mexico and somewhere else, and see.

I did re-fly the MMCT to MMUN flight with one (1) waypoint in between, and it worked perfectly. I have heard of other FMC's not liking "direct" flight plans (plans with no waypoints) so maybe it was that. I'll know eventually because I'll fly some routes like that.

I love your King Air. Great job. Tell all the programmers and graphic artists that for me.

Thank you for the kind words. Let me know if you have any more troubles. Thanks.

FYI -- I decided to try a short flight in the USA to see if I could reproduce this lockup there.

I flew KCGI to KJEF without a waypoint in-between -- and it locked.

Next, I re-flew KCGI to KJEF but this time I inserted FAM (a vor) as a waypoint, and it worked great.

So, it seems it's not handling routes without an intervening waypoint. No problem, I will simply remember to have at least one waypoint between the departure and destination airports.

Yes, that is correct. You must have at least one waypoint between airports