Couatl.exe not appearing in my FSX menu - HELP

[DMullert]

Hello Team!

I am at wits end with KJFK V2 not installing correctly.  This is the first scenery from FSDT I've purchased that has given me headaches.  I've read the forum posts and I see others have experienced the same issue.  The situation is this:

1. I am able to install KJFK V2 and properly activate it in my computer.
2. Addon Manager is present in my FSX menu and all corresponding products I have purchased appear properly activated.
3. Couatl is not present in my menu.
4. I have de-activated and de-installed the scenery several times.  I have turned off my antivirus (ESET NOD32).  I have added couatl.exe and bglmanx.dll to the antivirus exclusions as suggested in the forums.  I have re-downloaded the FSDT installers with the AV off and re-installed with the AV off and the same situation takes place.  KJFK shows no buildings, scenery, runway marks, or lights.
5. Perhaps there is a separate download for Couatl??
6. I am using Windows 7SP1 64bit

Please Help!

Thanks!

[virtuali]

Have you been asked permission to run the Couatl program when you first restarted FSX after installing JFK V2 ?

If not, do all the following, don't skip ANY step:

- DOWNLOAD AND INSTALL with the antivirus entirely OFF

- Uninstall the scenery. Reply YES when asked if you want to remove the Addon Manager and the Couatl Engine. Reply YES to both questions.

- TURN OFF your antivirus. Don't just exit from its interface, but turn off the real time protection. Actual wording changes between products, however, it's the option to scan every file that gets open in real time, without user intervention.

- Reinstall the scenery with the Antivirus TURNED OFF. Don't launch FSX yet.

- Configure the antivirus to exclude the following files from scanning:

YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\Couatl\couatl.exe

YourFSXFolder it's usually C:\Program Files\Microsoft Games\Microsoft Flight Simulator X, if you installed it in the default folder.

- Now you can turn the antivirus back on, and launch FSX.

- Check you are seeing BOTH the "Addon Manager" menu AND the "Couatl powered products" menu under the "Addons" menu.

Pay attention if you are being asked permission to run BOTH modules after you launch FSX after this entire procedure.

[DMullert]

Hello Humberto!

Thanks for your reply Mate!  I have done what you've suggested several times already as a result of the same response you gave another user in a previous post.  During the installation process, I keep getting a message saying "There was a problem updating some sceneries, please try again later"; for some reason the installer is looking for an AP_LSGG.bgl scenery file but I do not have that scenery ionstalled - I've never purchased LSGG so not sure why the installer is looking for that file.  FSX then asks me if I want to give permission for the Addon Manager to run and for Couatl to run - to which I respond Yes to both.  The Addon Manager gets activated without any problems and it appears in the menu but Couatl does not appear in the menu even though It's installed and with permission to run.  Is there maybe a separate install for Couatl we could try?  Could there be something preventing Couatl form running?  My antivirus software is ESET NOD32 and both Couatl.exe and BGLManx.dll have been excluded.  Any new ideas?

Thanks again!

[virtuali]

FSX then asks me if I want to give permission for the Addon Manager to run and for Couatl to run - to which I respond Yes to both.

you can activate the Simconnect diagnostic mode to see what's wrong with your install:

Open notepad, and copy the following text:

Code: [Select]

