somiller

api.dll crash, P3Dv4.3 Client only update

Recommended Posts

I'm experiencing api.dll error/crash. Happened to me flying the PMDG NGX, midflight. The panel displays quit responding, but aircraft continued moving over the ground; autopilot quit working, buttons and switches quit responding...All this continued with the aircraft continued moving over the ground for several minutes...then the little blue rotating windows ring, then finally a P3D crash.

I noticed this thread on FSDT forum, but Umberto insists he's fixed any problem that might be related to his products, by updating bglmanx64.dll, but I have the new version of that file and still have the problem.

http://www.fsdreamteam.com/forum/index.php/topic,17829.30.html

Interestingly, I have been getting bglmanx64.dll errors in event viewer after I close P3D, but it seems to be solved if I make sure ActiveSky AS4 is running before I start P3D.

I've also posted this problem on LM's P3D forum.

Something is clearly amiss, and if I can't find a solution to this very soon, I'm going back to P3Dv4.1

Programs/addons running on P3D computer: ChasePlane; TrackIR; LittleNavConnect; FS Force2; Remote CDU Simlink.
Programs/addons running on remote/client laptop: AS4; LittleNavMap; Remote Overhead; PSXseecontraffic; RealTraffic

Kind Regards,
Steven Miller

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Hi Steven,

Have you read this thread?

https://www.avsim.com/forums/topic/538062-exiting-shutting-down-p3d-v42-causes-apidll-crash/

I have not seen the api.dll error ever since I disabled DL. It's an error that LM needs to investigate.

Thanks.

Jose

Share this post


Link to post
7 hours ago, somiller said:

I'm experiencing api.dll error/crash.

I noticed this thread on FSDT forum, but Umberto insists he's fixed any problem that might be related to his products, by updating bglmanx64.dll, but I have the new version of that file and still have the problem.

http://www.fsdreamteam.com/forum/index.php/topic,17829.30.html

Hi Steven,

As you are aware I was one of those who became quite involved in that thread. It was a very frustrating exercise with little to show for it. GSX and the FSTD Addon Manager were definitely involved in some way and I heard it from a little bird that this may have been resolved in Prepar3D 4.3. I believe it and has something to do with the SDK version used during the further development of the product.

However, it seems likely that the circumstances surrounding your api.dll crash may be different in that the crash, as described in that thread, related to exiting the sim while the FSDT Addon Manager/couatl/GSX were running.

I have yet to test this as I am still going through the process of confirming compatibilities and reactivating my list of Addons after updating to P3Dv4.3.

Regards,

Mike

Share this post


Link to post
1 hour ago, Cruachan said:

Hi Steven,

As you are aware I was one of those who became quite involved in that thread. It was a very frustrating exercise with little to show for it. GSX and the FSTD Addon Manager were definitely involved in some way and I heard it from a little bird that this may have been resolved in Prepar3D 4.3. I believe it and has something to do with the SDK version used during the further development of the product.

However, it seems likely that the circumstances surrounding your api.dll crash may be different in that the crash, as described in that thread, related to exiting the sim while the FSDT Addon Manager/couatl/GSX were running.

I have yet to test this as I am still going through the process of confirming compatibilities and reactivating my list of Addons after updating to P3Dv4.3.

Regards,

Mike

Jose,

Thank you for the info. I'll test your DL theory on my end and see if it helps me.

 

Mike,

Indeed, my api.dll crash occurred during a flight, however, all the bglmanx64.dll errors I had were on P3D exit/close. I had noticed that your errors were on exit, and initially I hesitated to post in your thread, but I reasoned that there may be an outside chance of our experiences being related so I decided to post.

Thank you for your information...I'll be watching this, and your thread with interest.

Kind Regards,

Share this post


Link to post

100% - of the time I get the API.DLL error Addon Manage is active on my system.

60 to 70% - of the time I get the error while Addon manager is active, the parentage goes way up if I start  the sim at the default scenario airport.

