I had the same problem after latest update Manny

 

Hi Julian

 

I just noticed the awesome livery for that Real Air aircraft in your signiture... Where did you get it? link?

 

 

was planning on buying GSX but was not aware of these problems

 

GSX is a great product, the problem is how it's being managed via Coautl Add-On Manager.  Same with other FSDT Airports, really high quality products that are being mired by the Add-On manager.  I understand the need for DRM and software theft protection, but there are better ways to implement such protection.

Own a reasonably big stable of FSDT/Cloud 9/Flightbeam stuff and I can't really think of Addon Manager ever having been in the least way obtrusive, for me at least.

 

Conversely, I actually like the way it updates, in that it does it without the need to restart FSX. Others might consider an in-sim pop up unwelcome, and I can understand that.

 

Actually my biggest beef with FSDT is how long they take to update airports, a good example being Las Vegas, which has had a major new terminal for well over a year, yet there is apparently little urgency to change it. This is a top dollar airport, and worth every penny I might add, but currently not actually representative of the real thing.

 

On the flip side of that, GSX was changed to accommodate the PMDG 777 at the speed of light - somewhat easier than an airport redesign, of course.

So glad I read this thread... was planning on buying GSX but was not aware of these problems. Reminds me of all the useless TSR programs that made my life miserable back in the DOS days. At least there's no shortage of other add-ons to use my credit card on... time to go shopping....

 

It's your money, but I wouldn't let the comments here put you off buying GSX - one of the most cost effective add-ons, comparatively speaking. The alternative requires constant payments so you can have features like jetways enabled on airports for which you have already paid good money to have that sort of basic functionality, in my view. To my mind that is a far bigger scandal than anything Couatl might be accused of. FSDT jetways work superbly out of the box btw.

I would definitely echo that GSX is an awesome product.... have loved it from Day 1 and still use it on every airliner flight (as long as Couatl doesn't crash that is). 

 

And again, good point above about how quickly they updated GSX for the PMDG 777;  the day after the 777's release I believe. That is fast!

 

I think we all agree that FSDT products are really high quality, any issue seems to be around the Couatl engine that they are dependent upon, which I think can be fairly considered as a 'bloaty' (nicer term for bloatware :wink:) approach to authentication.  

The primary issue is, we have to deal with all the quirks of FSX itself... and instead of making our life easier, imagine if every single addon vendor with hundreds of products we install  has these quirks that we have to deal with.... Its becoming unmanagable and a nightmare.

 

Then, the probabily of successfully making a flight from one end to another  is practically zero. 

 

I am seriously considering some zones where they are clean and we don't have too many quirks.

 

This is my personal list for house cleaning and downsizing my FSX.

 

1) PNW (Orbx). Remove the old FS9 KPDX and KSEA. With some Orbix airports in the PNW Area. Remove the Orbx Australia and Earth simulations Gurnesy shurney etc..

 

2) Megascenery So Cal with the airport for KSAN, Aerosofts LA city (Catalina Airport)

 

3) Alaska area with the awesome Aerosofts Stevens airports.

 

4) Fly Tampa Princess Juliana and the carebean.

 

5) Asia. Thai Creations Paro,, VABB Mumbai, .. Nepal's VNKT and Aerosofts Luka and Fly Tampa's Kai Tak.

 

6) Dubai.

 

7) Freeware NL2000 with Aerosofts EHAM, German Airports and other Europe airports. And get all the Greek Island scenery. Remove the ugly Aerosofts Germany photosceneries. 

 

8) VFR Horizon UK Photoscenery and the autogen trees... and get all the UK2000 airports (This is something I am yet to venture into). 

 

9) FS Altitude Europe and NA.. Hmm..yet to decide if it goes or stays.

 

few other addon scenery.

 

AIRCRAFTS:

 

1. Limit it to PMDG for airliners (737NGX, 777 and the 747)

2. Maybe the CS 727

3. Real Air Dukes

4 One of the F1 aircrafts for the G1000

5) The Aerosoft's twotter.

 

Aircrafts can sit there if we don't use them...it does not intrude...so I can't complain too much about aircraft addons. I can also cut and past it outside the FSX directory entire set of addon aircrafts after I install them and if I feel nostalgic, I can copy and paste them back intio the Aircraft folder and now they are available.

 

