FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: silenthunter183 on June 20, 2016, 05:28:17 pm
-
Hello. I'm kinda new here :)
I have a simple problem - after fully deinstalling and installing new GSX to version current on your website (1.9.9), FSX started to crash after booting up.
Looks like this
1. Installed GSX sucessfully
2. Started FSX via my shortcut (i made it to enable disabled windows colors - it's not the problem because i used it with earlier GSX updates and it worked)
3. After enabling scirpts (GSX first load) and loaded main menu, after 5-30 seconds FSX crashers to desktop. in column with file causing problem: "file:unknown"
I can't even load a flight, because it's crashing in menu. Strange, because that never happend before.
I did fully reinstall with addon manager and couatl.
Thanks for any help.
-
Hello,
Same issue for me after installing latest addon manager :(.
Skip.
-
Also i searched internet, and tried some reinstalls.
I also noticed that this is issue with addon manager, not GSX itself.
Also found that CTD occurs when I click first time outside of FSX screen. That's strange...
-
Same issue with me today. Initially I got an error that there was an issue with FSUIPC4.
https://www.dropbox.com/s/qcu6sti0lmebdkr/fsx_crash.jpg?dl=0 (https://www.dropbox.com/s/qcu6sti0lmebdkr/fsx_crash.jpg?dl=0)
However, I reinstalled GSX by not using the addon manager and then FSX was crashing to desktop whilst selecting any airport, aircraft, time or weather. There were no error messages available then. As has already been said, possibly the addon manager at fault?
-
Same trouble with me. It started with "Addon <unknown> is causing Couatl Scripting Engine to restart". After reinstalling the addon manager and/or reinstalling GSX, FSX crashes on startup. When deinstalling GSX FSX runs well (I hope this is still true). During my last try, I also got the FSUIPC error. Very strange - please help!
-
What has solved a lot of issues for me when updates come out is to make sure you are running the latest versions of all FSDT airports, stand alone and GSX. Which means, download everything you own again, and reinstall everything. No need to uninstall.
-
And if you don't have any other FSDT airport products?
-
There is a screen with crash and CTD log:
Opis:
Stopped working
Problem sign:
Name of the problem event: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61472.0
Application Timestamp: 475e17d3
Fault Module Name: unknown
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: ffb701b7
Version of operating system: 6.1.7601.2.1.0.256.28
regional settings ID: 1045
-
Sorry, but I can only repeat and confirm I cannot replicate ANY crash. Please be sure you download and install ONLY the latest version of EVERY FSDT product you have.
Be sure you turn off the antivirus when installing! It might block some downloads, and cause a big mess of old/new files mixed together which will surely crash the sim.
-
I have the exact same problem as the OP.
I have uninstalled all fsdt sceneries and downloaded the latest version of the addon manager x from the website.
FSX crashes just prior to the menu.
If bglmanx and cuatl are excluded in the exe.xml and dll.xml all runs fine.
Please advise what to do.
Thanks
-
I have uninstalled all fsdt sceneries and downloaded the latest version of the addon manager x from the website.
You don't say when. Please do it now and be sure your antivirus is turned off when installing.
-
I did it again just now with antivirus off and only addon manager enabled in the exe.xml and dll.xml.
To report back, it worked!
Thank you
-
To report back I still getting THE SAME CTD as before
I DID EVERYTHING:
1. Installed THE LATEST (from today, 10AM version) update fro FSFDT site version of GSX and Stand-alone.
2. Tried to move dll.xml to the Program Data folder - not worked (i have FSX, of course it's workaround for P3Dv3, but worth a try)
3. Fully disabled AV for all installations and updates.
4. Tried to change Headers with BOM and coding type (from win-1252 to UTF-8) in dll.xml and exe.xml. Not worked.
I only found that when moving Addon Manager entry in dll.xml to the top down, I don't get CTD FSX, but instead I'm getting blmanx.dll error and Simconnect_text() error. Tried ALL fixes for them - not worked.
So what's left? I'm really sad that I can't use that best addon for ground services :'(
-
I only found that when moving Addon Manager entry in dll.xml to the top down, I don't get CTD FSX, but instead I'm getting blmanx.dll error and Simconnect_text() error.
This indicates another addon is using an OUTDATED version of Simconnect that, when loading it first, will take over and let the sim stuck with it. That's why our installer always put bglmanx.dll on top of the DLL.XML, in order to prevent addons using outdated Simconnect to load their version first.
It's *POSSIBLE* this might be the reason of the crash: the two Simconnect versions are not working together. They are *supposed* to work together, using the Windows Side-by-Side loading (which allows two different .DLLs with the same name to run together in the same process), but sometimes this doesn't work, and everything start to misbehave.
Why some developers still insist using OUTDATED Simconnect version (who's using FSX RTM or SP1 nowadays ???), it's beyond me, since the XPack/SP2 version we use works with FSX+SP2, FSX+Xpack, P3D 1, 2 and 3...
As I've said, so many times already ( but nobody has replied to it ), if you have a repeatable crash, I really need to have a look at your system with Teamviewer, because we are still unable to replicate ANY crash so, the only possible explanation, is a conflict with an addon with don't know of.
PM-me to arrange this.
-
Thanks for the reply. I already have sent you two private messages, but I'm sure you have A LOT of work and stress with another people, so i'm going to be patient :)
This is the last log of updating FSUIPC (from yesterday) to check what simconnects i have:
Checking compatibility with installed SimConnect:
Found SimConnect build 60905 (Original)
Found SimConnect build 61242 (SP1 May07)
Found SimConnect build 61259 (Acc/SP2 Oct07)As you can see, I have simconnect from SP2, so that's not problem of not having it (But, how you said, problem is that older and newer aren't working together).
Thanks Umberto and regards.
-
As you can see, I have simconnect from SP2, so that's not problem of not having it (how you said, two simconnects don't work together).
It's BECAUSE you have several Simconnect together that you might have problems!
As I've said, when everything's working correctly, it IS ( better say "it should be" ) possible for two versions of the same .DLL to run together in the same process (this is called Windows Side-by-Side loading). However, this sometimes won't work and the following might happen:
1) Another addon using the old versions will load *before* others, and will let the sim being "stuck" on the old version, not trying to load ALSO the newer one, required by another addon (the Addon Manager *requires* the SP2 version), so this will result in the Simconnect_text() error message, because the Addon Mananger cannot find that API call, which has been added in the FSX SP1 version of the library, but apparently, an addon using the RTM (Original) version has prevented the sim from loading the newest ones together with the original one.
This can be FIXED by loading the Addon Manager first, which is what our installer does anyway, by placing it on top of the DLL.XML file.
2) Even if the problem of the Simconnect_text() error goes away, that doesn't ensure the two .DLLs won't cause other issues when loaded together in memory because, the whole point of the Side-by-Side system is they SHOULD have been loaded together automatically, without any need to re-arrange the loading order. Re-arranging the loading order only side-stepped the problem but, if Windows hasn't allowed to load them together for some reason, it's possible they *will* load, but *will* then crash once loaded, since something happened to your Windows install that prevented the Side-by-side system to work correctly.
Unfortunately, it's not a very reliable system, and even Microsoft is moving away from it: they used it for the VC++ runtimes libraries since 2005, now they went back to a non-Side-by-Side system for VC++ 2013 and up. But unfortunately, FSX is made like that, and nobody is going to fix it.
The REAL fix, to prevent all potential conflicts between modules, is that developers would STOP using the RTM or the SP1 version of Simconnect, and moved on the SP2/Xpack version, which is the latest for FSX. Hardly anyone is still using FSX RTM or FSX SP1, so I really cannot see why any developer would still need to support them.
-
Finally!!!
I have just installed GSX with fully disabled AVG and excluded FSX folder from scanning.
IT WORKED :D
So thank you Umberto for help - now I don't have any CTD.
Also to notice, I didn't installed stand-alone manager. I think that stand-alone was causing problems. Good to notice.
Just need to use ONLY this one from GSX.
Again thanks and regards.
-
Finally!!! I have just installed GSX with fully disabled AVG and excluded FSX folder from scanning. IT WORKED :D So thank you Umberto for help - now I don't have any CTD.
Of course it works...
99% of the issues we found ARE caused by the antivirus. We don't know what else we could do, other than supporting all the latest standards in false positive prevention (double digital signature, both by FSDT and by the software Taggant system), that some antivirus companies don't seem to support yet.
Also to notice, I didn't installed stand-alone manager. I think that stand-alone was causing problems. Good to notice.
Just need to use ONLY this one from GSX.
There's no difference whatsoever between the Stand-Alone Addon Manager and the Addon Manager included with the full GSX, they both download and install the same file from the same location. The only reasons of having a Stand-Alone Addon Manager, is to offer a smaller installer to download, compared to the full GSX.