0% - is the number of errors I get the when Addon Manager is not installed or activated -since mid May.

According to my event log: the errors started showing up Mid May which coincides with the time I installed FSDT Las Vegas, until that time I only had FSDT LAX installed on my new puter  (puter built and LAX installed  - February 2018).

I have about 8 hrs of trouble shoot time with this API.dll thingy.  I've tested many combinations of add-ons, default settings, DL on/ff and even tested my hardaware at default bios settings ..... as long as ADDON Manager was not installed or active I get zero errors..

 

 

At Jose: I would be shocked if Dynamic Lighting, in a vacuum, is the root cause here, at least on my system.

 

Edited by FunknNasty

Share this post


Link to post

Interesting!

I do not think I saw this error in my log using P3D v4.2 while I had addon manager/GSX/Airports installed. I'm actually happy that the generating scenery on load was removed with updates.

But, I trust that it could be an issue on some systems.

Share this post


Link to post

I'm not totally unfamiliar with this issue. The 1st time I experienced the api.dll issue was on my Haswell when P3D V.4.0 was released, and sure enough the issue coincided with a Addon mgr install. I installed V4 along side my existing P3D v3.5, I think that's when ADDON MGR started using the addon-xml method, and I would get the same error when I used P3d V3.X  but not V.4.

 

Anyway, it's not a huge deal for me ...when it bugs me and I'm not flying to or from Vegas or LAX I just use the Lori tool to disable Addon Manager.

Share this post


Link to post
10 hours ago, somiller said:

Mike,

Indeed, my api.dll crash occurred during a flight, however, all the bglmanx64.dll errors I had were on P3D exit/close. I had noticed that your errors were on exit, and initially I hesitated to post in your thread, but I reasoned that there may be an outside chance of our experiences being related so I decided to post.

Thank you for your information...I'll be watching this, and your thread with interest.

Hi Steven,

Just a brief update to say that the problem is still there!

I tested the 3 exit routes (End Scenario, Exit and the 'X') with the FSDT Addon Manager enabled and the result was the same in each case. Sim crashes with the following reported error:

Note: the defaulting module is now ntdll.dll rather than api.dll.

Log Name:      Application
Source:        Application Error
Date:          07/07/2018 21:59:43
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Prometheus
Description:
Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263
Faulting module name: ntdll.dll, version: 6.1.7601.23889, time stamp: 0x598d5074
Exception code: 0xc000000d
Fault offset: 0x00000000000689f2
Faulting process id: 0x2b38
Faulting application start time: 0x01d4163432a87fea
Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ab892089-8228-11e8-abcf-40e230989421
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-07-07T20:59:43.000000000Z" />
    <EventRecordID>237636</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Prometheus</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.3.29.25520</Data>
    <Data>5b2c3263</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.23889</Data>
    <Data>598d5074</Data>
    <Data>c000000d</Data>
    <Data>00000000000689f2</Data>
    <Data>2b38</Data>
    <Data>01d4163432a87fea</Data>
    <Data>D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>ab892089-8228-11e8-abcf-40e230989421</Data>
  </EventData>
</Event>

When the Addon Manager is disabled the problem goes away. So, we are no further forward.

I've reported these findings over at FSDT, but I'm not holding my breath! To date, Umberto has appeared quite unwilling to accept there is an ongoing problem for some users. Understandable, I suppose, when he is unable to replicate the crash event.

Hard to know what else can be done to resolve this issue.

Regards,

Mike

 

Share this post


Link to post
48 minutes ago, Cruachan said:

 

I'm not unwilling to accept there's a problem for some users. I surely think and believe you have a problem but, even if "it goes away without the Addon Manager", that doesn't necessarily mean there's "a problem with the Addon Manager", it only means you have a problem that is already there, but you cannot see if without the Addon Manager triggering it.

Also, you are reporting a problem with NTDLL, while this thread was about the API.DLL problem.

