https://www.avsim.com/forums/topic/526743-p3d-41-ctd-near-labrador/

I've read a bit on this thread and I'd like to inform whoever is trying to study this problem that the crashing isn't confined to westbound transatlantic flights neither is it bound by time. I've managed to get it both in the middle of Russia, near Vorkuta and near the international date line. Sometimes within one hour of each other. I've posted a thread on the P3D support forums so feel free to pitch in and help us all find the culprit with this issue.

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=130298

Cheers o/

Edited July 19, 20187 yr by Ioan92

Your post mentions P3D 4.1.  Have you considered installing the 4.3 update?  I can get a crash also if I do not launch P3D on a fresh boot, especially if I have previously run any graphics intensive sims like Xplane11, or No Limits Coaster 2.  That is where I would start, 4.3 update, clean boot, then fly.  If I factor in the approx 100 hours I've spent on P3D, give or take I have had maybe a handful of random crashes, not enough to disturb me, and always invoked if I've run another app just before running P3D.  I am on P3D 4.3, and it has not crashed once, except for what I am about to post, which will make simmers laugh at my foolishness.

John

5 minutes ago, Cactus521 said:

Your post mentions P3D 4.1.  Have you considered installing the 4.3 update?  I can get a crash also if I do not launch P3D on a fresh boot, especially if I have previously run any graphics intensive sims like Xplane11, or No Limits Coaster 2.  That is where I would start, 4.3 update, clean boot, then fly.  If I factor in the approx 100 hours I've spent on P3D, give or take I have had maybe a handful of random crashes, not enough to disturb me, and always invoked if I've run another app just before running P3D.  I am on P3D 4.3, and it has not crashed once, except for what I am about to post, which will make simmers laugh at my foolishness.

John

The original post refers to 4.1 but I assure you the issue was present in 4.2 and still is alive and kicking into 4.3.

Should update the thread title to avoid further confusion.

I'm wondering if you've taken note of both the local and UTC time when these crashes occur.  Is it near midnight either local or UTC in the local timezone or in the timezone you're crossing into?  IOW, would crossing into the next timezone result in changing the date in local or UTC time (forward or backward)?

Regards

 

5 minutes ago, w6kd said:

I'm wondering if you've taken note of both the local and UTC time when these crashes occur.  Is it near midnight either local or UTC in the local timezone or in the timezone you're crossing into?  IOW, would crossing into the next timezone result in changing the date in local or UTC time (forward or backward)?

Regards

 

Every single time I've gotten this error I've been caught with my pants down while I was away in the house, so I cannot provide this information. All I can vouch for is that the crash only occurs on westbound flights at some vaguely defined locations above russian airspace. The catch is that I've yet to fly a westerly transatlantic in P3D yet but I am ready to bet I will get the same ctd/ stackhash near labrador. I will try the restarting GSX tip in the old thread to see if it changes anything. Oddly enough, while GSX was bugged and you had to restart it to finish baggage loading I don't recall getting faults but this may be a long shot, as I didn't restart GSX on IAD-NRT which is a 14 hr flight that went flawlessly.

Something is probably messed up in the base scenery.

One thing to suggest is fly this area in accelerated sim speed and then down to normal speed.  All fly all sorts of planes in these area by variety of users.  The more CTD found will help nail this bug....

I mean all sorts of flights - simple, complex planes etc.

Again just a suggestion....anyway my break is over, back to work

I wonder if there's some sort of flight logger that could be used to track a flight and log some metrics so that place/time at least would be known.  Something that runs outside P3D, using FSUIPC to gather data for example, would be ideal, as it wouldn't crash with the sim.

Regards

 

53 minutes ago, w6kd said:

I wonder if there's some sort of flight logger that could be used to track a flight and log some metrics so that place/time at least would be known.  Something that runs outside P3D, using FSUIPC to gather data for example, would be ideal, as it wouldn't crash with the sim.

Regards

 

Good idea Bob..., FSUIPC has a useful logger that I used a while back to trap VAS leakage (glad those days are gone).  It should be easy to set it up to sample every minute providing the lat/lon and then later add other parameters as desired.  The file gets big if you sample too often, but that shouldn't be a problem for most users.

The only potential issue with using FSUIPC's logger is that it is a DLL, so it dies with the sim in a crash, so the most useful recent data might be lost.

Another thought comes to mind as I ponder this (I've never actuially seen this problem here since I generally use QuantumLeap to beam myself ahead to somewhere close to the TOD): it seems these incidents are happening at high lattitudes--another potential issue might be something unhappy in the magnetic <-> true conversion math in locations close to the magnetic pole(s).

Regards

 

Just now, w6kd said:

The only potential issue with using FSUIPC's logger is that it is a DLL, so it dies with the sim in a crash, so the most useful recent data might be lost.

Another thought comes to mind as I ponder this (I've never actuially seen this problem here since I generally use QuantumLeap to beam myself ahead to somewhere close to the TOD): it seems these incidents are happening at high lattitudes--another potential issue might be something unhappy in the magnetic <-> true conversion math in locations close to the magnetic pole(s).

Regards

 

I think my ACARS program has a page showing present coordinates, I was however never inspired to take note of the last position it records. Next time it crashes I will take note and paste the location here.

In  "Modules\FSUIPC Documents\Example LUA plugins"  there is a lua that will log what's needed up until the time of crash -- "record to csv.lua"
Would advise not to run it until close to the point of the known trouble area.

 

 

I think the data that initially needs logged includes: position (lat/long), heading (true and mag), time (UTC and local), date (UTC and local), altitude, COM1/COM2 freq, wind (dir/speed), and outside air temp.

 

1 hour ago, w6kd said:

it is a DLL, so it dies with the sim in a crash, so the most useful recent data might be lost.

True, but it is writing the log file as the session progresses, it is not buffering so at the most you lose the last second or sample point.  It is easy to use which is why I thought of it, being lazy.

I use IFPro to ascertain the root causes of CTDs and problem addons.

ive always thought it was something to do with tijmezones