[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.

[DMullert]

Hello Umberto and Thanks again for your reply!

I've done as instructed.  Here are the first few lines of the file.  I have the entire contents of the file if needed.

> 13.57639 [74, 2196]MapClientEventToSimEvent:EventID=66708, EventName="EXTINGUI
SH_ENGINE_FIRE"
> 13.57655 [74, 2197]MapClientEventToSimEvent:EventID=66709, EventName="AP_MAX_B
ANK_INC"
> 13.57671 [74, 2198]MapClientEventToSimEvent:EventID=66710, EventName="AP_MAX_B
ANK_DEC"
> 13.57688 [74, 2199]MapClientEventToSimEvent:EventID=66711, EventName="AP_N1_HO
LD"
> 13.57704 [74, 2200]MapClientEventToSimEvent:EventID=66712, EventName="HYDRAULI
C_SWITCH_TOGGLE"
> 13.57721 [74, 2201]MapClientEventToSimEvent:EventID=66713, EventName="INCREASE
_DECISION_ALTITUDE_MSL"
> 13.57737 [74, 2202]MapClientEventToSimEvent:EventID=66714, EventName="DECREASE
_DECISION_ALTITUDE_MSL"
> 13.57754 [74, 2203]MapClientEventToSimEvent:EventID=66715, EventName="BLEED_AI
R_SOURCE_CONTROL_INC"
> 13.57770 [74, 2204]MapClientEventToSimEvent:EventID=66716, EventName="BLEED_AI
R_SOURCE_CONTROL_DEC"
> 13.57786 [74, 2205]MapClientEventToSimEvent:EventID=66717, EventName="TURBINE_
IGNITION_SWITCH_TOGGLE"
> 13.57802 [74, 2206]MapClientEventToSimEvent:EventID=66718, EventName="CABIN_NO
_SMOKING_ALERT_SWITCH_TOGGLE"
> 13.57819 [74, 2207]MapClientEventToSimEvent:EventID=66719, EventName="CABIN_SE
ATBELTS_ALERT_SWITCH_TOGGLE"
> 13.57836 [74, 2208]MapClientEventToSimEvent:EventID=66720, EventName="ANTISKID
_BRAKES_TOGGLE"
> 13.57852 [74, 2209]MapClientEventToSimEvent:EventID=66721, EventName="GPWS_SWI
TCH_TOGGLE"
> 13.57868 [74, 2210]MapClientEventToSimEvent:EventID=66722, EventName="VIDEO_RE
CORD_TOGGLE"
> 13.57884 [74, 2211]MapClientEventToSimEvent:EventID=66723, EventName="SET_AUTO
BRAKE_CONTROL"
> 13.57900 [74, 2212]MapClientEventToSimEvent:EventID=66724, EventName="TOGGLE_A
IRPORT_NAME_DISPLAY"
> 13.57917 [74, 2213]MapClientEventToSimEvent:EventID=66725, EventName="TOGGLE_M
ASTER_STARTER_SWITCH"
> 13.57933 [74, 2214]MapClientEventToSimEvent:EventID=66726, EventName="GEAR_EME
RGENCY_HANDLE_TOGGLE"
> 13.57949 [74, 2215]MapClientEventToSimEvent:EventID=66731, EventName="AILERON_
TRIM_SET"
> 13.57966 [74, 2216]AddClientEventToNotificationGroup:GroupID=2, EventID=66731,
 bMaskable=0
> 13.57982 [74, 2217]MapClientEventToSimEvent:EventID=66732, EventName="RUDDER_T
RIM_SET"
> 13.57998 [74, 2218]AddClientEventToNotificationGroup:GroupID=2, EventID=66732,
 bMaskable=0
> 13.58014 [74, 2219]MapClientEventToSimEvent:EventID=66733, EventName="CAPTURE_
SCREENSHOT"
> 13.58030 [74, 2220]MapClientEventToSimEvent:EventID=66734, EventName="MOUSE_LO
OK_TOGGLE"
> 13.58046 [74, 2221]MapClientEventToSimEvent:EventID=66735, EventName="MP_BROAD
CAST_VOICE_CAPTURE_START"
> 13.58063 [74, 2222]MapClientEventToSimEvent:EventID=66736, EventName="MP_BROAD
CAST_VOICE_CAPTURE_STOP"
> 13.58079 [74, 2223]MapClientEventToSimEvent:EventID=66737, EventName="FLY_BY_W
IRE_ELAC_TOGGLE"
> 13.58095 [74, 2224]MapClientEventToSimEvent:EventID=66738, EventName="FLY_BY_W
IRE_FAC_TOGGLE"
> 13.58111 [74, 2225]MapClientEventToSimEvent:EventID=66739, EventName="FLY_BY_W
IRE_SEC_TOGGLE"
> 13.58128 [74, 2226]MapClientEventToSimEvent:EventID=66740, EventName="MANUAL_F
UEL_PRESSURE_PUMP"

[virtuali]

Here are the first few lines of the file.  I have the entire contents of the file if needed.

They aren't. You missed the first lines. 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.

[DMullert]

Hello Umberto!

Man it scrolls fast but I think I got them this time around.  Here you go:


0.00000 SimConnect version 10.0.61259.0

0.26631 Exe Launched:  Path="C:\Program Files (x86)\GoFlight\GFDevFSX.exe"  Comm
andLine=""  Version="2.2.2.1"
0.26871 Exe Launched:  Path="C:\Program Files (x86)\Saitek\Pro Flight Panels\Sai
Panels.exe"  CommandLine="-run"  Version="1.0.0.1"
0.27265 Exe Launched:  Path="c:\OpusFSX\FSXSERVER.EXE"  CommandLine=""  Version=
"3.0.0.0"
0.27354 File not found: Path="Captain_Sim\777\cs.sound.dll"
0.27365 File not found: Path="Captain_Sim\Captain_Sim.b767.menu.dll"
0.27375 File not found: Path="Captain_Sim\767\cs.sound.dll"
0.27384 File not found: Path="Captain_Sim\Captain_Sim.b757.menu.dll"
0.27394 File not found: Path="Captain_Sim\757\cs.sound.dll"
0.27585 DLL Loaded:  Path="MD80.dll"  Version="<Unknown>"
0.27875 DLL Loaded:  Path="FeelThere\Erj\E145XH.dll"  Version="1.3.0.1"
0.28149 DLL Loaded:  Path="FeelThere\E170\EJetH.dll"  Version="1.3.0.1"
0.43421 DLL Loaded:  Path="Modules\LVLD.dll"  Version="1.4.2.1"
0.43731 DLL Loaded:  Path="PMDG\DLLs\PMDG_HUD_interface.dll"  Version="2.0.0.1"
0.44185 DLL Loaded:  Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flig
ht Simulator X\VistaMare\ViMaCoreX.dll"  Version="10.0.0.13"

[virtuali]

Man it scrolls fast but I think I got them this time around.  Here you go:

You have so many modules installed, that the "first 10 lines" are not enough. Try to get more of them, so they would include Couatl.exe

[DMullert]

Hey Umberto!

I cleaned up the CaptainSim stuff as I no longer have any CaptainSim products installed; that cleared the first section a bit.  Here's what I got now:


0.00000 SimConnect version 10.0.61259.0

0.20839 Exe Launched:  Path="C:\Program Files (x86)\GoFlight\GFDevFSX.exe"  Comm
andLine=""  Version="2.2.2.1"
0.21024 Exe Launched:  Path="C:\Program Files (x86)\Saitek\Pro Flight Panels\Sai
Panels.exe"  CommandLine="-run"  Version="1.0.0.1"
0.21394 Exe Launched:  Path="c:\OpusFSX\FSXSERVER.EXE"  CommandLine=""  Version=
"3.0.0.0"
0.21689 DLL Loaded:  Path="MD80.dll"  Version="<Unknown>"
0.22076 DLL Loaded:  Path="FeelThere\Erj\E145XH.dll"  Version="1.3.0.1"
0.22313 DLL Loaded:  Path="FeelThere\E170\EJetH.dll"  Version="1.3.0.1"
0.36619 DLL Loaded:  Path="Modules\LVLD.dll"  Version="1.4.2.1"
0.36836 DLL Loaded:  Path="PMDG\DLLs\PMDG_HUD_interface.dll"  Version="2.0.0.1"
0.37167 DLL Loaded:  Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flig
ht Simulator X\VistaMare\ViMaCoreX.dll"  Version="10.0.0.13"

Looks like Coautl is not getting loaded.  Below is a copy of what my DLL.xml file looks like:

<?xml version="1.0" encoding="WINDOWS-1252"?>
-<SimBase.Document version="1,0" Type="Launch"><Descr>Launch</Descr><Filename>dll.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad>-<Launch.Addon><Name>Object Placement Tool</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path></Launch.Addon>-<Launch.Addon><Name>Traffic Toolbox</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path></Launch.Addon>-<Launch.Addon><Name>Visual Effects Tool</Name><Disabled>True</Disabled><ManualLoad>False</ManualLoad><Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path></Launch.Addon>-<Launch.Addon><Name>MD80</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>MD80.dll</Path><DllStartName>module_init</DllStartName><DllStopName>module_deinit</DllStopName></Launch.Addon>-<Launch.Addon><Name>FeelThere ERJX Helper</Name><Disabled>False</Disabled><Path>FeelThere\Erj\E145XH.dll</Path></Launch.Addon>-<Launch.Addon><Name>FeelThere EJetX Helper</Name><Disabled>False</Disabled><Path>FeelThere\E170\EJetH.dll</Path></Launch.Addon>-<Launch.Addon><Name>Level-D Simulations</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>Modules\LVLD.dll</Path></Launch.Addon>-<Launch.Addon><Name>PMDG HUD interface</Name><Disabled>False</Disabled><Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path><DllStartName>module_init</DllStartName><DllStopName>module_deinit</DllStopName></Launch.Addon>-<Launch.Addon><Name>VistaMare Core</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll</Path></Launch.Addon>-<Launch.Addon><Name>FSUIPC 4</Name><Disabled>False</Disabled><Path>Modules\FSUIPC4_Loader.dll</Path></Launch.Addon></SimBase.Document>

[virtuali]

Looks like Coautl is not getting loaded.  Below is a copy of what my DLL.xml file looks like:

Couatl.exe, being an .EXE, should be in your EXE.XML file.

However, I don't see the Addon Manager listed in your DLL.XML file too, which also look a bit strange (it's possible corrupted?), and that would explain why none of the modules are loading or asking permission to load.

Don't try to post the XML file in the forum, this will change their format. ZIP both the EXE and the DLL XML files, and Attach them to a post, so I can check them as they really are.

[DMullert]

Hello Umberto!

Here you go my friend.

[virtuali]

Your files are fine, however they don't contain the Couatl.exe entries and the bglmanx.dll entires.

The entries are added automatically by any of our installers, provided the files are not already corrupted but, since they aren't, it's just not possible our installer couldn't add that line.

The only possible explanation, is the installer hasn't completed for some other reason.

Try to download and install the Stand-Alone Addon Manager and pay attention to any error messages while installing.

[DMullert]

Problem Solved Umberto!  The standalone installer did the trick.

Thanks a million for all your help today!

Cheers.