Board index » FlyTampa » FlyTampa-Dubai-Rebooted

Post
 acamp04 (Fri Jul 27, 2018 11:18 am)

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:

Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263
Faulting module name: VCRUNTIME140.dll, version: 14.11.25506.0, time stamp: 0x5967d7ce
Exception code: 0xc0000005
Fault offset: 0x000000000000c819
Faulting process id: 0x1efc
Faulting application start time: 0x01d4254b561d4336
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 690bb1eb-c6d2-4c77-aa65-a40bb4638361
Faulting package full name:
Faulting package-relative application ID:

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.
Post
 martin[flytampa] (Thu Aug 02, 2018 12:18 am)

Site Admin | Posts: 5201 | 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.
Post
 acamp04 (Sun Aug 05, 2018 11:32 pm)

Posts: 5 | Location: USA
I will try this and report back.
Post
 christinney (Sun Aug 12, 2018 9:12 am)

Posts: 2
Please let us know acamp04 if you do solve this. Ive had this problem ever since moving mover to P3D v4, and like you its always on the ILS approach. Not used Dubai in over 4 months because of this.

Only happens on this Fly tampa product which is strange!

Likewise if I come across anything that sorts it ill let you know

Regards

Chris
Post
 acamp04 (Mon Sep 24, 2018 3:20 pm)

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.
Post
 philbrown (Mon Sep 24, 2018 3:39 pm)

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.
Post
 acamp04 (Sun Sep 30, 2018 9:44 pm)

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.