FSDreamTeam forum
Products Support => Hawaiian Airports support FSX/P3D => Topic started by: HarFRXtreme on July 19, 2011, 01:00:31 pm
-
Hello FSDreamteam i just downloaded a trial version of Hawaiian Airport Vol.2 ( PHOG ) and loaded it in my FSX but there is only terrain the ground is visiable but all the termainals cargo ramps etc are not visiable they are just like black boxes please tell me a solution for it
-
As explained in the all previous threads about missing buildings, you should first check if you have BOTH the Addon Manager and the Couatl menus under FSX.
If not, it's likely caused by your antivirus which has mistakenly identified one or both modules as threats, and blocked them.
To fix this:
- 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.
-
i did all same now i cant even get in the game after loading it gives a error to restart my FSX
-
i did all same now i cant even get in the game after loading it gives a error to restart my FSX :(
As explained in all previous threads that mention that startup error, you should do exactly the opposite as FSX suggests and always allow the module to run, even if it crashes.
Try a couple of times, always allowing the module to run, and if doesn't work, try to reboot Windows another time, then try again, a couple of times, it will always fix itself after some tries, especially after a reboot.
If not, the it's likely your antivirus is *still* interfering, and it has corrupted the file so, redo the first procedure step by step, don't skip ANY step, especially the one that says reinstalling with the antivirus entirely turned off.
-
I have the same problem. Did everything step by step as you said, but there is no coatle in the addon-window. When I installed the PHNL and the Hawaii Vol. 1 everything was OK, but now with the Vol.2 it doesn't work. Very strange and disappointing.
-
I have the same problem. Did everything step by step as you said, but there is no coatle in the addon-window. When I installed the PHNL and the Hawaii Vol. 1 everything was OK, but now with the Vol.2 it doesn't work. Very strange and disappointing.
I'm sorry, but if you don't have the Couatl, the only possible explanation is that the antivirus is still blocking.
Repeat the procedure to the letter and don't skip any step, especially the one that says you have to INSTALL with the Antivirus TURNED OFF entirely.
If you followed the procedure to the letter, you should see a question about Trusting BOTH the Addon Manager and the Couatl engine, which you obviously have to reply YES to both. If you don't see both question, than it's sure your antivirus is still blocking the program.
-
Yes, I've got both questions during the FSX-launch. I'll give it another try. I think, I have to uninstall first all of your Hawaiian airports? And what's about the other stuff (JFK, KDFW a.s.o)? Should I also reinstall it?
-
I think, I have to uninstall first all of your Hawaiian airports? And what's about the other stuff (JFK, KDFW a.s.o)? Should I also reinstall it?
You should do only what I've said in the above procedure, exactly, nothing less, nothing more, follow all the steps, don't skip anything, don't add anything.
If it doesn't work, don't try to fix it yourself, but describe exact what happened.
Note that, sometimes when you trust a module for the first time, you need to exit from FSX and reenter to have it running.
-
Sorry, but I did everything as you have written above. But at the addon-windows is only the addon-manager, but no cuatl-menu. On my antivirus-system, the Microsoft Security Essentials are also the two files excluded. It also asked me, when I launched the FSX for both programmes. I'm helpless!
-
But at the addon-windows is only the addon-manager, but no cuatl-menu.
Check the following folder
%APPDATA%\Virtuali
and see if you have a file named Couatl.err. If you have it, post its content here.
-
In this folder is only a file named "KeyMapping.ini"
-
In this folder is only a file named "KeyMapping.ini"
Ok, this means Couatl hasn't generated any errors.
Let's try enabling enabling the Simconnect diagnostic mode, this way:
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 messages scrolling down, look for the first 10 lines or so, and see if you can spot anything related to Couatl.
If the lines scroll too fast, you can use the "Pause" key on the keyboard.
-
OK, I'll try it tomorrow. Now I'll going to sleep, it was an exhausting day. Thanks for your patience.
-
I did what you said, but it doesn't work. No window with diagnostic message. Sorry.
-
I did what you said, but it doesn't work. No window with diagnostic message. Sorry.
Sorry, but that's just not possible, you must have missed something, because the Simconnect diagnostic window it's nothing related to our software, it's a basic FSX function.
So, either you did something wrong when enabling it or, it's possible your FSX installation is broken up to a point that Simconnect doesn't work at all, including its diagnostic window.
However, if you see the Addon Manager menu, it means Simconnect works so, if you don't see the diagnostic window, it can only mean you haven't executed what I've said correctly.
The path "Microsoft Flight Simulator X Files" under the Documents folder where you have to save the Simconnect.ini file, might have different names if your Windows version is not in English. It's easy recognizable, because it already contains your saved Flights, which have the .FLT, .WX and .FSSAVE extensions.
The Simconnect.ini should be saved in the same folder.
-
Yes, that was the right folder. Now I uninstall all your Hawaiian airports and will see, what happen, when I first start it without the 5 airports. After that, I'll install each separately without my MES activated.
Can't understand, why it doesn't work. Beside the Hawaiians I have 8 airports from FSD and everything was OK. Now with this Cuatl-programm I have such trouble.
BTW as I started FSX with this simconnect-file, all my other addons in the Addon-Window disappeared (FSUIP, Open Clouds, Follow Me etc.) and I had to install it again.
-
BTW as I started FSX with this simconnect-file, all my other addons in the Addon-Window disappeared (FSUIP, Open Clouds, Follow Me etc.) and I had to install it again.
That's shouldn't happen either, the Simconnect.ini file simply enables the diagnostic mode (which doesn't seem to work on your system, which is unheard of) but it doesn't affect your addons at all.
The only files that could make your modules to disappear, are the DLL.XML and EXE.XML, which are in a different folder ( %APPDATA%\Microsoft\FSX ) so it seems unlikely that, by editing the Documents/Flight Simulator Files folder, you would affect these.
-
Hi Umberto, just two questions:
As the Cuatle-Menue doesn't work for me with all the uninstall and deactivating my MSE, perhaps is it necessary, to make the process with every other FDS-airports outside Hawaii too?
Should the Simconnect-check appears at the very beginning from the FSX-launch (on my PC with all my lots of AI-Planes and sceneries it takes about 15 minutes) and should it appears at every launch again?
-
+
As the Cuatle-Menue doesn't work for me with all the uninstall and deactivating my MSE, perhaps is it necessary, to make the process with every other FDS-airports outside Hawaii too?
No, because all related to Addon Manager and Couatl it's shared between sceneries so, it's enough to fix it using only one scenery only.
Should the Simconnect-check appears at the very beginning from the FSX-launch (on my PC with all my lots of AI-Planes and sceneries it takes about 15 minutes) and should it appears at every launch again?
The Simconnect diagnostic window will appear immediately regardless of how many addons you have, because it's started before any other addon, and will appear every time, as long as you have the Simconnect.ini file in the Documents/Flight Simulator Files folder.
Sorry, it's just not possible that you would see the Addon Manager menu (meaning Simconnect is working) but wouldn't be able to see the Simconnect diagnostic window, the only explanation is that you did something wrong activating it.
Note that, being a separate window, you have to run FSX in a Window, otherwise you wouldn't be able to see the two windows together.
-
Hi Umberto, the next problem:
After uninstall all the Hawaiian Airports, deactivated my MSE, put the Simconnect-check in the right folder, I tried to install one of my Hawaiian Airports again and get this message:
An error occured while trying to create a file in the destination directory:
Setup was unable to create the director< "C:\ProgramFiles.......--fsdreamtean\cuatl\wx"
-
I tried to install one of my Hawaiian Airports again and get this message: An error occured while trying to create a file in the destination directory:
Setup was unable to create the director< "C:\ProgramFiles.......--fsdreamtean\cuatl\wx"
This because you ran setup too quickly after closing FSX, without giving it time to close properly so, files were still open, and the installer can't write to them.
This is of course fixed by a Windows reboot.
-
Now I uninstalled every FSD-Airport I have (12), closed down my MSE and started from the very beginning with installing LSGG. Launching FSX and nearly at the end of the launching-process I saw the Simconnect-check. Then comes the two messages to answer with Yes. Holding the Pause-button I could see an empty sheet and when I put on another key, then I could only see quick that there was some written at the simconnect, but can't stop it. Nevertheless as you can imagine, the result was the same: only the addon-manager was there and no Coatle. But I can see all the new folders and files regarding the LSGG in the FSD-folder.
So the antivirus-program is absolutely not the reason for my problem.
Now I read in another thread here about LSGG, that I'm not the only with the coatle-problem. And there was somebody, who resolved the problem with putting the exe.xml in the coatle-folder. Could you or this guy help me, what I could do exactly with this file? Thanks a lot as always.
-
If you are being ASKED to run the Couatl program, it means your EXE.XML is fine, otherwise there wouldn't be any question.
Of course, it's impossible to say what the problem is, if you can't see the diagnostic. Try to change this line in the Simconnect.ini:
level=normal
Change it to this:
level=error
And save back the file. This will hopefully result in an easier to see text, because it will indicate only errors.
-
Does it help for you: I have no coatle.exe
-
Does it help for you: I have no coatle.exe
You are not supposed to have a file named coatle.exe. The correct name is Couatl.exe, and it's located under the fsdreamteam\Couatl folder, under the main FSX folder.
If you have the folder, but not that file, it can only means it has been removed by the antivirus. Are you SURE you don't have ANOTHER security program running, on top of the antivirus ?
In any case, have you tried to do what I've asked to do in my previous message, after checking if you have the Couatl.exe file in the correct folder ?
-
I have a file in this folder named "couatle" without any endings and it is 1.144 KB. Nevertheless I'll try the simconnection with your modification.
BTW I have only this MSE Antivirus-Programm.
-
No way to stop the simconnect-sheet and read it. Could we try another solution together?
-
No way to stop the simconnect-sheet and read it. Could we try another solution together?
First, you should do what I've said in my previous message: by logging only errors, it would be difficult the screen would scroll very fast.
And, as I've said in another previous message, you can pause the scrolling by pressing the "Pause" key on the keyboard.
-
Umberto, I did everything you said. But when the simconnection appears and I push the PAUSE button, then nothing happens. Afters this, I push another button, e.g. any letter, then the four messages with the questions about the trust appears. I say YES, pressing the PAUSE simultaneously, but during this procedures suddenly I see a writing on the sheet just not for a second and that's it. How can I fix and read it, when it disappear immediately?
BTW since yesterday or so when I download the first of my FSD_airports, I see in the couatl-folder not the couatl.exe file, instead of this there are a file only named "couatl" with a green snake-symbol in front. Is this OK?
There must be another solution, you could understand, that I'm not willing, all my purchased airports to throw away. And as I saw in this support-forum, I was not the only having the problem with the Cuoatl.
-
Afters this, I push another button, e.g. any letter, then the four messages with the questions about the trust appears. I say YES, pressing the PAUSE simultaneously, but during this procedures suddenly I see a writing on the sheet just not for a second and that's it. How can I fix and read it, when it disappear immediately?
First, it's not normal you would get the trust request *each* time. Is this what's happening ? Or, just because you are uninstalling completely each time ? There's no need to do that now, just try to read the diagnostic window.
And, to have the pause key working, you have to have the Simconnect text window on the foreground, the pause key will not do anything if you press it when another window is displayed.
Simply try to arrange the FSX window and the simconnect diagnostic window so the can both be seen together on your desktop, and then press the pause key only when the simconnect window is on focus. If it's not, simply click on it, this is basic Windows behavior...
And no, there will be no text appearing and immediately disappearing. The lines of text will *scroll* and, if you followed my previous instruction and replaced the logging command to log only errors, instead of everything, there should be only a few lines scrolling, which means it should be quite easily to read them, even without pausing.
BTW since yesterday or so when I download the first of my FSD_airports, I see in the couatl-folder not the couatl.exe file, instead of this there are a file only named "couatl" with a green snake-symbol in front. Is this OK?
Yes, if your windows is configured to not show file extension, you wouldn't see the .exe extension.
There must be another solution,
There's no other solution that follow what I've said, thus being able to read the diagnostic window messages, so I can understand your issue.
And as I saw in this support-forum, I was not the only having the problem with the Cuoatl.
Your issue doesn't seem to have anything to do with this, all the issues are because faulty antivirus products interfere with it, not because the Couatl program has a problem. Clear proof of this, if you *follow* all the discussion to the end, not just the start of them, is that when the antivirus is correctly configured as instructed, it wil always work.
Your issue *seems* to be different, which is why I've asked to run the diagnostics, without them, there's no way to even start thinking how to fix it.
If you are really unable to use the pause key as instructed, it's possible to direct the output to a file, change the simconnect.ini file as follows:
[SimConnect]
level=normal
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
file=%APPDATA%\MicrosoftFSX\simconnect%03u.log
file_next_index=0
file_max_index=9
I've removed the commas on the file commands, and changed the pathname to point to a writable folder.
Run FSX once, then exit from it when the first screen appears. If you do it correctly, a file named simconnect000.log should have been created under %APPDATA%\Microsoft\FSX.
Post it here attached to a message, so I can have a look at it.
-
Umberto just a question: when the first screen appears (you mean the Simconnect-Screen?) then it's empty. Schould I at this point exit from FSX?
-
Umberto just a question: when the first screen appears (you mean the Simconnect-Screen?) then it's empty. Schould I at this point exit from FSX?
It seems to indicate there were no errors. Try put the logging level line back to normal in the simconnect.ini
level=normal
-
Again no way to stop the sheet and there is also no file created at the Appdata....
BTW in question to the Couatl.exe appendix, all my other files have the full appendix, only the couatl is without the exe-appendix. Is this OK?
-
Again no way to stop the sheet
As I've said, you can stop the scrolling by pressing the PAUSE key on the keyboard. This is nothing related to FSX, Couatl or anything like that. It's basic, standard, Windows OS behavior.
As I've said, for the PAUSE key to work, you have
and there is also no file created at the Appdata....
Not possible, the only possible explanation is that you wrote something wrong on the Simconnect.ini. Again, this is a standard FSX feature that ALWAYS works, doesn't have anything to do with our software. Check again your simconnect.ini, and be sure you included the correct commands, exactly as I wrote them in my previous message. Don't miss the fact (which I advised) that it's not just the path name changed compared to before, but you also have to remove the lines that begin with a semicolon.
BTW in question to the Couatl.exe appendix, all my other files have the full appendix, only the couatl is without the exe-appendix. Is this OK?
No, it's not. But, if your renamed that file, you wouldn't see confirmation to run it, because if the .EXE extension is missing, a file is not considered executable anymore so, FSX will not ask permission to run it, but you said it does.
-
I can't do anything wrong with the text in the simconnect.ini. I just copied your text.
But I think, in my explorer there is another path for the appdata:
My name\AppData\Roaming\Microsoft\FSX
Could that be the reason, that I can't see it?
-
Finally I could stop the simconnect-message:
0.45800 Exe Launched:Path="fsdreamteam\coatl\coatl.exe" CommandLine=""Version="2.0.0.2119"
Does it help?
-
Hi Umberto, what shall we do now with this Simconnect-message? There is still no couatl on my addon-window and of course no buildings at the airports.
-
Finally I could stop the simconnect-message:0.45800 Exe Launched:Path="fsdreamteam\coatl\coatl.exe" CommandLine=""Version="2.0.0.2119"
Does it help?
This can't be the correct text message, because there's no such thing as a coatl.exe program inside a coatl folder. Instead, there should be a couatl.exe inside a couatl folder, this means this is not the text as generated by FSX, but something you typed.
Don't retype it, copy&paste from the window, because I need to be sure the whole text is correct and nothing is missing.
And, it looks like you stopped it too early, because I don't see ANY error message which can only means one of these two things:
1) You stopped the text too early, not getting any possible errors, or you got an error, but you haven't copied it here.
OR
2) There's no error so, it's just not possible you don't have the Couatl menu, because Couatl has been loaded fine without errors.
Try again, and be sure to copy any errors, if there are any.
-
Under this lines there were similar lines about two of my other addons (FollowMe, and FS Open) and nothing else. And for me it was not possible to copy the text out of the Simconnect-windows.
Unfortunately that what you suggested to do with this simconnect000.log file, there is not such a file in my whole PC. Could it be, that, as I wrote above, my AppData-Path is a bit different as you said?