As already explained on our forum, the API.DLL WAS, as it was reported on our forum, was indeed a problem with the Addon Manager and since that one I was able to reproduce it, I contacted LM, ask them where the sim was crashing, and with their help, I was able to find the problem in our code, and fixed it right away, and this has been confirmed on our forum and the LM forum too, both by other users, other developers, testers, and LM people too.

This clearly shows that, every report is taken seriously and, when it can be reproduced, it's fixed right away, and I never had any problems admitting there was a problem in our code. In fact, our release notes clearly says WE fixed the API.DLL silent crash on exit with an update. Note that, this doesn't necessarily mean we fixed *every* API.DLL crash that would ever appear. We just fixed that one which was our fault, but API.DLL crashes can have many different causes, and we could only act on the one related to us.

This problem of yours doesn't have anything to do with that one and, I'm afraid THIS one, I cannot reproduce, which means there isn't any chance to fixing (assuming it needs fixing on our side to begin with), until I could.

On our forum, I already offered a possible explanation, which would manifest just the same ( = goes away with the Addon Manager disabled ), which is problems with the navigational data. Some users reported that after installing a replacement set of .BGL files for updated navdata, caused NTDLL crashes, but only with GSX installed, but that's just because GSX asks the sim for airports around you, using a function provided by the sim so, what's really happening is not that GSX is causing a crash, but the sim it's crashing by itself when using its own function, which is confused by some corrupted data, not in the default scenery.

The only "fault" of GSX, is that it asks the sim for it but, in order to prevent or at least reduce the chance to be happening, and preventing users from being mislead into thinking the crash it's "caused" by GSX/Addon Manager (when the real cause it's a corrupted .BGL somewhere), we'll probably disable the query of nearby airports when flying above 10.000 ft and/or faster than 250 kts, so GSX would just stop doing anything while cruising, not even search for nearby airports, which is the only thing it does when flying right now.

Also, I already asked on our forum to post a new thread, so users won't be confused by having your issue posted in a thread that didn't had anything to do with it (like THIS one) and was a thread about a problem already solved.

Also, I kindly asking you to stop posting here, we would require me to do an entirely unnecessary double work (which will only decrease, not increase, the level of support you'll get), of following both threads.

And, as I've posted on our forum (again, please reply there), we can arrange a Teamviewer session at the beginning of the next week ( I'm replying to you now, on a Saturday night, but doing remote assistance late in the night is not very smart ), so I can have a look at your system, and perhaps find something.

Edited by virtuali

Share this post


Link to post
20 hours ago, somiller said:

I'm experiencing api.dll error/crash. Happened to me flying the PMDG NGX, midflight. The panel displays quit responding, but aircraft continued moving over the ground; autopilot quit working, buttons and switches quit responding...All this continued with the aircraft continued moving over the ground for several minutes...then the little blue rotating windows ring, then finally a P3D crash.

The API.DLL crash which was caused by the Addon Manager and was FIXED with the update was only happening after exiting the sim. There was a clear reason why it happened that way, and why it only happened on exit (and it could *only* happen on Exit), and this has been found and fixed easily enough. 

An API.DLL crash in midflight doesn't have anything to do with this, and I'm sure you get it even with no Addon Manager enabled. Any 3rd party product using Simconnect OR the new PDK might potentially cause an API.DLL crash so, it can be anything.

 

Quote

Interestingly, I have been getting bglmanx64.dll errors in event viewer after I close P3D, but it seems to be solved if I make sure ActiveSky AS4 is running before I start P3D.

This should prove the Addon Manager (bglmanx64.dll) didn't had anything to do with it and, instead, if was affected somehow by a different behavior of ActiveSky, depending if it's started before or after the sim. Sometimes it might be a conflict between different versions of the VC++ runtimes used by two modules, this is what usually happens when you observe a change depending on the module's loading order. 

Edited by virtuali

Share this post


Link to post
21 minutes ago, virtuali said:

