Need demo help with GSX

[murfman89]

Downloaded the GSX demo and the addon, installed both twice, app first then the addon, fired up FSX and got the Allow pop-ups, allowed them all, but can not run GSX with CTRL F12 or from the addon menu (not even there).  My default 737 nor my QWings 757 will run it from KSFO.  Just wanted to try it and see how much of a hit on FPS it is.  Also not listed under key commands to see if I can even change F12 keys.  The CouATL was installed and allowed as well.  Please help!!  Mike

[virtuali]

As explained in many other threads on the forum, you you are not seeing the Couatl menu in FSX, the most common cause it's the antivirus blocking it.

- DOWNLOAD AND INSTALL with the antivirus entirely OFF

- Uninstall GSX. 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 GSX 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

[murfman89]

Thanks, do I need to install both GSX and then the Addon Manager?

[murfman89]

Bummer, no luck.  Killed MS Security, removed all FSDream products and folders, reinstalled GSX, allowed those files to be run even with MS Security still off, open FSX and it asked to allow COUATL to run and then added to trusted items.  No GSX at KSFO with default 737, see photo.

[virtuali]

The MS Security Essentials is not a problem, can be used with our products without turning it off.

You can try to enable the Simconnect diagnostic, to see if it starts or not:

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 messages: the FIRST 10 lines or so are important: you should try to note what they are saying. If the text scrolls too fast, use the Pause key on the keyboard.