FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Neume on December 23, 2018, 10:04:08 pm
-
I am having the exact same issue as downscc in this post from April: http://www.fsdreamteam.com/forum/index.php/topic,17615.0/prev_next,prev.html#new when flying from EGLL to KSFO.
This time though, it is an ntdll.dll crash. Here is the exact position where the simulator crashed: https://i.imgur.com/B8EARM4.png
(I am the blue aircraft)
PMDG 747
GSX
FTX Global
Flightbeam KSFO
-
Could you please try this test version of the Addon Manager .DLL and see if you notice any improvements flying that area ?
http://betaupdate.fsdreamteam.com/setup/fsdtroot/bglmanx64.dll
-
I tried and I had no CTD near Newfoundland but an api.dll crash (which is new to me) during descent to JFK.
I have no idea if it's related but thought better to report. Pics attached.
Chris
-
I tried and I had no CTD near Newfoundland but an api.dll crash (which is new to me) during descent to JFK.
API.DLL crash doesn't have anything to do with this issue, and since you were flying over 10K feet, it's not possible that can have anything to do with any of our software, since now *both* GSX and the Addon Manager are not doing anything above that altitude.
API.DLL crash can be any software that use Simconnect so, basically, can be anything, while the other crash over Newfoundland/Canada was an NTDLL.DLL crash, which was caused BY THE SIM ITSELF, which crashed when accessed some data from the facilities which lead to likely corrupted navigation data in the default scenery.
It was TRIGGERED by both GSX+Addon Manager, but that doesn't obviously mean it was our fault: we only asked the sim a list of nearby airports and navigation data and, because something in that areas has an issue that, when *somebody* ask for navigation data in that area, the sim will crash BY ITSELF when accessing it.
So, we just changed the software to stop asking for any data while cruising, which should fix most of the problems.
-
Could you please try this test version of the Addon Manager .DLL and see if you notice any improvements flying that area ?
http://betaupdate.fsdreamteam.com/setup/fsdtroot/bglmanx64.dll
Hi Umberto,
Did you have more feedback concerning this new dll?
If i install the new dll, will it be replaced by the old one after running the liveupdate?
-
I've flown from Iceland to Nantucket, through Greenland and Terranova, using the new dll. No crash.
-
Well that's good news then :)
-
Could you please try this test version of the Addon Manager .DLL and see if you notice any improvements flying that area ?
http://betaupdate.fsdreamteam.com/setup/fsdtroot/bglmanx64.dll
Hi Umberto,
Did you have more feedback concerning this new dll?
If i install the new dll, will it be replaced by the old one after running the liveupdate?
Well, i have just started liveupdate and it seems that the newer bglmanx64.dll (version 4.5.0.14) was replaced by the older (original) version 4.5.0.13 ???
-
Well, i have just started liveupdate and it seems that the newer bglmanx64.dll (version 4.5.0.14) was replaced by the older (original) version 4.5.0.13 ???
Of course, we haven't published it officially, that's why there's a forum download link, so you must download it again and overwrite it, until we'll release it officially, which will come with a fairly large update that will be out in the next weeks.
-
Fairly large update that will be out in the next weeks.
I like the sound of that. ;D
-
Umberto, could you also provide a 32 bit version? While this seems to have fixed P3Dv4, I still get this crash on v3.
Perhaps the crash comes from bglman trying to look at data that does not yet exist in memory. As you come in from the Atlantic, I imagine the vector (or whatever) of facility objects is empty. The unusual thing about Canadian airports is many of them are missing basic features, like parking positions, taxiway nodes and paths, and runway paths. This isn't corrupt data - it's just not there because these airports are sparse in real life too. Perhaps the first (and initially only) airport that is loaded into the vector of airport objects is missing something (let's say parking positions), and as you try and loop through the entire population of parking positions (which you assume must exist because, hey, there's at least one airport in the object vector and surely all airports have parking positions), the program crashes, because there are no parking positions and the index for the loop is automatically out of range.
This sort of scenario would fit with the observation that the crash doesn't happen when flying the other way. The size of the population of parking positions (or whatever) is not zero, because other airports with parking spots are already loaded into the vector.
Bryn
-
I'll try that new DLL file. Hopefully all goes well.
Thanks a lot for the help.
Luke
-
Perhaps the crash comes from bglman trying to look at data that does not yet exist in memory.
The Addon Manager is not trying to do anything of that sort, like trying to decide how or when to look at that data.
It uses a simulator API request, and will ask the sim to get that data by ITSELF and, it's has been already proven it's the sim that crashes ITSELF on facilities.dll so, it's clearly a problem of the data or, quite simply, a simulator bug that has always been there, but nobody found it so far, because nobody else uses that API, which is a faster version of Simconnect, so it's not very popular, and most of 3rd party airplanes have their own internal database so, while we eliminate this way the need to keep a separate database and we don't have the issue to keep it synchronized with the simulator data, we might be exposed to possible bugs with it.
But as you said yourself, the problem is fixed in 64 bit, because we sidestepped it, by stopping any request while cruising. Unfortunately, I cannot post a 32 bit version of the updated .DLL, because we are in the middle of other updates, so they must all published together, because the current version I'm working with is not compatible with the released version so, I'm afraid you must wait for the official next update to get the new 32 bit version.
Also, you must understand that, sooner or later we'll drop support for 32 bit entirely, because it's hampering both our productivity and the reliability of anything new we put out. The next big update, for example, will cover almost exclusively P3D4.4-specific features and, considering the latest stats we saw on flight simulator usage (the ones released by Navigraph), 32 bit versions of P3D are being abandoned by users very fast.
-
Umberto, That was very informative. Thanks.
Thanks also for eventually including the fix in 32 bit. I’m only sticking with a side install of P3D3 while theres still a few aircraft not yet updated for v4. The FSLabs Concorde, the level d 767, THE PMDG MD11, the simcheck A300, and the feelthere 737s still only work in 32 bit. But that list is dwindling and of course I acknowledge support for 32 bit will eventually end.
Bryn
-
I have the same problems.
Always C:\windows\system32\ntdll.dll crash.
I also get it on a flight from ZSPD to LTBA somwhere over Russia
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
... 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 ?
-
I've done 3 east-to-west Atlantic crossings and haven't had a CTD since using the beta .dll.
-
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.
-
... because we are still not ready with the update.
Thank you for the headsup.
Waiting patiently.
-
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.
-
3/3 east to west successful flights so far. I'm starting to become cautiously optimistic.
-
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 (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:
-
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.
-
Of course I forgot to mention the most important, thanks for reminding. To be honest, I am not sure if the updated .dll was still active or not. I have downloaded and installed the updated .dll on the 16th of February after a crash off the Canadian coast like others. However, later I installed many other FSDT products and ran the Live Update several times during the time between installing the .dll and this crash so I am wondering, was this file overwritten? If it was, then it explains why the crash occured. What is unclear, that in a reply in January there was a line that says something like (not exactly like this, so don't quote me on this) the file will be included within a few weeks as part of a big update. Obviously I don't follow developers this closely so I can't tell if that "big update" already occured or not. So I am unsure, is this new .dll file already part of the official release? Hopefully not, and then at least, there is a hope that now that I reinstalled it again, things will go fine. In this case, though, if it's not yet part of the Live Update, I guess every Live Update overwites this file, so it must be manually added from time to time. Am I right?
-
Am I right?
I am afraid you are right.
That famous update is not - yet - released.
After a new (re)install of a scenery and/or Liveupdate, copy the new .dll file again.
-
Yes, that's correct. Since the updated .DLL is not considered official yet, it will be overwritten after running the Live Update, so you'll have to restore it.
Yes, we are late with the update, but it turned out to be bigger than we expected, so we took the chance to change some major parts of the whole GSX structure we didn't like entirely, in order to gain some big optimization benefit for P3D4 users. And, instead of "just" making new PBR textures, we remade many objects entirely from scratch, because they started to look outdated as well.
-
Yes, that's correct. Since the updated .DLL is not considered official yet, it will be overwritten after running the Live Update, so you'll have to restore it.
Yes, we are late with the update, but it turned out to be bigger than we expected, so we took the chance to change some major parts of the whole GSX structure we didn't like entirely, in order to gain some big optimization benefit for P3D4 users. And, instead of "just" making new PBR textures, we remade many objects entirely from scratch, because they started to look outdated as well.
That sounds nice thank you and looking forward to this
-
Hello Umberto,
I downloaded the bglmanx64.dll from your link within yr 1st message of this thread. It shows now version number 4.5.0.17. Is that the last correct beta version of this file?
Tks for brief confirmation,
Andreas
-
Hello Umberto,
I downloaded the bglmanx64.dll from your link within yr 1st message of this thread. It shows now version number 4.5.0.17. Is that the last correct beta version of this file?
Tks for brief confirmation,
Andreas
Yes, this is the latest. Too bad I didn't see this thread before the CTP today. Had a CTD in Canadian Airspace where everyone reports the problem. I should have taken a southern route.
-
Hello Umberto,
I downloaded the bglmanx64.dll from your link within yr 1st message of this thread. It shows now version number 4.5.0.17. Is that the last correct beta version of this file?
Tks for brief confirmation,
Andreas
Yes, this is the latest. Too bad I didn't see this thread before the CTP today. Had a CTD in Canadian Airspace where everyone reports the problem. I should have taken a southern route.
Did you have autosave? That is too bad, if CTP was ruined. This dll fixes it but becomes rewritten if you run FSDT Auto Update.
-
Ues, this is the latest. Too bad I didn't see this thread before the CTP today. Had a CTD in Canadian Airspace where everyone reports the problem.
But you are the only one reporting this crash using the updated .DLL so either your .DLL is not updated, maybe because you ran the Live Update after updating it manually, or this crash was caused by something else. All other users that posted here reported this problem as fixed.
Just to be clear: this updated .DLL will NOT magically fix any crashes in the sim. It will ONLY stop reading the airport database when cruising, since apparently there might be some corrupted data somewhere in that area which will crash the sim.
As explained, so many times already, the crash wasn't caused by our .DLL, it was the sim that crashed by ITSELF ( the crash happens FACILITIES.DLL ), when the bglmanx64.dll asks for navaids/airport data, which is required by GSX to know which airports are nearby. We don't query that data directly in memory, we just use the same functions the default GPS gauge use so, it's very likely if you opened the default Cessna GPS over that area and searched for airports or navaids, it would have crashed just the same.
This updated .DLL will ONLY fix THIS type of crash, by simply stopping to query navdata if flying above 10k feet. It doesn't do anything else, and won't surely fix any other crashes you might have.
-
Ues, this is the latest. Too bad I didn't see this thread before the CTP today. Had a CTD in Canadian Airspace where everyone reports the problem.
But you are the only one reporting this crash using the updated .DLL so either your .DLL is not updated, maybe because you ran the Live Update after updating it manually, or this crash was caused by something else. All other users that posted here reported this problem as fixed.
Your miss reading my reply. I did not know about your fix file when I was flying the CTP yesterday. If I had know there was a possible solution than I would have installed your updated file.
-
Installed the file and flew the route again. Worked like a champ. I can fly from Europe to the US once again. :)
Sent from my iPad using Tapatalk
-
Installed the file and flew the route again. Worked like a champ. I can fly from Europe to the US once again.
That's good to hear. I mis-read your reply, as if you were still getting a crash even after updating this file.
-
In any case, since the feedback so far has been very good, we replaced the .DLL on the Live Update server too, so there will be no need to replace it manually after a Live Update.
-
Thanks Umberto, your support is just great!
Andreas
-
I have the same problems.
Always C:\windows\system32\ntdll.dll crash.
I also get it on a flight from ZSPD to LTBA somwhere over Russia
I've found it in three places, the same as you over Russia. The normal place over northern Canada and in the North Sea of the coast of norway
-
I have the same problems.
Always C:\windows\system32\ntdll.dll crash.
I also get it on a flight from ZSPD to LTBA somwhere over Russia
I've found it in three places, the same as you over Russia. The normal place over northern Canada and in the North Sea of the coast of norway
I see this in other areas too. I had the ctd before using the updated dll after a p3d reinstall and not disabling some Canadian airports updated by Orbx vector. I do think the problem is a bug in afcad files that have incorrect navaids or unconnected parking and then the couatl dll having trouble reading it or getting stuck.
-
In any case, since the feedback so far has been very good, we replaced the .DLL on the Live Update server too, so there will be no need to replace it manually after a Live Update.
Is it still just the 64 bit DLL that is fixed? I just got this crash on the 32 bit P3Dv3 over Russia, and am still very eager to get the 32bit fix.
-
Is it still just the 64 bit DLL that is fixed? I just got this crash on the 32 bit P3Dv3 over Russia, and am still very eager to get the 32bit fix.
Yes, the 32 bit version has been updated too now.
-
Thank you very much!
-
In any case, since the feedback so far has been very good, we replaced the .DLL on the Live Update server too, so there will be no need to replace it manually after a Live Update.
Thanks for this Umberto, makes it easy.
-
There are no new live update notes since December 7th
-
There are no new live update notes since December 7th
We know that...but the new file is there anyway, regardless of the fact you haven't got the notification. So, just run the Live Update, and you WILL get it.