The API.DLL crash which was caused by the Addon Manager and was FIXED with the update was only happening after exiting the sim. There was a clear reason why it happened that way, and why it only happened on exit (and it could *only* happen on Exit), and this has been found and fixed easily enough. 

An API.DLL crash in midflight doesn't have anything to do with this, and I'm sure you get it even with no Addon Manager enabled. Any 3rd party product using Simconnect OR the new PDK might potentially cause an API.DLL crash so, it can be anything.

 

This should prove the Addon Manager (bglmanx64.dll) didn't had anything to do with it and, instead, if was affected somehow by a different behavior of ActiveSky, depending if it's started before or after the sim. Sometimes it might be a conflict between different versions of the VC++ runtimes used by two modules, this is what usually happens when you observe a change depending on the module's loading order. 

Umberto,

Do you consider it worthwhile to post on ActiveSky forum about the bglmanx64.dll error? Currently, the AS4 for P3Dv4.3 update is open beta. So far, EVERY time I start AS4 before starting P3D, I don't get the error. I can't confirm for sure that EVERY time I start P3D before AS4 that I get the error on P3D close, but it seemed like that was the case.

Kind Regards,

Share this post


Link to post
54 minutes ago, somiller said:

Umberto,

Do you consider it worthwhile to post on ActiveSky forum about the bglmanx64.dll error? Currently, the AS4 for P3Dv4.3 update is open beta. So far, EVERY time I start AS4 before starting P3D, I don't get the error. I can't confirm for sure that EVERY time I start P3D before AS4 that I get the error on P3D close, but it seemed like that was the case.

 

I contacted Hifi simulations myself.

Share this post


Link to post
57 minutes ago, virtuali said:

 

I contacted Hifi simulations myself.

Umberto,

Thank you!

Kind Regards,

Share this post


Link to post
On 7/8/2018 at 1:56 AM, Cruachan said:

I tested the 3 exit routes (End Scenario, Exit and the 'X') with the FSDT Addon Manager enabled and the result was the same in each case. Sim crashes with the following reported error:

Note: the defaulting module is now ntdll.dll rather than api.dll.

As you posted on our forum:

http://www.fsdreamteam.com/forum/index.php/topic,17829.msg126344.html#msg126344

After you removed ALL other modules from starting (except the FSDT modules), your NTDLL.DLL crashes were gone, clearly proving it didn't had anything to do with our software, which I was quite sure of.

We'll continue looking to find the cause of your other API.DLL crash, but since I'm sure this one is fixed on your side, just like the NTDLL crash, it will likely prove to be caused by something else.

Share this post


Link to post
21 hours ago, virtuali said:

As you posted on our forum:

http://www.fsdreamteam.com/forum/index.php/topic,17829.msg126344.html#msg126344

After you removed ALL other modules from starting (except the FSDT modules), your NTDLL.DLL crashes were gone, clearly proving it didn't had anything to do with our software, which I was quite sure of.

We'll continue looking to find the cause of your other API.DLL crash, but since I'm sure this one is fixed on your side, just like the NTDLL crash, it will likely prove to be caused by something else.

Just got this error with no CTD:

Log Name:      Application
Source:        Application Error
Date:          7/10/2018 9:21:28 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      JOSE-PC
Description:
Faulting application name: Couatl.exe, version: 3.2.0.3997, time stamp: 0x5b0e87ef
Faulting module name: Couatl.exe, version: 3.2.0.3997, time stamp: 0x5b0e87ef
Exception code: 0xc0000005
Fault offset: 0x00056fa4
Faulting process id: 0x1214
Faulting application start time: 0x01d4185087c76137
Faulting application path: D:\Prepar3D v4\Addon Manager\Couatl\Couatl.exe
Faulting module path: D:\Prepar3D v4\Addon Manager\Couatl\Couatl.exe
Report Id: 266f25e7-8444-11e8-90fb-888888888788
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-07-10T13:21:28.000000000Z" />
    <EventRecordID>3856</EventRecordID>
    <Channel>Application</Channel>
    <Computer>JOSE-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3997</Data>
    <Data>5b0e87ef</Data>
    <Data>Couatl.exe</Data>
    <Data>3.2.0.3997</Data>
    <Data>5b0e87ef</Data>
    <Data>c0000005</Data>
    <Data>00056fa4</Data>
    <Data>1214</Data>
    <Data>01d4185087c76137</Data>
    <Data>D:\Prepar3D v4\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>D:\Prepar3D v4\Addon Manager\Couatl\Couatl.exe</Data>
    <Data>266f25e7-8444-11e8-90fb-888888888788</Data>
  </EventData>
