FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: COA777 on February 17, 2010, 02:03:08 am
-
Hi ya'll today I loaded up the simulator in Honolulu since I wasn't there for a while and I saw that the buildings weren't there. Before it was working fine after I put in the register key now it doesn't work. I got no idea what's going on here.
Thanks.
-
Try this first:
- 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.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.
-
I dont have any anti-virus programs but I uninstalled the scenery. Then when I downloaded again I keep getting these errors. Those are just some of the errors I get I didn't want show all of them or I would be here all day :-\.
-
Nevermind after downloading the windows update it works fine now.
Thanks.
-
It wasn't the Windows update that fixed it, it was the fact that you rebooted Windows.
Those errors were caused by the fact you ran our installer when FSX was still not fully closed so, the installer couldn't copy files, because they were still locked by it. The reboot solved the issue, of course.
-
Im still having issues with the buildings not loading even with the update. When approaching 4l just the cargo buildings along with taxi signs and trees load when I am on about a half mile final. The terminal buildings load when I am about 500ft to 1000ft away. This part is really interesting, the interhawaii terminal and the middle terminal(gates 14-23) dont load till I am like 20 feet away. That isnt right to me. Would changing the compatibility of the coutl.exe make a difference? Or running it as admin?
I am also still having issues with texture flickering around 4l and 4r about mid runway.
-
I can only confirm that, all main terminals loads at exactly 8 nm, not less not more. In any case, this problem doesn't have anything to do with this thread, which is related only to buildings missing *entirely*, because something is preventing our software to run, which is not this case.
The compatibility mode shouldn't be touched, meaning it needs to stay without any of the compatibility modes enabled, otherwise it wouldn't just run. And no, running as admin wouldn't make any difference. Again, these things might worth checking, only when trying to understand why the software is not running at all. This isn't the case: if you are seeing buildings, just the loading has been delayed, which means everything is working.
The only possible explanation, is that another addon is clogging Simconnect with so many commands, that our own are received with a delay. It might be worth trying to disable *every* other 3rd party module in DLL.XML and EXE.XML, by setting the <Disable> tag to True, then trying one by one, and see if it makes any difference.
And, I can't see any runway flickering either. The added mesh should prevent this, and I doubt you have a mesh higher that 4.75 m/pixel taking priority over our own.
Note that, as explained already, to get our mesh to display ( there's nothing to "see", it's just flat, but being flat at highres, it should fix any other mesh that might cause the problem ), both mesh-related sliders in the Graphic Settings needs to be set at 100.
-
Ok, I figured out the flickering is cause of the mesh that I have from fs dreamscapes. Would you like me to look at my dll.xml and exe.xml?
-
As I've said, try to put the <Disabled>True</Disabled> line on each module (except the Addon Manager) and see if it makes any difference.
-
It doesnt make any difference. Next idea?? The termianl buildings arent even loaded I press fly now after its done loading.
-
The termianl buildings arent even loaded I press fly now after its done loading.
Now I'm confused: you first said that the buildings loads fine, but only when you are very close to the airport, now they don't load at all, even when at the airport ? The normal behaviour should be, the terminals should load with a 1-2 seconds delay, after the rest of the scenery is loaded.
What happens if you press ESC, as if you wanted to end the flight, but then return to flight ?
-
Nothing. Im baffeled.
-
What's your Scenery Complexity setting ?
-
Extremely dense and LOD is at Medium.
-
And you DO see both the Addon Manager menu and the Couatl menus ?
Also, can you reply to this ?
Now I'm confused: you first said that the buildings loads fine, but only when you are very close to the airport, now they don't load at all, even when at the airport ?
-
Yes the coutl and addon manager are there. Let me get you some screen shots. Only half of the scenery is loaded when fs finishes loading. Do you happen to have any form of instant messenger?
-
Ok, I understand, there's no need for screenshots. So, you now have HALF of the main terminals visible ?
-
Ok when fs finishes loading all that is loaded of the scenery is the ground photo texture, and the cargo and ga buildings. None of the terminals are loaded. My start position is on I think 4R and always has been. Once I slew over to the termainal area, all of the termainals load except for gates 14-23 and the interisland terminal. I have to get really close to those two terminals inorder for them to load.
Is that a better explination?
-
Ok, so we are now back to the original explanation: all the buildings loads, but there's a range problem, which is not what is supposed to be.
You said that, if you slew close to a terminal, it will appear. But, when happens when you slew backward to your original position ? Does it disappear, or does it stay ?
-
It stays. Here are some more shots. If I slew back 8miles till the buildings dissappear, then move back towards the airport, it takes me back to square 1 with the buildings not loading till really close to them.
-
Ok, so you have your correct 8 nm range, but only after they are loaded once.
I'm sorry, but I don't have any explanation. Does it happen at PHNL only, or in other FSDT airports ?
-
Its happening with all of your scenerys. DO u think the anti virus could be interfering? It didnt use to do this. I idk whats happening.
-
No, the antivirus will either allow the programs to run or not. In case the antivirus is blocking them, you won't see any buildings and no menus as well.
-
Any ideas at all? Id hate to see this go unsolved.
-
I don't really have any idea what's wrong with your system. I will send you a special debug version of the modules tomorrow.
-
Ok thanks man. I really appericate it.
-
I figured it out!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I looked at my compatibility settings for fsx.exe, and I was reading on avsim forums that changing the compability to vista, or vista sp2 would somehow make the sim run more smoothly, but that seemed to be what was keeping the buildings from loading, soo I unchecked the compatibility settings and its working now.
-
I unchecked the compatibility settings and its working now.
That's what I've said in one of my previous posts:
The compatibility mode shouldn't be touched, meaning it needs to stay without any of the compatibility modes enabled
This is valid for both FSX and the Couatl exe. I really can't see why one would suggest to use a compatibility mode to make the sim running better. What compatibility mode does, is to re-route file read/write into folders that a Vista/7 user can write to, for older program that do not take into accout non-writable folders in Vista/7, like C:\Program Files, C:\Windows, etc. so, if anything, the program should run slower, not faster, since every file access is re-routed...
In any case, FSX is fully Vista-compliant so, there's no need to enable any of the compatibility modes. The only Vista/7 feature that FSX doesn't support, is Aero but, it's automatically disabled anyway, when FSX starts.
-
Truth is, is that I forgot that I changed the fsx.exe compat settings, and I thought that you were refering to only coutl and changing its settings aswell. OO well, problem solved! YAY :) thanks for all the great help Umberto!!!