CTD in P3D v4.4 over Hudson Bay.

[virtuali]

As I've said in my previous post:

- If you have P3D4, please try with the updated Addon Manager .DLL posted before.

- If you have FSX, you must wait for the official update, since we cannot release the 32 bit fix separately from the rest of the update, which is not ready for release yet.

[m007j]

Thought I would check in here, as I'd posted over at the P3D forums as well: The updated bglmanx.dll file upthread works like a charm for me. I've now tested it with the PMDG 777 and 747 on V4.3 and V4.4 across all of the waypoints just off Labrador where I was getting the crash (from GRIBS to PELTU) and I have not gotten a single crash with that updated FSDT file, even with flights approaching 13-15 hours from the ME.

[downscc]

Since installing the beta module, I have not had the problem occur after many sessions that spanned the Greenland - Hudson Bay region and no problems either crossing Western China.

I played with the problem over S Hudson Bay as I had a P3Dv4.4 scenario that would reliably run into the CTD event.  The events would all happen within a 200 nm region but never in the exact same place.  If I ran the scenario and stopped to save it before entering the 'crash zone' and then restart P3D and load that second scenario closer to the region there would be no CTD event.  I have ran bgl2xml decompiler on all APX and NVX files in the 0301 region and have not found a data error.  I conclude it is the P3D facilities.dll with a code bug that is triggered only when there are few facilities (remote area such as Hudson Bay or W China) and it is only triggered when the session exceeds an hour or more.  It looks like a code bug rather than a data error to me.

I look forward to you announcing an update package that includes this revised dll module.

[smiley]

Yep I can report the same. Have done 4 flights from England into North america and Canada and for the first time in a very long time no CTD. I too look forward to the full update.

[kityatyi]

I have been doing a transatlantic from EDDF to CYYZ and have just crashed off the Canadian coast roughly at the waypoint CUDDY, 5 hours into the flight. It was my first CTD in a very long time and it's very frustrating. I have started to dig into it and ended up in this thread. I am going to give the attached file a try, hoping it will help.

[DaveCT2003]

Umberto, is the new file (to prevent CTDs around Canadian airspace) included via the FSDT Update Tool?  Or do we have to added it manually?

Many thanks.

[airbadger]

Umberto, is the new file (to prevent CTDs around Canadian airspace) included via the FSDT Update Tool?  Or do we have to added it manually?

Many thanks.

You have to download it from his link in this thread.

[headley]

... until we'll release it officially, which will come with a fairly large update that will be out in the next weeks.

Any news about this update?
I was away from flightsim for a couple of weeks, so not sure if it was released already ?

[airbadger]

I've done 3 east-to-west Atlantic crossings and haven't had a CTD since using the beta .dll.

[virtuali]

I've done 3 east-to-west Atlantic crossings and haven't had a CTD since using the beta .dll.

That's good news, and other feedback seems to confirm it. But until the next update is officially out ( and there will be a Live Update notification for it ), it will still have to be downloaded from the forum link, because we are still not ready with the update.

[headley]

... because we are still not ready with the update.

Thank you for the headsup.
Waiting patiently.

[ahuimanu]

Here to confirm that this updated bglmanx.dll does fix the problem for me as well.  I am grateful as this problem was very annoying.

[CaptKornDog]

3/3 east to west successful flights so far.  I'm starting to become cautiously optimistic.

[kityatyi]

Crashed this morning on a flight from ZSPD to EDDF. Takeoff was at 01:41am and crash occured at 07:47am, about 6 hours into the flight. The captain (that would be myself, hmmm) was on his crew rest, but recovering the flight data, the flight plan and ETO predictions of the OFP I can determine that the aircraft crashed between the waypoint of LITUN and ADMUR over northern Russia. Before flying this route overnight, I did the first leg from EDDF to ZSPD during the day without issues.

https://i.imgur.com/qEQlC8L.jpg

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: ntdll.dll, version: 10.0.17134.556, time stamp: 0x74bed8b0
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0xb5c
Faulting application start time: 0x01d4dd1d76a45b61
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: dddc8e7d-244d-43f3-83be-928f36a280ec
Faulting package full name:
Faulting package-relative application ID:

[virtuali]

Crashed this morning on a flight from ZSPD to EDDF.

Without saying if you use the updated .DLL posted in this thread, the report is not very useful. If you are, chances are the crash is caused by something else, since right now, 100% of users that used the updated bglmanx.dll file, reported no crash.