</Event>

Share this post


Link to post
18 hours ago, DJJose said:

Just got this error with no CTD:

Log Name:      Application
 

This error too, doesn't have anything to do with this thread, which is about a crash on exit in API.DLL.

As I've said to the other poster, which also had a crash which wasn't related to this thread (NTDLL.DLL that, after further testing, turned out to be NOT RELATED TO FSDT IN ANY WAY), it would be best if, instead of posting here, you would post about your issue on our forum, opening a new thread, with a proper title, and with a complete description of the problem and how it happened so, just like all other reports, we can check it.

There's at least one add-on, which I won't name here, which caused a crash in Couatl.exe, because was changing the default international settings (locale) of the whole sim (potentially dangerous), when in fact the correct method should have been to change the locale of its own application only.

This made Couatl crashing, without being our fault (it crashed inside a standard library we use) so, I got in touch with the developer, he fixed HIS code, and this prevented the crash. Just an example of a problem that "looks" to be "a Couatl problem", when its not, was caused by another add-on, and was fixed by fixing that one, because the developer was smart enough to recognize the problem in his code.

Edited by virtuali
.

Share this post


Link to post
5 hours ago, virtuali said:

This error too, doesn't have anything to do with this thread, which is about a crash on exit in API.DLL.

There's at least one add-on, which I won't name here, which caused a crash in Couatl.exe, because was changing the default international settings (locale) of the whole sim (potentially dangerous), when in fact the correct method should have been to change the locale of its own application only.

This made Couatl crashing, without being our fault (it crashed inside a standard library we use) so, I got in touch with the developer, he fixed HIS code, and this prevented the crash. Just an example of a problem that "looks" to be "a Couatl problem", when its not, was caused by another add-on, and was fixed by fixing that one, because the developer was smart enough to recognize the problem in his code.

Hi Umberto,

Interesting. However it does not appear to be helping my situation. 

Why? Simply because I have disabled all my Addons (with the exception of SODE and the FSDT Addon Manager), deactivated everything in the DLL.xml and EXE.xml files and the sim is currently running with default scenery.cfg (No ORBX activity) and minimally modified (Graphic Settings) Prepar3D.cfg files. Yet that crash with faulting api.dll error keeps occurring during sim exits.

During testing I have noted that when the Scenery indexes are being built afresh then this crash prevents the creation of the FilelistIndex.dat file. A clean exit with the FSDT Addon Manager inactive resolves this issue.

I appreciate how frustrating this issue must be for you, as it is for me. What diagnostic measures/tools were employed to isolate the issue as described in your previous post? Perhaps a similar approach could be tried here.

Lastly I should say that I had uninstalled the FSDT Addon Manager and SODE before reinstalling (as Administrator and Antivirus disabled), using the latest posted installers. 

Prepar3D v4.3 was updated fully (Client, Content and Scenery) and the sim is stable and is performing very well in every other respect.

Regards,

Mike

Share this post


Link to post
55 minutes ago, Cruachan said:

Hi Umberto,

Interesting. However it does not appear to be helping my situation. 

Of course it doesn't, since my last remark was related to ANOTHER problem, which doesn't have anything to do with the one discussed here, which is the crash on exit with API.DLL. That's why I keep saying not to post in unrelated threads: it makes impossible to follow them, as in this case.

 