OTHER ADDONS:

 

1) REX Textures

 

 

Thats it.

 

If I do that I can start enjoying my simming. I think.

Hi Manny, 

 

Just curious, but have you tried reaching out to Umberto/FSDT to find a solution to the issue you're having? He's always been able to resolve every single issue ever raised by Flightbeam customers. 

 

One thing I did want to point out, yes the DRM stuff is always annoying. However there's a backside to the Addon manager and Couatl that most don't know. It's helped us have a LOT more creative freedom. KIAD for example, wouldn't have the thick forest, or the dynamic night lighting without it. 

One other thing to add, is whether you want to believe it or not, FSDT is always listening, and you may be surprised to hear just how far the Addon Manager has gone in terms of making things easier for users. When we first started using it for our initial product, KSFO, I had many support emails every day with problems. I seldom have 1 a day now. It's come a LONG way, please have some patience. 

 

FSX is very finicky software, and for the sheer complexity of everything we are running, it's amazing we don't have more issues. The more patience we have for things to get smoother, the more quality products will come out. Out of our thousands of thousands of customers, we have VERY few with actual issues being reported. The large majority of people have no issues installing and running. Thats a final thought I want to point out, because threads like this end up being extremely damaging to developers. 

Hi Julian

 

I just noticed the awesome livery for that Real Air aircraft in your signiture... Where did you get it? link?

Hi Manny,

A user called Hangar 34  @ Opus simforums. I don't have it, but if you go to the forum I am sure you will be able to find out. Look for a post about "Banners" which was only posted a few days ago.

Just curious, but have you tried reaching out to Umberto/FSDT to find a solution to the issue you're having?

 

Hi There Mir.

 

No I have not.  The thing is, such issues do not appear all the time. I am sure I would go on for days without any issues..and then one day after a long flight just when I am on approach...BANG this could happen or not.  So this kind of issue gets us discussing the philosophy of this kind of tools...rather than the specific fail. my COUTL was slightly old and it was pointed out here. .. so I downloaded the latest and installed... so I am sure its probably fixed now.

 

And you are quite right, its become a serious issue for a  small minority of us who own lofs of payware sceneries.. If I had just 5-10 addons, then this is easily managable. 

 

If I have a specific addon installed and it works...then by installing another addon airport, the first should not break. I should not be expected to go and update some toolset to keep my previously installed working airport from breaking... . this kind of linking one product with another via these COUTL etc makes all this set of addons  fragile.  So its this philosophy of it that is an irrtant. 

 

I understand all software would have issues where we raise an issue and it gets solved and we move on. But this is another animal alltogether.

 

And let me also state, that both FSDT and you guys (Flightbeam) make one hellava airports...  So I really don't want to discourage developers like y'all stop making addon airports,,,   I still regret Flightzone folks stop making addon sceneries. So I wish that you guys profit and grow and continue making add ons. 

FSX is very finicky software, and for the sheer complexity of everything we are running, it's amazing we don't have more issues.

 

Sorta my point, why launch from within FSX if you know that's going to add another layer of possible support calls and problems?  Is it necessary to launch within FSX?  I just don't see a huge benefit in doing this (given the fragility of the environment) -- so users don't have to restart FSX?  As it stands now, not only do I have to restart FSX, I have to uninstall/re-install and re-enter keys for all those products under the Add-On manager if an update fails or goes wrong.

 

 

 

Thats a final thought I want to point out, because threads like this end up being extremely damaging to developers.

 

And I think here lies the problem, I didn't start this thread, but a lot of people have join in on this thread listing same or similar problems ... no one is complaining about the content (airports, GSX, etc.) ... it's the delivery/update process that's the problem for many of us - does it matter if we're a majority or minority?  How is that relevant?

 

So far, no one is acknowledging they're even looking into this - the theme seems to be it's somehow our fault?  In order to have "patients", wouldn't that require a "we're looking into this" -- is that the case?  A little positive communication could go a long way.

 

It is constructive in the sense it's many people reporting a similar problem, honestly, none of us are "trying" to break the Add-On manager, for the most part we hit the 1 option and let it update and the next thing we know all we see are jetways ... hopefully this is a two way street, not a one way.

 

