FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: nigelgrant on February 01, 2012, 04:33:42 am
-
Since installing GSX I have lost all airport buildings at Geneva, Zurich, Honolulu, Hawaii 1&2. Tried re-installing Geneva but did not make any difference
Nigel
Vancouver
-
As usual, whenever you have problems, always install the Stand-Alone Addon Manager. In this case, reinstall GSX first and then the Stand-Alone Addon Manager.
If you still have issue, don't do anything and report back.
-
My note was incorrect, I didn't uninstall Geneva, I deactiveted it then restarted FSX and reactivated Geneva; if you don't reply otherwise I will try your advise.
Nigel
-
I have lost my Honolulu buildings when I uninstalled GSX (with the keep Coutl option). Only way I have to now see the buildings is to re-install GSX. How can I get my buildings back without GSX?
-
I have lost my Honolulu buildings when I uninstalled GSX (with the keep Coutl option). Only way I have to now see the buildings is to re-install GSX. How can I get my buildings back without GSX?
Hi Like Umberto said you can install the stand alone add-on alone manger make sure the anti virus programs are not blocking it. http://www.fsdreamteam.com/products_phnl.html its right at the bottom/ below of were it says download fsx version the link is there.
-
Mine all fixed.
Looks like teh GSX installer did some magic.
Hope you get those pesky buildings fixed.
-
I am not having these problems with my other payware products.
I shelved the FSDT airport products and sadly won't buy GSX, my loss but till they fix this COMMON no building issue I refuse to continue buying their products.
You don't have such issues with other sceneries, because they don't have any features that require a software module to run, and the reason it's not the modules are bugged, but you have a PROBLEM in your system config, or ANOTHER product (antivirus, most common) that is preventing the software to run.
Once the cause is removed, you'll have the modules working without the need for any change in our software, which means it was already correct from the start.
The troubleshooting steps are not normally needed, but they are necessary to understand WHAT is causing the modules not running on YOUR system. There's no such thing as a common "no building" issue, the final effect (no buildings) might appear to the same, but the possible causes are many, which is why we can't just offer an universal solution, but we first need to know what, of the many possible causes, is the one the causes the problem on *your* system.
-
When you say to reinstall GSX Umberto, do I uninstall it first then reinstall or just reinstall overtop of my current install?
-
It doesn't really make much difference, you can usually reinstall without uninstalling first.
But if you uninstall, and reply YES to the questions "do you want to remove the Addon manager?" and "do you want to remove the Couatl engine?", there will be more clean up made, which might fix some issues.
-
Sounds good, thank you! This GSX is absolutely incredible. Just loaded up SWA 2986 and on to KSFO.
-
As usual, whenever you have problems, always install the Stand-Alone Addon Manager. In this case, reinstall GSX first and then the Stand-Alone Addon Manager.
If you still have issue, don't do anything and report back.
No luck I am afraid. I uninstalled Geneva, GSX and Addon Manager. Re-installed Geneva, GSX and the downloaded Addon Manager, with anti-virus disabled. No buildings at any FSDT airports, only jetways are showing.
Gor the following three messages duringthe installation process:
"Problem downloading AFD scenery list"
"There was a problem updating some sceneries, please try again later"
"Problem downloading Coautl plugins list"
Nigel
-
Already discussed here:
http://www.fsdreamteam.com/forum/index.php?topic=5518.0
The errors are not a problem, and don't have anything to do with your issue.
-
I seem to be getting nowhere fast; I still have no airport buildings in any of my FSDT sceneries – Geneva, Zurich, Honolulu,
Hawaii 1&2.
I stripped my scenery cfg file of all addon sceneries and left the FSDT sceneries and default only. Still no airport buildings.
Coautl did not show up in my addons menu.
Strangely, I found an extra Virtuali AddonManagerX, dated 2010 in My Programs and Features folder so I uninstalled that and left version 2.9.0.1 in place. Still no airport buildings.
So I uninstalled this 2.9.0.1version of AddonManager, and re-downloaded it from your website. I disabled my anti-virus (ESET) and reinstalled the AddonManager as administrator and there were no error messages as in my previous message, so the new download must have cured that, as you said it would.
During installation, Addon Manager and Coautl were entered into my Modules folder. I excluded the files bglmanx.dll and couatl.exe, in my antivirus as instructed, re-enabled my anti-virus, launched FSX to Geneva but still no buildings nor a Couatl entry in the addon manager menu.
My addon page within FSX is showing all 5 sceneries as installed and active, but strangely shows XPOI and GSX installed on a trial basis – I have not installed these, and GSX is showing up in the FSX/FSDreamTeam/Couatl folder.
But still no airport buildings, so what can you suggest now?
Nigel
Vancouver
-
My addon page within FSX is showing all 5 sceneries as installed and active, but strangely shows XPOI and GSX installed on a trial basis – I have not installed these, and GSX is showing up in the FSX/FSDreamTeam/Couatl folder.
So you DO have the Addon Manager in FSX, which means it's working. Do you also have the "Couatl powered products" menu too ?
-
but still no buildings nor a Couatl entry in the addon manager menu.
No, there is no "Couatl powered products" menu showing
Nigel
-
Have you been ASKED permission to run the Couatl module the first time you launched FSX after installing it ?
-
Have you been ASKED permission to run the Couatl module the first time you launched FSX after installing it ?
yes. this is the entry in the [Trusted] section of fsx.cfg
G:\FSX\fsdreamteam\couatl\couatl.exe.ntkebqwkckecnqeuaqznizzuqhblnezhlkaottzt=1
nigel
-
Let's see if it starts at lease, open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case l and a capital F )
Save the file as couatl.ini in the FSX\fsdreamteam\couatl folder, so it stays at the same level of the couatl.exe
Launch FSX, go to any FSDT airport, when it finished loading, exit from FSX, check if you have a Couatl.log file in the fsdreamteam\Couatl folder, and post its content here.
If you don't have the file, either be sure you followed this to the letter, or try running FSX As Administrator.
-
Is it couatl (lower caseL), or couat1 (number one)
Nigel
-
lower case couatl (L)
-
Let's see if it starts at lease, open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case l and a capital F )
Save the file as couatl.ini in the FSX\fsdreamteam\couatl folder, so it stays at the same level of the couatl.exe
Launch FSX, go to any FSDT airport, when it finished loading, exit from FSX, check if you have a Couatl.log file in the fsdreamteam\Couatl folder, and post its content here.
If you don't have the file, either be sure you followed this to the letter, or try running FSX As Administrator.
My original text couatl.log is still in the file couatl.ini which I created and put in the FSXroot/fsdreamteam/couatl folder, then launching FSX to Geneva as administrator
Nigel
-
Hello. I have tried what Umberto said in the second post in this topic, and I still have no buildings, runway textures, but I still have jetways. Any suggestions on what to do next?
-
Sorry guys, I had to be more clear: that command doesn't automatically "fix" anything, it's a way to instruct Couatl to produce a log file that contains some informations for us to understand why is not working correctly.
If you done it correctly, you should see a Couatl.log file in the FSX\fsdreamteam\Couatl folder, and you are supposed to post it here.
If you don't see the Couatl.log file, either you haven't followed the instructions, or Couatl hasn't even started, which most likely it's because has been blocked for some reasons.
This is usually caused by:
- The antivirus, which is STILL blocking them, even if you excluded them
- You might inadvertently un-trusted "Virtuali" on your system so, anything signed by us will be automatically refused to run.
To verify this, you can go to the Control Panel, under "Internet Options", look for the "Content" tab, there should be an "Authors" button, that will list the software authors that you trusted, and another tab with untrusted authors. If you see "Virtuali s.a.s", remove it from both tabs (especially if it's under untrusted)
-
Aha! My file extensions were off so my couatl.ini in fact was couatl.ini.txt and that is why it didn't work.
Now I have a logfile and it reads:
couatl v2.0 (build 2290)
log started on Fri Feb 03 12:27:47 2012
connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
-
Do you have the "Addon Manager" menu in the FSX menu bar ?
-
I've lost my airport buildings also with the installation of GSX, but couldn't begin to diagnose the problem or determine what is wrong. How do I uninstall GSX and regain my FSDT KDFW & KLAS airports?
-
Do you have the "Addon Manager" menu in the FSX menu bar ?
yes! On the FSX menu bar, the "add ons" menu includes "addon manager" which opens up to the various scenery activating options and configuration settings. But no Couatl menu anywhere.
Nigel
-
yes! On the FSX menu bar, the "add ons" menu includes "addon manager" which opens up to the various scenery activating options and configuration settings. But no Couatl menu anywhere.
Which is strange, because Couatl is running, at least is able to produce a Log. Just to be sure, try to remove the Log file you posted before, and launch FSX again, and see if a new Log is created after you exit. Just to check if Couatl is still running *now*
-
yes! On the FSX menu bar, the "add ons" menu includes "addon manager" which opens up to the various scenery activating options and configuration settings. But no Couatl menu anywhere.
Which is strange, because Couatl is running, at least is able to produce a Log. Just to be sure, try to remove the Log file you posted before, and launch FSX again, and see if a new Log is created after you exit. Just to check if Couatl is still running *now*
same as before:
couatl v2.0 (build 2290)
log started on Fri Feb 03 18:45:30 2012
connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
Nigel
-
For the folks who have no problem with GSX, I ask, "What anti-virus are you using?" If you are using Avast, what settings do you have?
-
OK, I got everything back. For me, with Avast, while reinstalling GSX, I had to turn off three functions: web shield, network shield. It was a major issue and I was still getting the danger/block message from Avast. I just kept hitting retry and eventually it all went in. Clumsy, but I have KORD back and GSX is working like a charm.
Cheers, hope it works for you.
-
Maybe the previous message of Dan Roman may give some clues. I use ESET NOD32 antivirus, which is popular with simmers because of its low resource usage. I have Windows7 64bit OS.
I went into my ESET log file, and since starting with the installation of GSX, every installation has a similar error message highlighted in red, under the threat column:
“a variant of Win32/Packed.EnigmaProtector.F potentially unwanted application”
-
We sent samples of our executables to ESET more than a month ago, no reply so far.
Unfortunately, not all antivirus companies are the same, some of them are very fast removing false positives, some aren't, which is funny in this case, considering that ESET it's an Italian company, one would think they shouldn't have much trouble contacting us...
-
BTW, I got my paid version running and did a flight from KBUR to KSFO in a CRJ.... surprised and happy at the presence of GSX, even for a small jet.... You have done a remarkable job!
-
For the folks who have no problem with GSX, I ask, "What anti-virus are you using?" If you are using Avast, what settings do you have?
Also, is there anyone using microsoft security essentials? That's what I'm using, and GSX ain't working for me. If there's anyone, please what are your settings?
THanks
-
Also, is there anyone using microsoft security essentials? That's what I'm using, and GSX ain't working for me. If there's anyone, please what are your settings?
This is what we use.
I normally exclude the whole FSX folder from scanning, but MSSE doesn't mistakenly flag our products as threats, even without *any* configuration, the only reason why I exclude the whole folder, is to speed up loading time.
-
Also, is there anyone using microsoft security essentials? That's what I'm using, and GSX ain't working for me. If there's anyone, please what are your settings?
This is what we use.
I normally exclude the whole FSX folder from scanning, but MSSE doesn't mistakenly flag our products as threats, even without *any* configuration, the only reason why I exclude the whole folder, is to speed up loading time.
Exactly what I have done. I excluded the entire FSX folder, to speed up loading time too. I've never received any flags either.
-
Umberto
I am not sure where I go from here, the lost buildings seems to be a problem for others as well as myself, and the couatl menu doesn’t appear to be showing up for lots as well. Are you working towards a resolution on this?
My five sceneries – Geneva, Zurich, Honolulu, Hawaii 1&2 were all working fine, until I installed GSX. Now these five sceneries do not show airport buildings, whether GSX is installed or not – and I would like to get these back.
It seems as though something in the GSX installation has messed things up. I did not get any feedback from you on the couatl log entry – start-up seemed to stall at “bglmanx” - non ready yet, waiting; does that mean anything to you?
Where do you see the status of this issue at the present?
Nigel
-
We believe it might be something related to the audio. Try to reinstall GSX, and then:
- Open the file at %APPDATA%\VIRTUALI\Couatladdons.ini with Notepad
look the section [gsx], there should be several parameters related to timings like refueling time, etc. after the last one, add the following:
Disable=1
And save the modified file back.
This will run all the latest Addon Manager/Couatl but with GSX DISABLED, which is the only plugin that try to use the audio card. If your sceneries will now run, it would then very likely your problem is caused by some issues with the audio on your system.
-
We believe it might be something related to the audio. Try to reinstall GSX, and then:
- Open the file at %APPDATA%\VIRTUALI\Couatladdons.ini with Notepad
look the section [gsx], there should be several parameters related to timings like refueling time, etc. after the last one, add the following:
Disable=1
And save the modified file back.
This will run all the latest Addon Manager/Couatl but with GSX DISABLED, which is the only plugin that try to use the audio card. If your sceneries will now run, it would then very likely your problem is caused by some issues with the audio on your system.
Tried this but still no airport buildings or couatl menu. The file already had a disable=0 at the start of the GSX section and I made it disable=1
Nigel
-
I have also lost the menu plus the airport buildings of my DSFT scenery.
I tried reinstalling the addon manager but it kept producing error messages when trying to replace exsisting files during the installation, such as
Deletefile failed: code 5
Access is denied
I have checked the file permissions, and they all show the correct permissions.
Rob
-
I tried reinstalling the addon manager but it kept producing error messages when trying to replace exsisting files during the installation, such as
Deletefile failed: code 5
Access is denied
That error code means you tried to run the installer too quickly after FSX was still closing itself so, it locked some files for writing. A Windows reboot will fix it.
-
I have also lost the menu plus the airport buildings of my DSFT scenery.
I tried reinstalling the addon manager but it kept producing error messages when trying to replace exsisting files during the installation, such as
Deletefile failed: code 5
Access is denied
I have checked the file permissions, and they all show the correct permissions.
Rob
You're getting that error code because the couatl process is still running even though you've closed FSX.To stop that error code, you need to open task manager and go to the 'processes' tab, then select the 'couatl.exe 32*' and click on end process. Then you can retry the installation
-
I tried reinstalling the addon manager but it kept producing error messages when trying to replace exsisting files during the installation, such as
Deletefile failed: code 5
Access is denied
That error code means you tried to run the installer too quickly after FSX was still closing itself so, it locked some files for writing. A Windows reboot will fix it.
For some reason, the couatl installed by either the new addon manager or the gsx never stops running until you close it with task manager or you log off windows and log back on/reboot. but that doesn't happen with any of the FSDT airports
-
I have reinstalled the addon manager once I followed the above instructions to ctop the Courtl process. I now have the Courtl menu back and the GSX services.
Thanks
Rob
-
Umberto
I am no further ahead, played around with disabling ORBX people mover entries in my dll.xml but did not make any difference - still no buildings nor couatl menu. Tried Windowed mode of FSX and clicked on coutl.exe but nothing happened.
What about the couatl.log entry about stall at “bglmanx - non ready yet, waiting" - I notice others' logs get beyond this. Is this telling us anything.
Would you recommend I uninstall my ESET anti-virus and install Microsoft Security Essentials, following on from another posting - my ESET is due for renewal in a week, maybe I should be abandoning it.
Nigel
-
If you have Couatl logging, it means it's running, so the antivirus is not a problem. I'll send you a special version of the Addon Manager to check via PM.
-
Sorry to say, but I also have lost all my buildings (PHNL, Hawii 1+2, KDFW, LSZG) after GSX (trial) install.
In my case, however, Addon Manager and Couatl powered products menus are present in FSX. Above sceneries result active.
Also after deinstallation of GSX and reboot still no buildings. I ran updater for Addon Manager and Couatl but no change.
During installation antivirus was disabled, now FSX-folder is permanently excluded from scanning.
Thanks for any help
-
Sorry to say, but I also have lost all my buildings (PHNL, Hawii 1+2, KDFW, LSZG) after GSX (trial) install.
First, download install the Stand-Alone Addon Manager after all the scenery NOW, and see if it changes.
If not, open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case l and a capital F )
Save the file as couatl.ini in the FSX\fsdreamteam\couatl folder, so it stays at the same level of the couatl.exe
Launch FSX, go to any FSDT airport, when it finished loading, exit from FSX, check if you have a Couatl.log file in the fsdreamteam\Couatl folder, and post its content here.
If you don't have the file, either be sure you followed this to the letter, or try running FSX As Administrator.
-
Umberto, I have followed your indications. FSX is started as Admin by default. No buildings yet. GSX was/is NOT installed
Here comes the couatl.log
Peter
-
I have my buildings back ! I checked a lot of things and found a corrupt FSX.cfg with an invalid entry for the SimObjects\Misc folder. Sorry for trouble!
I installed also GSX and it seems working, but it's too late now for more ....
During my troubleshooting I noticed some strange entry in my fsx.xml : Couatl results twice, once with short path, another with full path ( I attach the file ) - Is this normal and correct or should it be one entry only?
Grazie, Peter
-
During my troubleshooting I noticed some strange entry in my fsx.xml : Couatl results twice, once with short path, another with full path ( I attach the file ) - Is this normal and correct or should it be one entry only?
No, it's not normal, you must have added the long path version yourself while trying, and forgot about it. Just leave the short path version.
-
Umberto
I hope this uploads the file for you
Nigel
-
I hope this uploads the file for you
You said your problem was fixed, and your log is absolutely normal, is there a reason why you wanted to be looked at it ?
And besides, it's best if you reinstall the Addon Manager, because the logging version of the .dll is slower and generate a log file that could take a lot of hdd space if you fly for more than a few minutes so, it's best not using it normally.
-
I hope this uploads the file for you
You said your problem was fixed, and your log is absolutely normal, is there a reason why you wanted to be looked at it ?
No - my problem is not fixed, I started this thread on February 1 but many others have joined it. If you track the Nigel entries, I have no buildings on any of my airports nor do I have the couatl menu. I posted my couatl log which stopped at bglmanx
Nigel
-
If you track the Nigel entries, I have no buildings on any of my airports nor do I have the couatl menu. I posted my couatl log which stopped at bglmanx
Sorry, I must confused you with Pooch.
In any case, the bglmanx.log only show the two programs can't talk to each other. Are you sure the antivirus is not blocking Couatl now ?
To verify this, remove the Couatl.log you had, and launch FSX again, exit, and see if a new log is produced.
-
If you track the Nigel entries, I have no buildings on any of my airports nor do I have the couatl menu. I posted my couatl log which stopped at bglmanx
Sorry, I must confused you with Pooch.
In any case, the bglmanx.log only show the two programs can't talk to each other. Are you sure the antivirus is not blocking Couatl now ?
To verify this, remove the Couatl.log you had, and launch FSX again, exit, and see if a new log is produced.
Here are the contents of the Couatl.log - seemed to get a bit further this time. ESET was coming up for renewal next week so I uninstalled ESET and installed Microsoft Security Essentials to give it a try - I have excluded the FSX files from the MSE scanning.
Couatl.log content:
couatl v2.0 (build 2290)
log started on Tue Feb 07 08:28:04 2012
connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
Nigel
Vancouver
-
Please do another log for bglmanx too, with the changed situation.
-
Please do another log for bglmanx too, with the changed situation.
Here it is
Nigel
-
Umberto
I now have Microsoft Security Essentialls installed, and have uninstaled ESET AV including using the clean out file for NOD32 - I turned off the anti-virus protection and the Windows Firewall, then I uninstalled GSX and the Virualli AddonManager, rebooted the computer then reinstalled GSX and reinstalled the stand-alone Addon Manager, started up FSX to Geneva and still no buildings and no couatl menu or options.
I have turned antivirus and firewall back on, and I have attached a zip file of the bglmanx.log created with your special bglmanx.dll file in the FSX root folder.
Where do I go from here I seem to have reached an impasse? Windows 7 64bit
Nigel
Vancouver
-
Have you uninstalled by replying YES to the question "Do you want to remove the Addon Manager" and YES to the question "Do you want to remove the Couatl engine ?"
If yes, have you been ASKED permission to run the Couatl module the first time you launched FSX after installing it ?
If no, uninstall again and be sure you reply YES to the question "Do you want to remove the Addon Manager" and YES to the question "Do you want to remove the Couatl engine ?", and note if you are asked permission to run the Couatl module the first time you launched FSX after installing it
If you are, try to do also a Couatl.log too, as explained before.
-
Have you uninstalled by replying YES to the question "Do you want to remove the Addon Manager" and YES to the question "Do you want to remove the Couatl engine ?"
YES both times
If yes, have you been ASKED permission to run the Couatl module the first time you launched FSX after installing it ?
YES but also asked to run the AddonManager
If no, uninstall again and be sure you reply YES to the question "Do you want to remove the Addon Manager" and YES to the question "Do you want to remove the Couatl engine ?", and note if you are asked permission to run the Couatl module the first time you launched FSX after installing it
If you are, try to do also a Couatl.log too, as explained before.
No buildings and no coualt menu options.
But there are entries in the MODULES section of the FSX.cfg file for both the ADDON manager and couatl
The couatl log is shortened again, seems to stop at bglmanx, here is its entry
couatl v2.0 (build 2290)
log started on Wed Feb 08 17:11:54 2012
connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
Nigel
-
We are reading your message, no need to bump anything, we are trying to figure out your problem, which is quite unusual.
-
We are reading your message, no need to bump anything, we are trying to figure out your problem, which is quite unusual.
thx, Umberto
-
Could you check if you have two copies of the Couatl.exe process in the Task Manager ?
-
Could you check if you have two copies of the Couatl.exe process in the Task Manager ?
There is no Couatl.exe process showing in the Task Manager when I put FSX in windowed mode; I try starting Couatl.exe directly through a shortcut on the desk-top with FSX in windowed mode, and there is still no Couatl.exe process showing in the Task Manager (nor is there any Couatl entry in the addon manager menu bar of FSX).
Do the logs show what might be stopping it to start?
Nigel
-
Keep the Taskmanager open, launch FSX and try to not if Couatl.exe launches at least for a brief moment.
Or, try to enable The Simconnect diagnostic mode: open notepad, and copy the following text:
[SimConnect]
level=normal
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files
At the next FSX launch, you should see a text window with diagnostic message, that should tell what's going wrong. Let me know what you are getting, so we can have an idea what's happening.
Only the first few lines are important: if the window scrolls too fast, you can use the "Pause" key on the keyboard to pause the scrolling. Post here only the first 10 lines or so of the diagnostic, but it's important you post the first 10 lines.
-
Keep the Taskmanager open, launch FSX and try to not if Couatl.exe launches at least for a brief moment.
Or, try to enable The Simconnect diagnostic mode: open notepad, and copy the following text:
[SimConnect]
level=normal
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files
At the next FSX launch, you should see a text window with diagnostic message, that should tell what's going wrong. Let me know what you are getting, so we can have an idea what's happening.
Only the first few lines are important: if the window scrolls too fast, you can use the "Pause" key on the keyboard to pause the scrolling. Post here only the first 10 lines or so of the diagnostic, but it's important you post the first 10 lines.
Umberto
Attached are two screen shots - first is the Task Manager - couatl.exe appeared for about 2 seconds; second is the first pasge of the Simconnect log. Hope they tell you something!
Nigel
Vancouver
-
Umberto
Attached are two screen shots - first is the Task Manager - couatl.exe appeared for about 2 seconds; second is the first pasge of the Simconnect log. Hope they tell you something!
Nigel
Vancouver
Here is the first screen shot, they were too large for a single upload
Nigel
-
Keep the Taskmanager open, launch FSX and try to not if Couatl.exe launches at least for a brief moment.
Or, try to enable The Simconnect diagnostic mode: open notepad, and copy the following text:
[SimConnect]
level=normal
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Microsoft Flight Simulator X Files
At the next FSX launch, you should see a text window with diagnostic message, that should tell what's going wrong. Let me know what you are getting, so we can have an idea what's happening.
Only the first few lines are important: if the window scrolls too fast, you can use the "Pause" key on the keyboard to pause the scrolling. Post here only the first 10 lines or so of the diagnostic, but it's important you post the first 10 lines.
Umberto
Attached are two screen shots - first is the Task Manager - couatl.exe appeared for about 2 seconds; second is the first pasge of the Simconnect log. Hope they tell you something!
Nigel
Vancouver
Umberto
Any progress from these two screen shots I submitted?
Nigel
-
Any progress from these two screen shots I submitted?
They show both the Addon Manager and the Couatl exe loaded. However, your Couatl.exe is not the most current version (2290, it should be 2296) so, either you haven't installed the latest udpate we released 2 days ago. Try that one, and see if it makes any difference.
However, from your screenshots and your logfiles, both programs are running, but they just can't communicate, which seems to indicate something wrong in your Windows installation is happening.
Do you have other entries in your Simconnect.ini file, or you just created from scratch ?
-
Any progress from these two screen shots I submitted?
They show both the Addon Manager and the Couatl exe loaded. However, your Couatl.exe is not the most current version (2290, it should be 2296) so, either you haven't installed the latest udpate we released 2 days ago. Try that one, and see if it makes any difference.
I have 2296 but no change
However, from your screenshots and your logfiles, both programs are running, but they just can't communicate, which seems to indicate something wrong in your Windows installation is happening.
Do you have other entries in your Simconnect.ini file, or you just created from scratch ?
I did a copy and paste of your suggested entry
Everything was working fine until I installed the GSX, then all my buildings disappeared, so something got upset during the installation. What other areas should I be looking at for commands that might block couatl.exe from operating?
Nigel