FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Angelo on February 04, 2012, 09:15:15 am
-
I am having a slight problem with my Sim at the moment. I am noticing after I complelty close FSX to the desktop, my mouse pointer shows with a "Wait" cursor next to it, the blue circle. When I check my running programs in task manager I can see two Couatl 32 running in the list, and they refuse to close even if I try to end the task.
On a hunch I completely uninstalled GSX and the Addon manager along with Couatl and the problem went away. I could load and close FSX and the wait cursor would disappear when it should. As soon as I reinstalled it, the problem immediately came back.
The only way to get rid of the wait cursor is to reboot the machine.
Any ideas as to why this is happening?
Edit: I re-ran the sim and now when I check task manager again there are now 4 Couatl running in the list. This is after I shut down the sim and some time has passed. I am also unable to end the task forcefully so I am not sure what else to do.
Angelo
-
This shouldn't simply happen, and it's even less normal that you are not allowed to close it with the Task manager.
Maybe it's another addon that is preventing to close it, you might try editing your EXE.XML file located at %APPDATA%\Microsoft\FSX with a text editor, and try disabling all modules except Couatl.exe (set their <disabled>False</disabled> to <disabled>True</disabled> ) and see if the problem goes away.
-
Okay, I disabled everything except couatl.exe and the exe.xml. The problem is still there, what should I do next?
-
Okay, I disabled everything except couatl.exe and the exe.xml. The problem is still there, what should I do next?
Try to do the same with the modules in the DLL.XML, except the Addon Manager.
-
Okay I did that, and that seemed to have fixed the problem, now should I re-enable them? I will await your reply.
Right now I have items disabled in the exe.xml and dll.xml
-
Okay I did that, and that seemed to have fixed the problem, now should I re-enable them? I will await your reply.
Well, it seems the conflicting one is in the dll.xml, try to remove them one by one, launch FSX, test, and you'll eventuall find which one is causing this.
-
Okay so the culprit that was causing the wait sign to stay on turned out to be in the (exe.xml) file, not the dll.xml.
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>True</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
If I change the value back to False the problem comes back, if I leave it to True then everything is fine, however I would like to return it back to the way it originally was. Why is this happening, what else can I do?
Angelo
-
That is the main exe.xml section, if you set <Disabled>True</Disabled> for it, the whole file would be disabled, you should set it to False, and separately disable a single module one by one (except Couatl.exe) until you find if there's one that conflicts with it.
-
Trying now, will post back...
-
Okay it is Couatl that was the problem,
-
Okay it is Couatl that was the problem,
You are trying to understand why Couatl doesn't close automatically, if you disable it entirely, it will not even *START* to begin with so, how can that "fix" Couatl not closing ???
Sorry, but you must have overlooked something else which hasn't been deactivated, because Couatl closes just fine.
Try a Windows reboot, and redo all the DLL.XML test and all the EXE.XML test. DO NOT ever disable the Addon Manager or the Couatl program otherwise the whole test would lose any meaning.
-
The problem is, is that I have to reboot my machine after every attempt to clear out the wait symbol. There are over 20 entries in the dll.xml file. What you are asking is extremely time consuming, and we can see that it is couatl that is the problem, I will try what you said, but it is strange that this problem all of a sudden came about as soon as I updated GSX through the User Interface. Maybe to save some time, I should try to un-install and re-install?
-
The problem is, is that I have to reboot my machine after every attempt to clear out the wait symbol
No, you don't. You can simply kill the Couatl.exe in the Task Maanger after each try,
.we can see that it is couatl that is the problem,
No, it's not. You still don't understand what I've said: you haven't found Couatl is the problem, you have *disable* it, how it can possibly stop not being closed, if it hasn't even STARTED ???
I should try to un-install and re-install?
Just do what I said, go through EACH module in the DLL.XML and test one by one, until you find the conflicting one, and then do the same for the EXE.XML. DO NOT ever disable the Addon Manager or the Couatl program otherwise the whole test would lose any meaning.
You don't need to reboot Windows after each try, but do at least one reboot before starting. At every test, you can just terminate the Couatl.exe process with the Task Manager.
-
I am unable to end the task couatl in task manager though, each time I try it says "The operation could not be completed." "The operation is not valid for this type of process."
-
^^^^ Bump.
-
Something is not right on your system, because I can terminate the process just fine.
-
Just posted about the exact same problem in another thread before I saw this thread...obviously something changed in the latest update since I've never seen this problem before and my problem is EXACTLY the same as described here so at least there are more than one with the same problem after the latest update.
Any progress on finding out what is causing this odd behaviour of couatl.exe?
(I'm actually having the spinning "wait" cursor right now as I type this post since I still haven't restarted my PC after closing FSX...)
-
I will try to uninstall GSX along with Couatl, and Addon Manager reboot, and then download and install the latest GSX and Standalone Addon Manager and report back.
-
I already tried that to no avail, however I didn't download GSX but used the downloaded setup file I already had on my PC. Did download the Standalone Addon Manager though.
-
As I've said already (in another thread, are we supposed to continue on both threads ? Maybe it's best if you stop posting there, since this is titled appropriately for your problem), have you tried after a Windows reboot ?
-
You're right, this thread is better and yes...as I already posted in the other thread I've tried rebooting several times and when doing that the problem of course goes away but as soon as I start FSX the problem is back.
-
So, the first FSX after a reboot, everything works normally, but if you close FSX Couatl doesn't close automatically, and you can't even close it manually with the Task manager ?
Since it works on the first launch, have you checked if the Audio setting panel is saying something about problems with the audio, as I've asked before ?
-
^^ Yes this is exactly how my situation is as well. However as soon as I launch FSX from a clean reboot and before even selecting a flight, I get the "Wait" symbol when it should normally be just a mouse pointer, since by now everything would have been loaded. Otherwise exactly as you described Umberto, is how I am experiencing it, unable to end task with task manager.
Edit: this is after a full re-install of GSX and the latest standalone addon manager as well. (With Anti-Virus Off)
Here's what the Task Manager looks like, and notice the CPU is loaded to 100% this is also very unusual.
]http://imageshack.us/photo/my-images/29/couatl.jpg/]]http://imageshack.us/photo/my-images/29/couatl.jpg/]]http://imageshack.us/photo/my-images/29/couatl.jpg/] (http://imageshack.us/photo/my-images/29/couatl.jpg/)
-
I am able to close it via the task manager...but I am in the same boat...as if I want to close FSX and then fly again later...I always have to go to the task manager, and close the process before I start up again...otherwise it won't start with the sim.
-
Something has to be wrong here, I am not even able to open the Error log in the Virtuali folder on my C drive. The err file is 188,946KB in size, and as soon as I open it notepad freezes. Also after I close FSX and Couatl stays running all 4 cores on my CPU are at 100% pinned with no fluctuation. I am really at a loss right now.
-
Maybe the problem is the log file itself, try too reboot Windows and remove it before launching FSX.
-
Okay I did that, the problem still exists. Also, the new ERR file has been generated and continues to grow by 1KB per second as long as the program is running. So looking at the file closed in the Virtualli folder the size will go from 330, 331, 332, 333, 334KB on upwards every second until I physically stop by turning off the PC.
-
Wow, I just got the ERR file to open finally! Turns out....
couatl v2.0 (build 2290)
panic log started on Wed Feb 08 23:03:32 2012
error in config file C:/Users/Angelo/AppData/Roaming/Virtuali/CouatlAddOns.ini: no value given in 'disable_on_airports ='
I must have deleted one line too many here, as soon as I put KLAS back in the list because I use AES there, the wait sign disappeared and CPU load went back to IDLE. Wow go figure that.
Sorry for being a pain Umberto, but I am really glad yo stuck around to help me out on this one, I appreciate your help.
Now I can return to HAPPY SIMMING!
Angelo
-
So, the first FSX after a reboot, everything works normally, but if you close FSX Couatl doesn't close automatically, and you can't even close it manually with the Task manager ?
Since it works on the first launch, have you checked if the Audio setting panel is saying something about problems with the audio, as I've asked before ?
No, it doesn't work the first time...as soon as I launch FSX I get the waiting cursor just as described by others and as I said in my previous posts both in this and the other thread.
And no, I can't close couatl via the Task Manager as trying to do so will give me the error message I already posted.
-
error in config file C:/Users/Angelo/AppData/Roaming/Virtuali/CouatlAddOns.ini: no value given in 'disable_on_airports ='
I must have deleted one line too many here, as soon as I put KLAS back in the list because I use AES there, the wait sign disappeared and CPU load went back to IDLE. Wow go figure that.
Ah!
That's it, there's a reason why the installer by default puts disable_on_airports = None by default, because an .INI with a key and no value after the = sign it's illegal, and would confuse the .INI parser that comes with the standard Python language, but since the disable_on_airports key is NOT rewritten by the installer after running it again (in order to keep your excluded airports list), if you corrupt it once, it will stay that way.
In theory, there must be some code to deal with that special case, but maybe it's not working now.
-
This is great news :-)
Will check my ini file as well and hope I can fix it the same way!
-
I'm happy to tell you my problem is solved as well by adding None to the ini file, great find!!