FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Kjelle on November 28, 2014, 03:40:35 pm
-
Hello.
I installed today the latest Addon Manager update and after that FSX closed on. Whats wrong?
Kjelle
-
You are not alone Mate. I have lost this morning a very stable GSX v1.8.9.x by updating to GSX v1.9.
Maybe it it OS dependend. The former GSX was running under Windows XP SP3 with FSX SP2.
-
If FSX is QUITTING to the desktop without any errors (so it's not a crash), you are probably having the same problem discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,10489.0.html
-
If FSX is QUITTING to the desktop without any errors (so it's not a crash), you are probably having the same problem discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,10489.0.html
But with this we started this afternoon our Teamviewer session and found nothing. Just after working alone (with teamviewer connectable) everything went bad again.
After de-installing GSX v1.9 I see a running FSX SP2 on my desktop now for hours. But a pity w/o GSX avbl. :-((
-
Same problem here. Fsx gets to the cockpit then freezes for around 15 seconds and then we are back to desktop. Tried uninstalling, cleaning registry, rebooting, reinstalling and still the same. Runs fine without GSX. I have fs passengers and full fsuipc.
-
Still trying.....
If I start fsx and change aircraft from my normal/last choice before starting a flight then fsx will run. But if I try to change aircraft again after starting flight then back to desktop. If I try to change time of day after starting flight then back to desktop. Very unstable.
-
If I start fsx and change aircraft from my normal/last choice before starting a flight then fsx will run. But if I try to change aircraft again after starting flight then back to desktop. If I try to change time of day after starting flight then back to desktop. Very unstable.
Doesn't happen here. I just started a flight, and changed all the airplanes one by one, and of course no problems whatsoever. Again, as explained many times already, GSX by itself CANNOT cause an FSX crash, because it's run externally under the Couatl.exe interpreter so, in the worse case you will just lose the Couatl menu and GSX functions, but FSX cannot crash because of this.
If you have FSX crashing while flying, whatever is causing it, it's not GSX.
If you have FSX QUITTING silently AT START, that's the issue that I'm asking to check with Teamviewer.
If you don't have a crash anymore by uninstalling GSX, it might be a new conflict with another add-on and the Addon Manager, although the Addon Manager HAS NOT been updated with this GSX release so, if you had it working with previous GSX, you ALREADY had it, so it cannot be the Addon Manager either, which is the only program that can technically cause an FSX crash (again, Couatl/GSX CANNOT).
Please, provide a 100% replication steps, clearly indicating what you did, and ALL 3rd party products you used/selected, and in which order.
-
Since the update to the latest version that was recently released , Couatle is no longer visible in the addon's menu. I have uninstalled the program, then reinstalled with anti virus off then on also selected run as administrator and then off with out any success a few times now. GSX has always been stable for me until now. I am not getting any crashes to FSX but cannot get Couatle restarted after this latest update. I am running window 8.1 professional.
-
Since the update to the latest version that was recently released , Couatle is no longer visible in the addon's menu.
It's not entirely clear from your message, if the Couatl menu disappears while FSX is running, or it doesn't even start. If it doesn't even start, the most likely cause is the antivirus blocking it.
As explained, many times already, it's NOT enough to just install with the antivirus off, you MUST also configure it to exclude the following files from scanning:
YourFSXfolder\bglmanx.dll
YourFSXfolder\fsdreamteam\couatl\Couatl.exe
-
Same problem here also. since update can't get into fsx.
TeamView info pm sent. waiting on reply.
Hope tat fixes it.
UPDATE: I somehow got FSX to load, but after a few seconds it crashes to desktop with no error message so I also agree, a fix is needed.
-
Since the update to the latest version that was recently released , Couatle is no longer visible in the addon's menu.
It's not entirely clear from your message, if the Couatl menu disappears while FSX is running, or it doesn't even start. If it doesn't even start, the most likely cause is the antivirus blocking it.
As explained, many times already, it's NOT enough to just install with the antivirus off, you MUST also configure it to exclude the following files from scanning:
YourFSXfolder\bglmanx.dll
YourFSXfolder\fsdreamteam\couatl\Couatl.exe
I thought I was pretty clear and concise in my message. Furthermore I have configured my anti virus to exclude the above. It was my oversight not to mention that in the original thread; however it does seem I am not the only one experiencing this issue and a fix is needed. You don't have to be arrogant because something has been explained already. I am not getting FSX crashes.
-
Since the update to the latest version that was recently released , Couatle is no longer visible in the addon's menu.
It's not entirely clear from your message, if the Couatl menu disappears while FSX is running, or it doesn't even start. If it doesn't even start, the most likely cause is the antivirus blocking it.
As explained, many times already, it's NOT enough to just install with the antivirus off, you MUST also configure it to exclude the following files from scanning:
YourFSXfolder\bglmanx.dll
YourFSXfolder\fsdreamteam\couatl\Couatl.exe
I thought I was pretty clear and concise in my message. Furthermore I have configured my anti virus to exclude the above. It was my oversight not to mention that in the original thread; however it does seem I am not the only one experiencing this issue and a fix is needed. You don't have to be arrogant because something has been explained already. I am not getting FSX crashes.
I've also the same experience and I know very well what I must to do with the FSDreamTeam products. For now I've completely deinstalled all the FSDreamTeam airports and GSX otherwise I was unable to run FSX or P3D v2.4. Before GSX 1.9 everything was running smoothly on my computer (W7 64 Bits). I suspect a problem with Couatl and not GSX because I've already tried to reinstall an airport and the same problem still occurs.
So I'll wait patiently till a solution will be find ;)
Best Regards
Marc
-
I thought I was pretty clear and concise in my message
No, you weren't. You said you installed with the antivirus off, which is not enough, which is why I added the information that you MIGHT need that WAS missing from your post.
Furthermore. I have configured my anti virus to exclude the above. It was my oversight not to mention that in the original thread
That's what I meant...
however it does seem I am not the only one experiencing this issue and a fix is needed.
Your issue doesn't even have anything to do with this thread, which is about ONE thing: FSX closing/crashing when the new Addon Manager is installed while, according to your own report, you lost the Couatl menu with no FSX crashes.
Entirely different, and there's nothing to "fix" in both cases, I'll be able to tell you what the real cause is in your case, when'll post a clear answer.
I am not getting FSX crashes.
That's also what I've said about your report being unclear. You said: "Couatl is no longer visible in the addon's menu", so I'll repeat my question again: It's not entirely clear from your message, if the Couatl menu disappears at a certain point while FSX is running, or it doesn't even start. If it doesn't even start, the most likely cause is the antivirus blocking it.
I said "the most likely cause" it's the antivirus, which was an entirely legitimate answer, consider you haven't said if you HAD configured it correctly or not, you just said you installed without the antivirus.
Now, assuming it's not the antivirus, it doesn't mean that my question if Couatl disappears after a while or not even appearing is not valid anymore, since "most likely cause", doesn't mean the ONLY cause. There are other less common causes for Couatl not starting at all, but it doesn't make any sense searching for them, if you don't reply to the original question about Couatl not even starting, or disappearing after FSX starts.
Furthermore, since as I've said this thread is about FSX closing and NOT about "Couatl disappearing", by posting your issue here, you are just making this thread more confusing for everybody to follow.
So, after you checked if Couatl doesn't start or if Couatl disappears, as I've asked, please OPEN A NEW THREAD with the proper title ( "Couatl doesn't start" or "Couatl disappears" ), so other users might find it easily in the future. Do not reply here, please, because your issue doesn't have anything to do with this thread.
-
:-\ I installed last Addon manager: lost of all Add-Ons, like FSUIPC,Sqawkbox,PMDG settings...and so on. PMDG MD-11 cannt be load (fsx crash), FS global weather cannt be load in fsx ::) HELP??
-
PMDG MD-11 cannt be load (fsx crash), FS global weather cannt be load in fsx
If it's just the MD11 or that other weather program crashing, I can't see how this could have anything to do with the Addon Manager or any of our products. Are the Addon Manager and GSX working now ?
-
Because after installing Addon manager everything ceased to operate. On the top sheet: Flights - Options - Addons.... / Addons: lost of fsuipc, squawkbox and many more. only addon manager and coualt (gsx settings) are still there. it has so much to do with it..
-
Because after installing Addon manager everything ceased to operate.
That's not what you said. You said the MD11 and the other weather program didn't load so, based on that report, it seemed that everything else is working. Now you are saying another thing.
On the top sheet: Flights - Options - Addons.... / Addons: lost of fsuipc, squawkbox and many more. only addon manager and coualt (gsx settings) are still there. it has so much to do with it..
Again, it doesn't have ANYTHING to do with this. What is really happening, is that your EXISTING DLL.XML file was probably ALREADY corrupted before installing GSX, usually because of hand-editing done wrong, or having edited with the wrong program (like Word or Wordpad, for example)
The GSX installer obviously CHECK the XML file, using the official XML validation library that comes with Windows. This is done for the obvious reason that, if we tried to modify an already-corrupted XML file, it would probably create even more problems.
So, if the validation test fails, because your XML file was already corrupted, the GSX installer will ASK YOU what you want to do. You have the option to either ABORT the installation, so you can try to FIX the file yourself, or to create a NEW XML file, that will surely correct, but will contain JUST the Addon Manager line.
You chose to create a new file, so your XML file has been recreated, that's why you only see the FSDT menus under the "Addons" menu.
OF COURSE, the installer ALSO created a backup, so you can restore you existing XML file, and try again, maybe you'll understand why it was already corrupted in the first place. You'll find the backup file in the %APPDATA%\Microsoft\FSX folder, alongside the current DLL.XML
-
i said this: I installed last Addon manager: lost of all Add-Ons, like FSUIPC,Sqawkbox,PMDG settings...and so on. PMDG MD-11 cannt be load (fsx crash), FS global weather cannt be load in fsx HELP?? .... and this: Because after installing Addon manager everything ceased to operate. On the top sheet: Flights - Options - Addons.... / Addons: lost of fsuipc, squawkbox and many more. only addon manager and coualt (gsx settings) are still there. it has so much to do with it..
because everything works fine before i instlled your super update. thx fo help.. forget
-
because everything works fine before i instlled your super update. thx fo help.. forget
I obviously helped you, because I TRIED to make you UNDERSTAND what the real problem was. You are confusing the cause with the effect.
The effect was that after you told the installer to create a new XML file (because you existing one had an error), you "lost all your addons", but the cause is NOT the GSX or Addon Manager installer, the cause was your already existing file corruption of one of your XML files.
because everything works fine before i instlled your super update.
And there's a reason for this which, again, you are mistakenly thinking there's something wrong with our installer, when there's isn't.
FSX is quite tolerant to syntax errors in the XML file. It will just skip the corrupted line so, you might not have a single 3rd party module, but maybe you haven't realized it.
But since we must MODIFY that file, we CANNOT risk touching something that is not 100% correct, because the result would be an even more corrupted files.
WHICH IS WHY, the installer checks the file BEFORE touching it, and will ASK YOU what to do. And if you allow to create a new file, it's normal and expected you'll lose all the existing installed lines if you do that.
WHICH IS WHY, the installer also create A BACKUP
Do you understand NOW ?
-
Hello,
I installed the latest Addon Manager update and FSX is quitting at start to the desktop without any errors.
I installed it without the antivirus and i configurate it to ecclude from scanning bglmanx.dll and Couatl.exe, FSX still quitting at start to the desktop without any errors.
My configuration: Fsx acceleration and Windows XP
do you have any solution ?
thank's.
best regards
-
Same problem for me. FSX seems to crash to desktop everytime I start injecting weather with ASE.
-
I installed it without the antivirus and i configurate it to ecclude from scanning bglmanx.dll and Couatl.exe, FSX still quitting at start to the desktop without any errors.
As I've already replied in this same thread, if FSX is QUITTING to the desktop without any errors (so it's not a crash), you are probably having the same problem discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,10489.0.html
So you must follow the indications in that thread.
-
Same problem for me. FSX seems to crash to desktop everytime I start injecting weather with ASE.
What "same problem" ? This thread discusses FSX quitting to desktop when it STARTS, so you can't even go to the first screen. Your problem is entirely different and there's no indication it has anything to do with GSX.
There was another thread on our forum, which reported a crash only when using Active Sky, which seemed to have been fixed by that user by resetting the FSX.CFG to default:
http://www.fsdreamteam.com/forum/index.php/topic,8301.msg67994.html#msg67994
And, there's another thread that discuss potential issues to be aware of when using Active Sky:
http://www.fsdreamteam.com/forum/index.php/topic,8849.0.html
-
Same problem for me. FSX seems to crash to desktop everytime I start injecting weather with ASE.
What "same problem" ? This thread discusses FSX quitting to desktop when it STARTS, so you can't even go to the first screen. Your problem is entirely different and there's no indication it has anything to do with GSX.
There was another thread on our forum, which reported a crash only when using Active Sky, which seemed to have been fixed by that user by resetting the FSX.CFG to default:
http://www.fsdreamteam.com/forum/index.php/topic,8301.msg67994.html#msg67994
And, there's another thread that discuss potential issues to be aware of when using Active Sky:
http://www.fsdreamteam.com/forum/index.php/topic,8849.0.html
Well, usually I start ASE prior to FSX, so I wouldn't know the difference. Just by chance I forgot to do it this time and tried again to be sure.
Fact is:
FSX, GSX and ASE worked perfectly together before the update. With the vehicle update and Addon Manager update, nothing worked anymore. With a complete new install of GSX and without ASE I am at least able to launch a flight. I will not ruin a FSX.cfg that works/worked perfectly and took like forever to build to its current condition. If that means to say bye-bye to GSX, so be it!
-
Well, usually I start ASE prior to FSX, so I wouldn't know the difference. Just by chance I forgot to do it this time and tried again to be sure.
Fact is: FSX, GSX and ASE worked perfectly together before the update.
Fact is, that NOTHING in the current GSX update can have any relationship with Active Sky, I can't see how adding de-icers could affect Active Sky. GSX reads the temperature, of course, so if Active Sky but it always read it even before,
With the vehicle update and Addon Manager update, nothing worked anymore
Installing the GSX vehicle updates and the Stand-Alone Addon Manager would result in having the same GSX files as the full installer.
With a complete new install of GSX and without ASE I am at least able to launch a flight
You said yourself what the real situation is: GSX is running normally without ASE. FSX is crashing with ASE. That's clearly indicates what's causing the problem
I will not ruin a FSX.cfg that works/worked perfectly and took like forever to build to its current condition.
I think you got it backwards: according to THAT user report, the FSX.CFG you don't want to "ruin" might be the CAUSE of the issue, perhaps a tweak you read about which shouldn't applied.
But that's besides the point. You don't have to "ruin" anything. The obvious course of action, to try that solution, would be:
- Create a COPY of your existing FSX.CFG and then remove it, or MOVE IT to a safe place, like your Desktop
- This will result in FSX recreating it from scratch, so at least you can TRY if your issue has anything to do with the FSX.CFG.
There might be only two outcomes out of this:
1) either this will fix the problem, like the other user in one of the linked thread did, so we can start looking WHAT tweak caused it, so you can get back your SAVED FSX.CFG and remove just the offending one
OR
2) it won't make any difference, so you can restore your existing FSX.CFG, and report back here that "it wasn't the FSX.CFG", so we might look for other solutions.
In BOTH cases, you'll never "ruin" your FSX.CFG
If that means to say bye-bye to GSX, so be it!
Do you realize that you could go to the Active Sky forum with this sentence of yours:
"With a complete new install of GSX and without ASE I am at least able to launch a flight"
And it would be entirely logical THEY would have to reply with some help, or you should say "If that means to say bye-bye to ASE, so be it!" ?
-
Apparently you overread the essential message I was trying to submit, which was the follwoing:
FSX, GSX and ASE worked perfectly together before the update. (of GSX)
That clearly indicates that GSX must have caused the issue. Not ASE or some tweaks I made to the FSX.cfg. If I go to the Active Sky Forums and tell them about the problem they will immediately send me back to you with close to 100% certainty. And why wouldn't they? They haven't changed anything for sure.
But just to please you, I will try with a rebuilt FSX.cfg.
EDIT: The problem persists. As soon as I launch ASE, FSX shuts down with the new .cfg.
-
That clearly indicates that GSX must have caused the issue.
This doesn't "clearly" indicate any of that.
It only indicates you are noticing a problem now, but there's no indication that it wasn't there before. You are assuming that it "must" be GSX, just because it has been updated, but that's an assumption, it could well be that something else changed in your FSX install, and you never got the chance to notice it before.
As soon as I launch ASE, FSX shuts down with the new .cfg.
THIS, instead, clearly proves the problem is caused by ASE. Would you like to try a Teamviewer session, so I can have a look at your system ?
-
I'm not a fan of the Teamviewer idea. How big is the chance, you can solve the issue by using it? BTW: ASE is off the hook, the CTDs occur also without weather.
-
I'm not a fan of the Teamviewer idea. How big is the chance, you can solve the issue by using it?
The obvious reason for asking to connect with Teamviewer, is that it happens only to you, so without having a look at your system and see what's REALLY happening on YOUR system, it's impossible to even start discussing a fix, which is not even sure (without looking at YOUR system) that is something that should be fixed in GSX in the first place.
Do you see hundreds of other users reporting the *same* problem ? Obviously not, that's why it's easier if you just let me check.
In the real world of IT support, getting remote assistance is considered a privilege, or something you pay for.
BTW: ASE is off the hook, the CTDs occur also without weather.
"without weather" is the same as "without ASE" ? Or, are you saying the "With a complete new install of GSX and without ASE I am at least able to launch a flight", sentence of yours wasn't accurate ?
-
I deinstalled GSX, downloaded a new copy, installed it and launched FSX. On the first attempt I didn't even get to the opening menu of FSX. On the second attempt I could start a flight, even activated GSX but after about 2 minutes FSX froze, just after the beep sound you hear after boarding is complete. ASE was inactive all the time.
I am of course thankful for your offer of remote assistance, but I have concerns about letting a stranger have access to my system. I will think about it and let you know.
-
about 2 minutes FSX froze, just after the beep sound you hear after boarding is complete.
Does the sound seemed to hang up ? Because, as I've said, GSX by itself CANNOT "froze FSX", since it's running entirely external to it so, the worse it can happen if GSX crashed or Couatl.exe crashed, is that you'll lose the Couatl menu and GSX won't work anymore, but that's it.
What CAN cause a crash, instead, might be a problem with your audio drivers, that's why now that you are mentioning sounds, I asked if it seemed the sound had problems, like not having being played entirely or being stuck, etc.
ASE was inactive all the time.
Inactive is not the same as disabled. Have you removed its .DLL module or you simply are letting it idling ?
Do you still have the crash you initially reported about FSX crashing "as soon weather is injected", like you reported before ?
ìI am of course thankful for your offer of remote assistance, but I have concerns about letting a stranger have access to my system. I will think about it and let you know.
That doesn't make any sense, you are not granting any permanent access to anyone: teamviewer is a program designed for remote assistance, the connection is possible only if YOU start the program, and nobody can connect anymore if the program is not running. On top of that, the session password is randomly generated for each new session so, even if you forget to quit from teamviewer, the password used for the previous connection won't work anymore.
-
Does the sound seemed to hang up ? Because, as I've said, GSX by itself CANNOT "froze FSX", since it's running entirely external to it so, the worse it can happen if GSX crashed or Couatl.exe crashed, is that you'll lose the Couatl menu and GSX won't work anymore, but that's it.
What CAN cause a crash, instead, might be a problem with your audio drivers, that's why now that you are mentioning sounds, I asked if it seemed the sound had problems, like not having being played entirely or being stuck, etc.
FSX didn't accept any commands, there were no movements anymore. The sound of the departing baggage truck was still to hear. About 20 or 30 seconds later, FSX crashed to desktop.
Inactive is not the same as disabled. Have you removed its .DLL module or you simply are letting it idling ?
Do you still have the crash you initially reported about FSX crashing "as soon weather is injected", like you reported before ?
ASE needs to be launched first to do anything. That was not the case during the last trials I made. But I haven't removed anything.
-
I have done all of the above and even removed all MS Visual C+++ and reinstalled them. Even the removal of the standalone and FSX and I still get the error. Can you remote me and see what is going on??? Paid good money for this program and can't even use it??
Thanks... ???
-
I have done all of the above and even removed all MS Visual C+++ and reinstalled them. Even the removal of the standalone and FSX and I still get the error. Can you remote me and see what is going on??? Paid good money for this program and can't even use it??
Thanks... ???
Can you be a little more specific with your problem? What "error" are you describing? Is FSX quitting to desktop?
-
I have done all of the above and even removed all MS Visual C+++ and reinstalled them. Even the removal of the standalone and FSX and I still get the error. Can you remote me and see what is going on??? Paid good money for this program and can't even use it??
You mean that when ACTIVE SKY is injecting weather, FSX freezes ? If yes, I hope THAT's the program you "paid good money for" you are referring to. And of course, since GSX is sold in Trial version, you have been given plenty of chances to verify with YOUR system and YOUR combination of other add-ons BEFORE purchasing it. That's the whole point of having a Trial version.
But yes, I would like to have a look at your system, PM me to arrange it.