Blackened spaces on scenery at terminal D **solved**

[virtuali]

Do you see the airport bacgkround at least ?

[phenocom]

If you mean the taxiways and runways and the taxi way bridges I do see those until the trial period expires.

[virtuali]

Try this:

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

Run FSX, go to KDFW, then quit FSX after the airport has been loaded. Check if you have a couatl.log file in the FSX\fsdreamteam\couatl folder and post its content here.

[phenocom]

I did what you instructed me but after I started FSX and the Airport KDFW came up I checked my addons and Couatl Powered products was not listed anymore and there was no couatl.log file in the couatl folder after I quit FSX.

[virtuali]

I did what you instructed me but after I started FSX and the Airport KDFW came up I checked my addons and Couatl Powered products was not listed anymore and there was no couatl.log file in the couatl folder after I quit FSX.

This means Couatl didn't run this time. However, it's not possible that asking it to do a log, would prevent it to run so, I suspect it didn't run also the previous times, that's why you don't see buildings.

Check the Couatl.exe process is not stuck in the Task manager, this can happen if you relaunch FSX too quickly after a test. If you still see Couatl.exe in the Task manager with FSX closed, kill the process, and try again.

[phenocom]

Ok I checked the task manager and found that Couatl.exe was stck in the task mgr. I then killed the process and then restarted FSX and ran the scenery for KDFW however the scenery still was not displayed. I did manage to get a couatl.log file and I am posting its contents:

couatl v1.0 (build 1024)
log started on Thu Sep 16 17:35:19 2010

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addon ZurichX:
Addon ZurichX loaded
Loading addon OHareX:
Addon OHareX loaded
Loading addon JFK:
Addon JFK loaded
Loading addon XPOI:
Addon XPOI not installed or missing one or more files, skipping
Loading addon ParkMe:
Addon ParkMe loaded
Loading addon LSGG:
Addon LSGG loaded
Loading addon KLAS:
Addon KLAS loaded
Loading addon KFLL:
Addon KFLL loaded
Loading addon PHNL:
Addon PHNL loaded
Loading addon KDFW:
Addon KDFW loaded
Loading addon ENBR:
Addon ENBR not installed or missing one or more files, skipping
SharedMemInterface connected
Entering ParkMe area Dallas-Fort Worth International Airport
disconnected from SimConnect.

[virtuali]

As I expected: the log simply shows KDFW has been loaded successfully, and everything is working fine...the problem must be somewhere else.

You can activate the Simconnect diagnostic mode, this way:

Open notepad, and copy the following text:

Code: [Select]

[SimConnect]
level=verbose
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. Go to KDFW, let the sim run for 10-20 seconds, then exit.

You should see a file named simconnect000.log in your C:\ drive. Zip it and send it to me via email. It's obvious your problems is very specific to your system so, there's no need to continue here, we'll sort it out via email.

[phenocom]

Umberto
I sent a pm to you for your email address in it I included my email.
Thank You
Dave

[virtuali]

Problem has been solved, in this specific case, everything was working correctly, just the computer was so slow loading FSX (about 7 minutes) that the trial time elapsed before the loading finished.