I'm sorry you feel this is damaging, but exactly what else are we supposed to do?  Umberto is responsive, but at no point has he said "I'm looking into this" ... I'll even offer up my computer if he wants to provide a special trace/logging build that will help him with debugging and diagnostics.  PM me -- I want to help because I enjoy your product content.

 

Rob

I did the fairly recent update to couatl (I only have GSX installed) and the update "appeared" to work fine, but I noticed later that day that the "Updating airports" message did not go all of the way to 100%.  I thought nothing of it at the time and completed my flight with no problem.  Unfortunately, when I tried to set up a new flight later that day, FSX's load screen  would only load up to 83% and hang.  I had to Ctrl-Alt-Del in order to exit out.  The couatl update was the only thing that has gone into my FSX in the last couple of weeks.  Not knowing it was a problem with the couatl update, I searched for quite some time looking for anyone having a similar problem but got so frustrated that I ended up uninstalling FSX and all of the addons.  It took some time to do that, and took about 3 days worth of free-time to get everything loaded back up.

 

As Manny said above, I too decide to clean house of any addon aircraft and scenery no longer being utilized and I do appreciate the cleaner and faster loading sim. 

But I won't be loading any couatl updates for quite some time...

Absolutely agree with Rob.

 

Whilst I accept threads like this will be damaging, all we are really dealing in is free choice and feedback.  There is clearly a trend of feedback that this thread is reflecting.   Of course not everyone will feel the way we have expressed about Couatl/Add-on Manager, but when this many people rush to a thread to add that they feel the same way............. well clearly there is something there.

 

So back to free choice....... Umberto has the free choice to look into this, perhaps to acknowledge it, perhaps to consider a change, or perhaps to remain commited to the platform, and not change anything.

 

As Rob said, the problem is actually very clear    - we have a developer unnecessarily adding complexity to FSX by having his authentication programme run in FSX.      As said above, what if all developers did this ?? .............. Why do almost all other not do it ?

 

What we see here is some free choice and expression on the part of FSDT users, but also on the part of Umberto.

Fligthbeam uses this couatl thing also? The only manufacturer left on my list for addon airports now is Fly Tampa. Are there any of these issues with their products?  Before this thread is done I'm afraid I'll be back to 100% freeware.  The irony is that I switched from freeware to payware years ago to reduce my exposure to buggy software. Looks like the times are changing. The bright side is I'll be saving a good amount of cash. No I won't, I'll just spend it on aircraft instead. :lol:

 

Ted