55 minutes ago, Cruachan said:

Why? Simply because I have disabled all my Addons (with the exception of SODE and the FSDT Addon Manager), deactivated everything in the DLL.xml and EXE.xml files and the sim is currently running with default scenery.cfg (No ORBX activity) and minimally modified (Graphic Settings) Prepar3D.cfg files. Yet that crash with faulting api.dll error keeps occurring during sim exits.

As I've said, API.DLL is Simconnect so, even an airplane gauge that use Simconnect, but doesn't have/require a module that you can disable, can cause this, so you are mislead thinking you "disabled everything", but the code is loading just by loading the airplane.

 

 

55 minutes ago, Cruachan said:

I appreciate how frustrating this issue must be for you, as it is for me. What diagnostic measures/tools were employed to isolate the issue as described in your previous post? Perhaps a similar approach could be tried here.

Since I WAS (I'm not, now), able to reproduce the SILENT (only in the Event Viewer, is THIS what's happening to you ?) API.DLL crash on Exit, I sent it to LM to try, they were able to reproduce it too, and told me where the sim was crashing, which allowed me to find the problem in my code.

After the fix, everybody that had this problem, both on LM forum and on our forum too, confirmed it was fixed. You are the only one that says otherwise, which is why I'm quite convinced it must be something else.

 

Share this post


Link to post

Hello Umberto,

 

2 hours ago, virtuali said:

Since I WAS (I'm not, now), able to reproduce the SILENT (only in the Event Viewer, is THIS what's happening to you ?) API.DLL crash on Exit, I sent it to LM to try, they were able to reproduce it too, and told me where the sim was crashing, which allowed me to find the problem in my code.

After the fix, everybody that had this problem, both on LM forum and on our forum too, confirmed it was fixed. You are the only one that says otherwise, which is why I'm quite convinced it must be something else.

When was the Addon Mgr. issue fixed -regarding the api.dll?

I ask because I had no api.dll  issues with my new puter build -built late Feb 2018 and with just your LAX installed (also installed around the time the computer was put together) until around the time I installed your Vegas airport in mid May.

-thanks

 

Share this post


Link to post
9 minutes ago, FunknNasty said:

When was the Addon Mgr. issue fixed -regarding the api.dll?

May 22th

https://www.fsdreamteam.com/couatl_liveupdate_notes.html

However, if you installed something before that date, and haven't updated (or updated after the fix) it's possible you would never see the problem, it appeared only when we made some additions to the software which will be required only by KORD V2 and GSX Level 2, so it wasn't always there, it only started to appear after a certain date, most likely around March/April.

Share this post


Link to post
7 minutes ago, virtuali said:

May 22th

https://www.fsdreamteam.com/couatl_liveupdate_notes.html

However, if you installed something before that date, and haven't updated (or updated after the fix) it's possible you would never see the problem, it appeared only when we made some additions to the software which will be required only by KORD V2 and GSX Level 2, so it wasn't always there, it only started to appear after a certain date, most likely around March/April.

Ah Ha!  It is you!!!!  See, just my luck, you fixed it for the masses at my expense. <-----just a guess

Anyway, I hope you see something down the road that you can share that will help me solve my api.dll issue.

...I can live with the api.dll issue but not LAX. 🙂

-Thanks

Share this post


Link to post
2 hours ago, virtuali said:

Since I WAS (I'm not, now), able to reproduce the SILENT (only in the Event Viewer, is THIS what's happening to you ?) API.DLL crash on Exit, I sent it to LM to try, they were able to reproduce it too, and told me where the sim was crashing, which allowed me to find the problem in my code.

After the fix, everybody that had this problem, both on LM forum and on our forum too, confirmed it was fixed. You are the only one that says otherwise, which is why I'm quite convinced it must be something else.

 

Hi Umberto,

