43 minutes ago, exeodus said:

Were you flying at normal sim rate when the crash happened?  It only crashed for me when I was using a 4x sim rate.

No mine was accelerated to 8x. Will try normal rate. 

This is getting a bit ridiculous now. How come LM is unable to solve such a basic glitch? This is the busiest intercontinental route in the entire world and most of the time active NATs pass right above the doomed territory. 

Has this been reported to them?

1 hour ago, regis9 said:

Has this been reported to them?

Yeah someone said earlier in this thread they’ve reported the issue in LM forums only to get banned by a moderator. That’s how they solve the issue - shooting the messenger. 

I guess it depends on *how* they raised it.

2 hours ago, regis9 said:

I guess it depends on *how* they raised it.

Well then why don’t you go ahead and raise it the right way see if you can get it sorted by 4.3. 

May I suggest that those with this problem work together to define the problem.  Come up with a method to be able to reliably create the event.  You have to be mindful of the fact that those with this problem are in a minority of users, which does not mean it doesn't exist but simply you need the evidence not required if the entire user base experienced the problem.

1 hour ago, downscc said:

May I suggest that those with this problem work together to define the problem.  Come up with a method to be able to reliably create the event.  You have to be mindful of the fact that those with this problem are in a minority of users, which does not mean it doesn't exist but simply you need the evidence not required if the entire user base experienced the problem.

...that’s exactly what most users in this thread are trying to do... they’re sharing routes, add-ons, settings, etc. I appreciate you’re trying to help, but your post is coming off as patronizing and people who drop in to issue threads just to let us know that they aren’t experiencing a bug aren’t terribly helpful. 

2 hours ago, downscc said:

May I suggest that those with this problem work together to define the problem.  Come up with a method to be able to reliably create the event.  You have to be mindful of the fact that those with this problem are in a minority of users, which does not mean it doesn't exist but simply you need the evidence not required if the entire user base experienced the problem.

We can all do without this type of thinly veiled scorn. Keep your suggestions to yourself please. 

Same issue encountered today. Was flying LHR-PHL on Vatsim, and the sim randomly crashed just south of Nova Scotia. Last lat long before it crashed was 51.46915 -0.48229.

https://vatstats.net/flights/7000819

I wonder if it has to do with the sim loading Open LC NA for the first time after just loading ocean textures. I think it also might be because of an FSX AFCAD that I have installed in the New York area.... doubt it though. I have deleted this scenery and recompiled my scenery library so ORBX products are below third part airports. Will try again tomorrow. I am running P3D 4.2 and have completed flights before this in other parts of the world with no issues. There were no AI aircraft loaded in at the time of crash, and no other instensive programs being run. At the time I was working on a school essay in Microsoft word with no other non flight sim addons running.

When checking event viewer, the only thing that crashed is ntd.dll... which doesn't explain a lot. 

3 hours ago, Aviationsim4862 said:

Same issue encountered today. Was flying LHR-PHL on Vatsim, and the sim randomly crashed just south of Nova Scotia. Last lat long before it crashed was 51.46915 -0.48229.

https://vatstats.net/flights/7000819

I wonder if it has to do with the sim loading Open LC NA for the first time after just loading ocean textures. I think it also might be because of an FSX AFCAD that I have installed in the New York area.... doubt it though. I have deleted this scenery and recompiled my scenery library so ORBX products are below third part airports. Will try again tomorrow. I am running P3D 4.2 and have completed flights before this in other parts of the world with no issues. There were no AI aircraft loaded in at the time of crash, and no other instensive programs being run. At the time I was working on a school essay in Microsoft word with no other non flight sim addons running.

When checking event viewer, the only thing that crashed is ntd.dll... which doesn't explain a lot. 

It’s most probably the unusual time zone in that area. The sim would still crash crossing the pacific towards the NA if it was anything to do with OpenLC textures, but it doesn’t. 

On 2/19/2018 at 6:26 PM, Bardia said:

We can all do without this type of thinly veiled scorn. Keep your suggestions to yourself please. 

You are being too sensitive.  What Dan has suggested is exactly the logical thing to do if you want LM to address the issue - especially if only a few are experiencing the problem - as annoying as it is.

Can anyone with better skills than I plot the rough border of where people are getting these at on a map? Probably would need to call through these posts and maybe a Google search using "CTD Canada fsx" and "CTD Canada P3D". NTDLL error associated with this is very very likely a memory management corruption issue which could be tied to the time zone theory. 

I am not a P3D user yet and I have been following this thread with interest.

I cannot test and this is all conjecture on my part. This part of the world, assuming that P3D has the correct time zones in place, is unique. According to timeanddate.com, Nuuk is a half hour ahead of Newfoundland & Labrador. Newfoundland & Labrador is a half hour ahead of Atlantic Canada. Atlantic Canada is an hour ahead of Eastern US. 

Correct me if I’m wrong, but half hour time zone changes are not the norm in the world. I believe the only other part of the world that this occurs is in North Korea which is relatively new. Not sure if P3D has that implemented.

In the Southern Pacific there are some strange time zones as well. Tonga vs. The Chatham Islands. That appears to be a 45 minute time zone change.

If it is a time zone thing, then maybe a test flight between North and South Korea would help isolate that, unless P3D doesn’t incorporate the time change between the two Koreas. Maybe a test flight South Pacific might further isolate this. 

There are quite a few half hour time zones between Greenland and Canada so this is why I chimed in on this.

Like I said, all conjecture on my part, take it for what it is worth.

19 minutes ago, Groovy_Kincaid said:

I am not a P3D user yet and I have been following this thread with interest.

I cannot test and this is all conjecture on my part. This part of the world, assuming that P3D has the correct time zones in place, is unique. According to timeanddate.com, Nuuk is a half hour ahead of Newfoundland & Labrador. Newfoundland & Labrador is a half hour ahead of Atlantic Canada. Atlantic Canada is an hour ahead of Eastern US. 

Correct me if I’m wrong, but half hour time zone changes are not the norm in the world. I believe the only other part of the world that this occurs is in North Korea which is relatively new. Not sure if P3D has that implemented.

In the Southern Pacific there are some strange time zones as well. Tonga vs. The Chatham Islands. That appears to be a 45 minute time zone change.

If it is a time zone thing, then maybe a test flight between North and South Korea would help isolate that, unless P3D doesn’t incorporate the time change between the two Koreas. Maybe a test flight South Pacific might further isolate this. 

There are quite a few half hour time zones between Greenland and Canada so this is why I chimed in on this.

Like I said, all conjecture on my part, take it for what it is worth.

Time zone crash should be the least of anyone's worries when flying into North Korea!

 

Joking aside, P3D does not have correct time zones, even after the fixes delivered by 4.2, so there is no way of reliably testing this theory in the parts of the world where the real-life time zones are similarly anomalous. 

 

I was going to fly the problematic route sans time compression but haven't had the chance so far. Will report back when done.