FSDreamTeam forum
General Category => General Discussion => Topic started by: crash77 on October 08, 2015, 10:44:45 pm
-
Wow...I really don't know where to begin. I have spent hours and hours trying to figure this out...so I'll try to keep it short. Ever since you implemented the Couatl "live" I have had nothing but problems. First, it pops up and says it needs to download via in game....ALL the time. I checked and already had the latest Couatl manager downloaded...so what does it keep trying to update??? Second, when it does update it often makes FSX crash saying that their is a conflict with the Couatl module. I have had to delete ALL FSDT products and reinstall them for it to stop crashing. The CYVR scenery which I have NEVER had issues with then crashes until after all scenery's are loaded and the latest Couatl manager is reinstalled after everything. I cannot load PHNL straight from FSX without going to another FSDT scenery and letting it load the cache. Only then can I load PHNL without it crashing. Now tonight...yet ANOTHER Couatl update (really?? another??) and now FSX keeps crashing on exit. This time I got a message saying their was a problem with my FSUIPC module..REALLY?? So I reinstalled the version of FSUIPC (same version already installed before) and no more message. Yet FSX still crashes on exit every time. Something that has never happened. I love your scenery's but really getting sick and tired of the constant updates which usually only leads to other issues. I'm at a total loss and ready to just delete all FSDT products and stop using them...something that I am really trying to avoid, but if this keeps continuing to happen really what choice do I have. I have never had any issues with Flightbeam, Fly-Tampa or any other add-ons except Couatl and FSDT. Any ideas or help would be greatly appreciated, thanks for your time...Crash.
-
Just deleted all my FSDT products...FSX no longer crashes after closing. I think I'm done with FSDT products, a sad day indeed.
-
Umberto, I have the same problem(s).
I just installed the latest version of GSX, the one you updated today and my FSX (not SE, just Acceleration) doesn't start anymore. There is a crash on FSUIPC4 version 4.938c.
I have been following the messages of people having crash problems in the last few days, and I concur. There is something wrong with GSX. I updated 2 weeks ago to the latest version, and since then, I have been having crash after crash. The mouse and the keyboard freeze, and I have no other option than a hard re-start of the computer. The error is not even registering on my AppCrashView.
I hope you can fix this or give us a chance to flip back to the older versions.
Thanks,
Johan
PS: see below the latest crash info
Version=1
EventType=APPCRASH
EventTime=130888229063451181
ReportType=2
Consent=1
UploadTime=130888229063919182
ReportIdentifier=dc3e678e-6e19-11e5-94f6-00226865b384
IntegratorReportIdentifier=dc3e678d-6e19-11e5-94f6-00226865b384
WOW64=1
Response.BucketId=1275000367
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=StackHash_0a9e
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=ffb9008e
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
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close 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\SysWOW64\SYSFER.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[6]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[7]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[8]=C:\Windows\syswow64\GDI32.dll
LoadedModule[9]=C:\Windows\syswow64\USER32.dll
LoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[11]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[15]=C:\Windows\syswow64\LPK.dll
LoadedModule[16]=C:\Windows\syswow64\USP10.dll
LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[18]=C:\Windows\syswow64\ole32.dll
LoadedModule[19]=C:\Windows\system32\apphelp.dll
LoadedModule[20]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[21]=C:\Windows\system32\UxTheme.dll
LoadedModule[22]=C:\Windows\system32\WINMM.dll
LoadedModule[23]=C:\Windows\system32\samcli.dll
LoadedModule[24]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[25]=C:\Windows\system32\MSACM32.dll
LoadedModule[26]=C:\Windows\system32\VERSION.dll
LoadedModule[27]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[28]=C:\Windows\system32\sfc.dll
LoadedModule[29]=C:\Windows\system32\sfc_os.DLL
LoadedModule[30]=C:\Windows\syswow64\USERENV.dll
LoadedModule[31]=C:\Windows\syswow64\profapi.dll
LoadedModule[32]=C:\Windows\system32\dwmapi.dll
LoadedModule[33]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[34]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[35]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[36]=C:\Windows\syswow64\urlmon.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[43]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[44]=C:\Windows\syswow64\iertutil.dll
LoadedModule[45]=C:\Windows\syswow64\WININET.dll
LoadedModule[46]=C:\Windows\system32\MPR.dll
LoadedModule[47]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[48]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[49]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[50]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[51]=C:\Windows\system32\mscms.dll
LoadedModule[52]=C:\Windows\system32\DDRAW.dll
LoadedModule[53]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[54]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[55]=C:\Windows\syswow64\IMM32.dll
LoadedModule[56]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[57]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[58]=C:\Windows\syswow64\NSI.dll
LoadedModule[59]=C:\Windows\system32\msi.dll
LoadedModule[60]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[61]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll
LoadedModule[62]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL
LoadedModule[63]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[64]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[65]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll
LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll
LoadedModule[68]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll
LoadedModule[69]=C:\Windows\system32\DINPUT8.dll
LoadedModule[70]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll
LoadedModule[71]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll
LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll
LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll
LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll
LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll
LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll
LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll
LoadedModule[78]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll
LoadedModule[79]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[80]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[81]=C:\Windows\system32\d3d9.dll
LoadedModule[82]=C:\Windows\system32\d3d8thk.dll
LoadedModule[83]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll
LoadedModule[84]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll
LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll
LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll
LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll
LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll
LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll
LoadedModule[93]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll
LoadedModule[94]=C:\Windows\system32\DSOUND.dll
LoadedModule[95]=C:\Windows\system32\POWRPROF.dll
LoadedModule[96]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll
LoadedModule[97]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18946_none_72d45ee78666ea32\gdiplus.dll
LoadedModule[98]=C:\Windows\system32\MSIMG32.dll
LoadedModule[99]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[100]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[102]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dll
LoadedModule[103]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[104]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[106]=C:\Windows\system32\rsaenh.dll
LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[112]=C:\Windows\system32\wbemcomn.dll
LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[118]=C:\Windows\system32\dxgi.dll
LoadedModule[119]=C:\Windows\system32\d3d11.dll
LoadedModule[120]=C:\Windows\system32\nvd3dum.dll
LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[122]=C:\Windows\system32\bcrypt.dll
LoadedModule[123]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[124]=C:\Windows\SysWOW64\bcryptprimitives.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\SysWOW64\dxdiagn.dll
LoadedModule[130]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[131]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[132]=C:\Windows\system32\winbrand.dll
LoadedModule[133]=C:\Windows\system32\nvapi.dll
LoadedModule[134]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[135]=C:\Windows\system32\WINSTA.dll
LoadedModule[136]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[137]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll
LoadedModule[138]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[139]=C:\Windows\SysWOW64\wer.dll
LoadedModule[140]=C:\Windows\System32\Wpc.dll
LoadedModule[141]=C:\Windows\System32\wevtapi.dll
LoadedModule[142]=C:\Windows\System32\msxml6.dll
LoadedModule[143]=C:\Windows\system32\SAMLIB.dll
LoadedModule[144]=C:\Windows\system32\netutils.dll
LoadedModule[145]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dll
LoadedModule[146]=C:\Windows\system32\OLEACC.dll
LoadedModule[147]=C:\Windows\System32\MMDevApi.dll
LoadedModule[148]=C:\Windows\System32\PROPSYS.dll
LoadedModule[149]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[150]=C:\Windows\system32\RICHED20.DLL
LoadedModule[151]=C:\Windows\system32\HID.DLL
LoadedModule[152]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[153]=C:\Windows\system32\wdmaud.drv
LoadedModule[154]=C:\Windows\system32\ksuser.dll
LoadedModule[155]=C:\Windows\system32\AVRT.dll
LoadedModule[156]=C:\Windows\system32\msacm32.drv
LoadedModule[157]=C:\Windows\system32\midimap.dll
LoadedModule[158]=C:\Windows\system32\dinput.DLL
LoadedModule[159]=C:\Windows\System32\wship6.dll
LoadedModule[160]=C:\Windows\System32\wshtcpip.dll
LoadedModule[161]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll
LoadedModule[162]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[163]=C:\Windows\system32\MSVCP120.dll
LoadedModule[164]=C:\Windows\system32\MSVCR120.dll
LoadedModule[165]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KMRY\scenery\ObjectFlow_KMRY.dll
LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[167]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll
LoadedModule[168]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simpropext.dll
LoadedModule[169]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\AbacusCatapultFSX.dll
LoadedModule[170]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll
LoadedModule[171]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll
LoadedModule[172]=C:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll
LoadedModule[173]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Captain_Sim\520\cs.sound.dll
LoadedModule[174]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Captain_Sim\Captain_Sim.b767.menu.dll
LoadedModule[175]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Captain_Sim\767\cs.sound.dll
LoadedModule[176]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll
LoadedModule[177]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\VMCX_AP.dll
LoadedModule[178]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[179]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FSX2BMAP_DLL.dll
LoadedModule[180]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FSXLauncher.dll
LoadedModule[181]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll
LoadedModule[182]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Captain_Sim\777\cs.sound.dll
LoadedModule[183]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll
LoadedModule[184]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[185]=C:\Windows\system32\WINNSI.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=1275000367/nBucketTable=1/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
-
Just deleted all my FSDT products...FSX no longer crashes after closing. I think I'm done with FSDT products, a sad day indeed.
You waited only 1 hour and then reported that you deleted all your products, why bother? Did you download and install the latest addon manager?
http://www.fsdreamteam.com/products_addonmanager.html
-
I have been following the messages of people having crash problems in the last few days, and I concur.
All of them used FSX Steam. We clearly identified the problem, and there's no way BOTH the old crash, and the fix for it, could affect normal FSX.
Nothing in your log indicates the crash has antyhing to do with GSX or any of our products. It's just FSX.EXE crashing itself.
There is a crash on FSUIPC4 version 4.938c.
This clearly proves it has nothing to do with any of our products. None of them use or interacts with FSUIPC.
-
Ever since you implemented the Couatl "live" I have had nothing but problems.
There are no problems with it.
First, it pops up and says it needs to download via in game....ALL the time.
No, it doesn't. It does that, only if you don't install the suggested update
I checked and already had the latest Couatl manager downloaded...so what does it keep trying to update???
That's you mistake. You assume that "because" you downloaded the "latest Couatl manager" ( there's no such thing, maybe you mean "The Stand-Alone Addon Manager" installer ), there will be no further updates. If you see an update message, it means there has been another update that has been released AFTER the day you last installed the Stand-Alone Addon Manager.
Second, when it does update it often makes FSX crash saying that their is a conflict with the Couatl module.
No, it doesn't do that.
When a minor update is released, it will restart Couatl.exe. So, it's possible your problem is the Restart function is not working for some reason, but this is of course entirely unrelated to the Live Update, you woould probably see the same message even if you tried "restart Couatl" yourself.
But since you haven't indicate the PRECISE, exact text of the message ( there's no such message like "there is a conflict with the Couatl module" ), it's difficult to understand what's causing this. Please indicate the precise, exact, text of an error message, so we can understand if it's coming from our software or from FSX, or from Windows itself, and they are all entirely different issues that must be handled entirely different.
I have had to delete ALL FSDT products and reinstall them for it to stop crashing.
This was obviously entirely redundant and not needed. If you have issues with the Live Update, just download and install the Stand-Alone Addon Manager, and install it when FSX is not running. This will update EVERYHING related to the Addon Manager and Couatl.exe.
The CYVR scenery which I have NEVER had issues with then crashes until after all scenery's are loaded and the latest Couatl manager is reinstalled after everything.
Please indicate the precise, exact, text of any errors you see.
I cannot load PHNL straight from FSX without going to another FSDT scenery and letting it load the cache.
If with "loading the cache" you mean REGENERATING the cache, this might be your problem. You are not even supposed to "wait" to load for the cache. The cache will be recreated ONLY if you add a new scenery OR if it wasn't completed successfully the last session. This might happen if FSX crashed in the previous session.
Normally, you should see just the "Airport cache loaded successfully" message at startup, without any wait.
If you see the cache regeneration message, with the progress percentage, try not doing anything, and let it end. Check if it says the cache has been recreated successfully or not,. If it hasn't, maybe there's a problem with one of your sceneries (a corrupted .BGL, for example), so it cannot complete the regeneration, and it will start again on the next start.
If the cache regeneration has completed successfully, try to EXIT from FSX, wait a few seconds so you are sure it has closed correctly, then restart it. You should see the "Airport cache loaded successfully" message at startup now.
Only then can I load PHNL without it crashing. Now tonight...yet ANOTHER Couatl update (really?? another??) and now FSX keeps crashing on exit. This time I got a message saying their was a problem with my FSUIPC module..REALLY??
This clearly proves the problem doesn't have anything to do with us, since none of our modules use or interacts with FSUIPC.
So I reinstalled the version of FSUIPC (same version already installed before) and no more message.
This further clearly proves the problem didn't had anything to do with us, since it was fixed by reinstalling FSUIPC.
Yet FSX still crashes on exit every time.
Please indicate the precise, exact, text of the error message. And please indicate even if you don't see ANY error message. A silent crash with no messages is caused by having old and new files mixed together, and this might be caused by the antivirus or the firewall, which is blocking SOME of the files that are supposed to be updated, and let it pass some others, causing a total mess that will surely crash FSX with no error messages.
In this case, be sure you turn off the firewall, and reinstall the Stand-Alone Addon Manager for FSX only.
I have never had any issues with Flightbeam, Fly-Tampa or any other add-ons except Couatl and FSDT.
You said it...Flightbeam uses EXACTLY THE SAME FILES AS WE DO!! They use the precise, identical, exact, same version of Couatl we use with GSX, and their installers downloads the same files from the same location (OUR server), because WE MADE THE installers for Flightbeam!
-
I am sorry to disagree. I desinstalled GSX and I don't have that problem anymore...
-
You are free to disagree as much as you want, but the fact stands, that FSUIPC is TOTALLY unrelated to us. In fact, what an FSUIPC crash might prove, is that you had ANOTHER problem that is *affecting* BOTH FSUIPC, and GSX.
Yes, I know it sound "logical" saying "I desinstalled GSX and I don't have that problem anymore", but that doesn't mean the problem IS *caused* by GSX, it only means that, if there's no GSX to call into sim features that normally should work, but don't (because of the problem that was ALSO affecting FSUIPC), you have no way to see the problem triggered, not that GSX is the *cause* for it.
Note that, some of the problems like libraries conflicts, due to different addons trying to use different version of the libraries at the same time, are sometimes only temporary, affecting a single FSX session so, it's possible that the problem that affected FSUIPC and GSX, could have been cured by simply restarting Windows.
Try to:
- Restart Windows
- Reinstall GSX now, to be absolutely sure you get all the current versions of the files, and be sure you TURN OFF FIREWALLS AND ANTIVIRUS, otherwise you might not get them (because they are mistakenly blocking the downloads).
You said you "updated 2 weeks ago" so, you are surely outdated by now, because we had updates in the last days.
-
All I can tell you is that ever since this "live" update I have had problems, and yes I have the latest manager version downloaded. That's why I don't understand what it needed to "update." Now their is something very wrong here. My FSUIPC (latest version) keeps crashing FSX with an error message at start stating that their is a problem with the FSUIPC add-on. If I chose to run it with any FSDT product that install the COUATL manager it automatically crashes FSX to desktop. If I chose to run without COUATL manager installed the message still comes up on start, but allows me to run FSX. If I chose not to run the the FSUIPC add-on it will not load the module. All I did in the beginning was run the "live" update (when I already had the latest COUATL manager installed), and then this FSUIPC issue started. I'm not sure what the problem is or how to fix it, all I know is everything was working fine before I installed the "live" update. The only thing I can think of is the much dreaded fresh reinstall of FSX and all my add-ons. I'm not saying for fact it is any of your products causing this. But it all started when I started a flight in FSX and the COUATL "live" popped up and said to download the latest version....even though I already had v.3.0.0.9. installed. I even removed the FSX.cfg file and let it rebuild but no luck.
-
I have contacted Pete of FSUIPC to see if he has any suggestions. I noticed from the FSUIPC download page it says that the current version is 4.946. Yet if you download the file it's version 4.947. Can someone confirm using both FSUIPC v4.947 and COUATL manager v.3.0.0.9. with FSX without any issues? Thanks.
-
All I can tell you is that ever since this "live" update I have had problems, and yes I have the latest manager version downloaded.
Fact you downloaded the latest version, doesn't mean you have the latest version of the files, because the installer *downloads* them so, it doesn't matter when you download, it matters when you install it.
That's why I don't understand what it needed to "update."
The Live Update has a feature to display the release notes. They tell you what has been "updated".
My FSUIPC (latest version) keeps crashing FSX with an error message at start stating that their is a problem with the FSUIPC add-on. If I chose to run it with any FSDT product that install the COUATL manager it automatically crashes FSX to desktop.
Does this sentence means (it seem so) that: FSUIPC is displaying an error when "FSDT product that install the COUATL manager" (again, there's no such thing as a "Couatl manager" ) ? This CLEARLY indicates you have a problem, regardless if our modules are installed or not.
If I chose to run it with any FSDT product that install the COUATL manager it automatically crashes FSX to desktop.
If with "automatically crashes FSX to desktop" you mean a silent crash with no error message, this usually mean your firewall/antivirus is BLOCKING the correct update of our files, letting pass some of them, and blocking others. This is GUARANTEED to cause such crash.
The solution (assuming THIS is the "crash" you see now), as already indicated, is to run the Stand-Alone Addon Manager with the firewall and antivirus turned off.
If I chose to run without COUATL manager installed the message still comes up on start, but allows me to run FSX. If I chose not to run the the FSUIPC add-on it will not load the module.
Again, there's no such thing as the "Couatl manager". The message you see it's either about the "Addon Manager", which is a module OR the "Couatl scripting engine", which is an entirely different module.
What do you mean with " chose to run without COUATL manager installed ?
Do you mean:
- You have the <ManualLoad> setting in the EXE.XML, so you usually always see a *request* to start the Couatl SCRIPTING ENGINE at start, so you turn it down ?
OR
- You Unistalled GSX, so you are not running any of our modules
OR
- You see BOTH a request to run the "Couatl SCRIPTING ENGINE" AND another request to run the "Addon MANAGER" and you are replying NO to BOTH, so you are starting FSX without them ?
All I did in the beginning was run the "live" update (when I already had the latest COUATL manager installed), and then this FSUIPC issue started.
Again, we don't have any interaction with FSUIPC. Not only that. If with "Live Update" you mean the one the program says it can be applied without restarting FSX, it doesn't even *install* a new Couatl or a new Addon Manager! It JUST updates the GSX code, which run entirely separate from FSX, under you EXISTING Couatl.exe interpreter so "JUST" running the Live Update, by itself, CANNOT cause any problems with FSX or any of the 3rd party modules you might have installed.
If you seen this after the "Live Update", and only did THAT (running it), your FSUIPC issue doesn't have anything to do with it, and it happened at that time only by coincidence.
But it all started when I started a flight in FSX and the COUATL "live" popped up and said to download the latest version....even though I already had v.3.0.0.9. installed. I even removed the FSX.cfg file and let it rebuild but no luck.
We haven't done a MAJOR update. The MAJOR update is the one that tells you to EXIT from FSX and download and install the latest Stand-Alone Addon Manager. We ONLY made a minor update recently, the one that says you can apply it without restarting FSX.
So, either you weren't updating since several weeks, or you shouldn't have seen the MAJOR update prompt.
Not that this would cause in problems if you do. But if you do it, be sure you turn off all firewall and antivirus, otherwise it might not be downloaded correctly.
-
Uhg man I don't know. This is very frustrating. I have no FSDT products installed and FSUIPC v 4.947 won't install without this error popping up now. I need to figure this out first, then deal with the FSDT install. The strange thing is I never had this error until I installed the COUATL stand alone manager 3.0.0.9. I didn't realize the "live" update was separate. Even so, I need to get FSUIPC working first. I do have firewall/defender turned off. Again can someone confirm using the latest FSUIPC without any issues in FSX (not FSX:SE)? It's version 4.947. Thanks.
-
I have no FSDT products installed and FSUIPC v 4.947 won't install without this error popping up now. I need to figure this out first, then deal with the FSDT install.
Just to be sure about this, do as follows:
- Install any FSDT product, not necessarily a product, just the Stand-Alone Addon Manager
- As soon as you installed it, go into the Windows Control Panel and remove it, and be sure you reply YES to these questions:
"Do you want to remove the Addon Manager ?"
"Do you want to remove the Couatl scripting engine ?"
THIS is a real removal, because it will also remove the modules so, if you are still are having issues with FSUIPC after this step, you can be sure the problem is happening entirely within FSUIPC and it's not, for example, an issue like a *conflict* with it and our modules, which I never heard of, but is not something that can be excluded.
-
OK well this is exactly how I have removed the stand alone manager so strangely this has now somehow become A FSUIPC issue. I have sent Peter a message hopefully he will respond soon.
-
OK well this is exactly how I have removed the stand alone manager so strangely this has now somehow become A FSUIPC issue.
I asked because I wanted to be sure of it.
If this is the case, then Yes, I guarantee that, if you replied YES to both the above questions about removing the Addon Manager and the Couatl scripting engine, both modules are disabled from loading in the EXE/DLL.XML files and are also physically removed from the hard drive so there's no chance for them to still have any effect on FSX.
-
I started to have the same problem AFTER I installed GSX. FSX-SE crashed every time I went to exit out of it. After I uninstalled GSX the problem went away. I reinstalled GSX and the problem came right back. I updated GSX and no change. Uninstalled GSX again and the problem went away. This is CLEARLY a problem with GSX. It seems like GSX is interfering with all of the other add-on dll's in FSX, because every crash upon exit creates a different windows event involving a different add-on dll in FSX. Any help please would be appreciated, and with out the same cockiness (our products are perfect etc), just acknowledge that there is a problem with GSX and FSX/FSX-SE and fix it please.
Jeremy
-
I'll post this here simply because it seems to be somewhat consistent with what I'm seeing.
P3D V3.4. Everythng ran fine and has for months until I unistalled the FB KIAD when it came out and uninstalled/deactived the version that was running the FSDT installer.
Now, when I select an FSDT airport I get the the following:
Couatl Scripting Engine for FSX/ESP has stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: Couatl.exe
Application Version: 3.2.0.3883
Application Timestamp: 5a1ee90a
Fault Module Name: VCRUNTIME140.dll
Fault Module Version: 14.0.24212.0
Fault Module Timestamp: 57869168
Exception Code: c0000005
Exception Offset: 0000e352
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
The interesting thing is that if I open the KPHX FB scenery, which is still using the FSDT installer it opens fine. This is true even after rerunning the Live Updater to make sure that the latest Couatl stuff has been loaded. Before I crash the system by loading an FSDT scenery all of the items in the Add On menu are there as shown in the attached screenshot.
Another interesting thing is that when I uninstall a scenery, (KLAS for example) I get the prompt on removing the Addon Manager but DON'T get the prompt to remove the Coautl one. Even when I remove KPSX (which does load) I don't get the Coautl prompt.
Everything shows correctly in the Scenery Library.
This computer is dedicated to flight sim and has no anti-virus installed.
Any suggestions?
Jon
-
Your screenshot shows you have several things outdated, because you are running SODE 1.4.2, and GSX won't even install, if you don't have the latest version, and will prompt you to uninstall the old one.
- Uninstall SODE 1.4.2
- Download and install the latest version of every FSDT product you have. Don't use older installers.