I refer you to post #16 in the api.dll thread marked *SOLVED* over at the FSDT forum where I described in detail how the sim is crashing. In that post I included several images, one of which answers your question. No, the crash is not silent and never has been.

With respect, I think you are forgetting those users who posted in that thread and, because the fix did not work for them, decided the only “solution” was to uninstall GSX/FSDT Addon Manager meantime in the hope an effective resolution can be found eventually.

You appear convinced that this is a Simconnect issue, possibly involving an a/c gauge. If this is true then why is this happening while using default aircraft? Somehow that does seem unlikely in my case.

Is there any way that the cause can be tracked down or will I have to throw in the towel and join those who have gone before me? Don’t misunderstand me, I do want to continue using GSX, which is a great product, but faced with this constant intransigence and unwillingness to try to help is really quite wearing and at some point I may have to concede enough is enough.

Regards,

Mike

 

Share this post


Link to post
57 minutes ago, Cruachan said:

Hi Umberto,

I refer you to post #16 in the api.dll thread marked *SOLVED* over at the FSDT forum where I described in detail how the sim is crashing. In that post I included several images, one of which answers your question. No, the crash is not silent and never has been.

Then it's possibly not the crash we fixed, and it's not necessarily caused by our software. I obviously took the time to verify your claim that you always get a crash after pressing "ESC" then "Exit", and posted a video on our forum, showing the crash doesn't happen.

 

Quote

With respect, I think you are forgetting those users who posted in that thread and, because the fix did not work for them, decided the only “solution” was to uninstall GSX/FSDT Addon Manager meantime in the hope an effective resolution can be found eventually.

 

There's only ONE other user (Sabretooth78) that says he has a crash on API.DLL when exiting but, there's no evidence of what other software he use or whether he has disabled all addons, which means there's no evidence his crash is the same that we fixed. 

 Another user (413x3) *USED* to have crashes on exit, now only complains about general instability of his system (again, no evidence this is *caused* by our software), and he said he has NO crash on exit.

Again, I can only repeat and confirm the "silent API.DLL crash on Exit" IS fixed in the last update. And, I cannot replicate any other API.DLL crash so far.

Maybe, we might have a Teamviewer session, so I could check your system directly, trying to understand what is so specific of your system only is causing it, which is maybe shared by the only other user that still have it, after the fix. In fact, I already offered you a Teamviewer session so why, instead of just doing it, you keep posting here, when I also asked you to continue on the FSDT forum ?

Edited by virtuali

Share this post


Link to post
1 hour ago, FunknNasty said:

Ah Ha!  It is you!!!!  See, just my luck, you fixed it for the masses at my expense. <-----just a guess

 

As I've said, the problem has been fixed since May 22th so, if you ran the FSDT Live Update after that day, and if you still have it, it's not necessarily the same problem, and it's not necessarily caused by our software.

Try to disable each and every 3rd party module BOTH in the Options->Addons menu AND in the 4 DLL/EXE.XML files in BOTH locations (%APPDATA% and %PROGRAMDATA%), leaving only the Addon Manager enabled, and see if you still have the crash.

If you have, please don't post here. Post on the FSDT forum, or send me a PM *THERE*, so we might eventually arrange a Teamviewer session, so I could have a look at your system, check if you really disabled all the other addons, and see if there's something special in your system which is causing this problem.

Again, please do not reply here, it's totally useless, since we'll have to arrange a TM session on the FSDT forum anyway.

Share this post


Link to post
2 hours ago, virtuali said:

I obviously took the time to verify your claim that you always get a crash after pressing "ESC" then "Exit"

Hi Umberto,

Please point me to the post where I made that claim. To my knowledge I never made such a statement. Perhaps you are confusing me with another poster? 

I described three exit scenarios: End Scenario, Exit and ‘X’. Never in my years if simming have I used the ‘ESC’ key as a means to leave the running sim. Perhaps selecting End Scenario is equivalent to hitting the ‘ESC’ key?

Mike

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now