I actually was "loathing" this topic as all the commercial developers need to hire a company to manage security for their software and make sure the product is legal.  That's what we have to put up with.  I'm not "loathing" so much about the topic anymore as tonight my FSX was crashing every time I loaded the 777 and set my location at the FSDT KLAX V2.  It crashed just as my aircraft was sitting at the gate every time.  When I was finally able to load KLAX I saw there were no buildings.  I opened up the Addon Manager and saw that the product(s) was properly activated (I own 99% of all of the FSDT/FlightBeam products).  I decided to deactivate the product and reinstall but the Addon Manager would not allow it and I got an error message (can't recall it now). 

 

Every time I had the CTD I got the following crash report from the AppCrashView:

 

Version=1
EventType=APPCRASH
EventTime=130233257666353749
ReportType=2
Consent=1
UploadTime=130233257666693768
ReportIdentifier=72ccf9dd-1a68-11e3-8d98-74d02b2c1fc8
IntegratorReportIdentifier=72ccf9dc-1a68-11e3-8d98-74d02b2c1fc8
WOW64=1
Response.BucketId=3765168531
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.18205
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=51db9710
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0002e41b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[60]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll
LoadedModule[61]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[64]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll
LoadedModule[65]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll
LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll
LoadedModule[70]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
LoadedModule[71]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll
LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll
LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll
LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll
LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll
LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll
LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll
LoadedModule[83]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll
LoadedModule[84]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll
LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll
LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll
LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[99]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[100]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[111]=C:\Windows\system32\wbemcomn.dll
LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[117]=C:\Windows\system32\dxgi.dll
LoadedModule[118]=C:\Windows\system32\d3d10.dll
LoadedModule[119]=C:\Windows\system32\d3d10core.dll
LoadedModule[120]=C:\Windows\system32\d3d11.dll
LoadedModule[121]=C:\Windows\system32\nvd3dum.dll
LoadedModule[122]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[123]=C:\Windows\system32\nvwgf2um.dll
LoadedModule[124]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[125]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[126]=C:\Windows\system32\d3d10_1.dll
LoadedModule[127]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[128]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[129]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[130]=C:\Windows\system32\WINSTA.dll
LoadedModule[131]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[132]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[133]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[134]=C:\Windows\SysWOW64\wer.dll
LoadedModule[135]=C:\Windows\System32\Wpc.dll
LoadedModule[136]=C:\Windows\System32\wevtapi.dll
LoadedModule[137]=C:\Windows\System32\msxml6.dll
LoadedModule[138]=C:\Windows\system32\SAMLIB.dll
LoadedModule[139]=C:\Windows\system32\netutils.dll
LoadedModule[140]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[141]=C:\Windows\system32\OLEACC.dll
LoadedModule[142]=C:\Windows\System32\MMDevApi.dll
LoadedModule[143]=C:\Windows\System32\PROPSYS.dll
LoadedModule[144]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[145]=C:\Windows\system32\RICHED20.DLL
LoadedModule[146]=C:\Windows\system32\HID.DLL
LoadedModule[147]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[148]=C:\Windows\system32\wdmaud.drv
LoadedModule[149]=C:\Windows\system32\ksuser.dll
LoadedModule[150]=C:\Windows\system32\AVRT.dll
LoadedModule[151]=C:\Windows\system32\msacm32.drv
LoadedModule[152]=C:\Windows\system32\midimap.dll
LoadedModule[153]=C:\Windows\system32\dinput.DLL
LoadedModule[154]=C:\Windows\System32\wship6.dll
LoadedModule[155]=C:\Windows\System32\wshtcpip.dll
LoadedModule[156]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll
LoadedModule[157]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[158]=C:\Windows\system32\inetmib1.dll
LoadedModule[159]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[160]=C:\Windows\system32\WINNSI.DLL
LoadedModule[161]=C:\Windows\system32\snmpapi.dll
LoadedModule[162]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_W16\scenery\ObjectFlow_W16.dll
LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[164]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KJAC\Scenery\ObjectFlow_KJAC.dll
LoadedModule[165]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll
LoadedModule[166]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\VMCX_AP.dll
LoadedModule[167]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[168]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4_Loader.dll
LoadedModule[169]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[170]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll
LoadedModule[171]=C:\Windows\system32\Secur32.dll
LoadedModule[172]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[173]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[174]=C:\Windows\system32\DNSAPI.dll
LoadedModule[175]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[176]=C:\Windows\System32\netprofm.dll
LoadedModule[177]=C:\Windows\System32\nlaapi.dll
LoadedModule[178]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[179]=C:\Windows\system32\rasadhlp.dll
LoadedModule[180]=C:\Windows\System32\npmproxy.dll
LoadedModule[181]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[182]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[183]=C:\Windows\system32\MSDART.DLL
LoadedModule[184]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[185]=C:\Windows\system32\bcrypt.dll
LoadedModule[186]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[187]=C:\Windows\system32\comsvcs.dll
LoadedModule[188]=C:\Windows\system32\ATL.DLL
LoadedModule[189]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[190]=C:\Windows\SysWOW64\msjetoledb40.dll
LoadedModule[191]=C:\Windows\SysWOW64\msjet40.dll
LoadedModule[192]=C:\Windows\SysWOW64\mswstr10.dll
LoadedModule[193]=C:\Windows\SysWOW64\msjter40.dll
LoadedModule[194]=C:\Windows\SysWOW64\MSJINT40.DLL
LoadedModule[195]=C:\Windows\SysWOW64\mstext40.dll
LoadedModule[196]=C:\Windows\system32\mlang.dll
LoadedModule[197]=C:\Windows\system32\RAASAUDIO32.DLL
LoadedModule[198]=C:\Windows\system32\X3DAudio1_6.dll
LoadedModule[199]=C:\Windows\SysWow64\xactengine3_4.dll
LoadedModule[200]=C:\Windows\SysWow64\XAudio2_4.dll
LoadedModule[201]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[202]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[203]=C:\Windows\system32\ntmarta.dll
LoadedModule[204]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[205]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[206]=C:\Windows\system32\msimtf.dll
LoadedModule[207]=C:\Windows\system32\msls31.dll
LoadedModule[208]=C:\Windows\system32\d2d1.dll
LoadedModule[209]=C:\Windows\system32\DWrite.dll
LoadedModule[210]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[211]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaIScnX_AP.dll
LoadedModule[212]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
LoadedModule[213]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX.DLL
LoadedModule[214]=C:\Windows\system32\NETAPI32.dll
LoadedModule[215]=C:\Windows\system32\srvcli.dll
LoadedModule[216]=C:\Windows\system32\wkscli.dll
LoadedModule[217]=C:\Windows\system32\WSOCK32.dll
LoadedModule[218]=C:\Windows\system32\MSVCP100.dll
LoadedModule[219]=C:\Windows\system32\MSVCR100.dll
LoadedModule[220]=C:\Windows\SysWow64\XAudio2_7.dll
LoadedModule[221]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX_3.DLL
LoadedModule[222]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges\PMDG_737NGX_2.dll
LoadedModule[223]=C:\Windows\system32\napinsp.dll
LoadedModule[224]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[225]=C:\Windows\System32\winrnr.dll
LoadedModule[226]=C:\Windows\system32\wshbth.dll
LoadedModule[227]=C:\Windows\system32\icmp.Dll
LoadedModule[228]=C:\Windows\system32\msadp32.acm
LoadedModule[229]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\AES\ViMaCli.dll
Sec[0].Key=LCID
Sec[0].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

 

On 3 attempts I got the ntdll.dll as the faulting module and on 2 additional attempts it was the infamous BEX/StackHash CTD.  Once it indicated the API.dll was the faulting module.  I thought maybe I needed to restart Coualt and went to the FSX Menu and there was no menu item for Coualt.  So I immediately diagnosed the problem was probably an issue with the Addon Manager and went to the FSDT website and reinstalled the Addon Manager.  Problem solved.  No more CTD's.  The buildings at KLAX were there and I had no problems taxiing or taking off.  In the FSX Menu, the entries for Couatl and the Addon Manager were there again.  So something happened.  I did nothing out of the ordinary. I do recall getting a GSX update two or three days ago but I had no problems running fsx after that other than today.  I fly out of KLAX often and suddenly this problem happened.  So, if you ever get a CTD when taking off or landing at an airport which is handled by Coualt (or the Addon Manager), this should be your first suspect.  Look at your Addon Menu and make sure the Addon Manager and the Coualt menu is there.  If not, you will need to download and installed the Addon Manager again.

 

I see a lot of CTD's like the ones I had up in the CTD Forum but never suspected it could be something like Couatl.  This will be one of my recommendations for a fix for BEX/StackHash, API, and NTDLL.dll ctd's in the future. 

 

Best regards,

Jim
 

And I think here lies the problem, I didn't start this thread, but a lot of people have join in on this thread listing same or similar problems ... no one is complaining about the content (airports, GSX, etc.) ... it's the delivery/update process that's the problem for many of us - does it matter if we're a majority or minority? How is that relevant?

 

 

 

So far, no one is acknowledging they're even looking into this - the theme seems to be it's somehow our fault? In order to have "patients", wouldn't that require a "we're looking into this" -- is that the case? A little positive communication could go a long way.

 

 

 

It is constructive in the sense it's many people reporting a similar problem, honestly, none of us are "trying" to break the Add-On manager, for the most part we hit the 1 option and let it update and the next thing we know all we see are jetways ... hopefully this is a two way street, not a one way.

 

 

 

I'm sorry you feel this is damaging, but exactly what else are we supposed to do? Umberto is responsive, but at no point has he said "I'm looking into this" ... I'll even offer up my computer if he wants to provide a special trace/logging build that will help him with debugging and diagnostics. PM me -- I want to help because I enjoy your product content.

 

 

Well said, Rob. Could not have put it better except you managed it better because of your perspective as a software engineer.

When I was finally able to load KLAX I saw there were no buildings

 

 

 

 

 

 

That is precisely what happened to me, Jim, and yet I could see that that airport was in the Add-on Manager, installed, and activated. That's when I decided enough was enough.

You know what I love the eye candy that FS Dreamteam brings to the sim, but their are a ton of problems with their addon manager as mentioned repetively is this thread.Next time when FS Dreamteam has a new airport, I will think twice before purchasing.