Posts: 5 | Location: USA

Hi,

I started a thread earlier this year about a CTD on approach; which I then left and never returned to (so sorry!!). I just experienced another CTD on approach to runway 30R. After some experimentation I found that the CTD's on approach only happen when you intercept the glideslope. You can set up the approach, intercept the localiser, but as soon as you intercept the glideslope it crashes. This is the windows event viewer log:

It seems that the VCRUNTIME is the problem, however I know that my runtime is up to date. This error and CTD only happen on ILS approach to OMDB. I tried to do a STAR and then visual approach and that worked perfectly. So I'm guessing there's an issue with the ILS. Thanks for your help! I'll definitely check this thread this time.

Site Admin |&nbspPosts: 4842 | Location: Tampa/FL

I haven't been able to replicate this crash here. If you do have the ability to do so, have you tried loading our OMDB afcad in ADE, deleting that ILS, recompiling to see if the crashing stop? I wonder because I have never really heard of crashes because navaids in Afcads.

Posts: 5 | Location: USA

I know it's been a while since I've been on this thread, but I'm going to work on this sometime this week (maybe the weekend). I'm a HS band director so my life got crazy after I posted this topic. I'll try to find time this week to work the problem.

Posts: 1

Just as an extra bit of information, I also experienced the same dll crash the last flight I made into Dubai.

I was flying the IMPED 3E approach, and I had a crash pretty much 10 miles out from the airport (I had a 10 mile range circle set up on the ND).However, as I was coming in from the south and overflying the airport to land from the north, I wasn't on the ILS.

I'm wondering whether it might be something that gets loaded when we're 10 miles out rather than an ILS issue? Typically, if you're at 3000ft, you owuld intercept the glide at about 10 miles out.

Posts: 5 | Location: USA

So I did a lot of testing today and experienced a weird phenomenon; not one CTD. I wanted to see if I could reproduce the issue like I was able to when I first created this topic. I would start the plane out far enough that the airport and scenery would not be loaded (about 30 miles), then set the plane up for the approach, and then run the testing. I tested the issue tonight with many different variables:

Visual approach with ILS programmed into the FMC/VNAV (Runways 30L and R):-With the PMDG 747-8F and -8i, and PMDG 747-400F (the -400F was the aircraft I used to test when I first posted this topic)-During the day and at night-GSX Enabled and Disabled

ILS tests (Runways 30L and R): -With PMDG 747-8F and -8i, and PMDG 747-400F-During the day and at night-With full autoland and with hand-flying the ILS-GSX Enable and Disabled

-The last test that I will run will be a fully loaded long haul flight from KSDF with vpilot, virtual airline's ACARS, Active Sky, and head-tracking. This will take place next weekend.

I was able to land and taxi off the runway towards the gates in every test with no issues whatsoever. I'm not sure why I can't reproduce the problem like I could before, but I'm guessing it's a good sign. I'm starting to think it has something to do with GSX, as I've been reading that GSX has been causing a lot of strange CTD's. I downloaded the update for GSX and now I don't have problems with CTD at Dubai. Now that's not necessarily the reason it seems fixed, but I know GSX reinstalls or repairs the windows runtime so that might have something to do with it.

Again, not sure why it's working for me now. I was able to reproduce the crash every time with the ILS approach for either runway, day or night back in August. Maybe try to update your GSX if you have it, and if you don't maybe try to update your windows runtime. Would love to hear your guys' thoughts.

Posts: 2

Same problem happened to my right now ... CTD on ILS 30R about 10 nm before the rwy.This is on P3D4.3 with the PMDG 737NGX.My GSX is up-to date. I have no idea what to update to avoid this very annoying CTD.