Products Support > Honolulu FSX/P3D
HNL Add-on Buildings Missing **SOLVED**
James8133:
Yes, I did buy the scenery. I figured out what the problem was. I had to update my AES from Aerosoft, and now it works. What I don't understand is why it wasn't working before I updated it?
bravotango:
I too am having this problem of no buildings and so far can't fix it.
Finally dragged kicking and screaming into dealing with windows 10 because my old PC failed so I upgraded to an ACER gaming machine
with a top graphics card.
My main concern was to run FSX so I stupidly installed FSX on the data disk which is 1TB.
Installing it on the SSD was out of the question as it is only 120GB.
That did work but I could not get couati to register my fsdreamteam Honolulu scenery and also the buildings at PHNL were not visible.
It would accept my registration key but then do nothing and leave me in trial mode.
So I had an idea to change the root directory for FSX to the one on my old drive which I have installed on the ACER (can't boot from it).
Changing the path was easy using the FSXRegUtility.
Somehow starting FSX on the old drive worked like a charm and couati generated all the registration keys and installed them in my home folder
during the FSX start up.
However this was never going to work as I would have to fix numerous registry items for too many addons so back to the FSX on data disk.
To try to fix the problem I uninstalled PHNL and both Hawaii sceneries and GSX then the addon manager and pretty sure all registry items were fixed.
I still have the registration keys in the home folder.
I thought to only install one scenery at a time so I installed the addon manager and PHNL.
Now when I boot FSX there appear to be two instances of addon manager running.
One tells me that I am in trial mode and the other tells me PHNL is installed and activated but of course no buildings, just loading docks and lots of cars.
Maybe two instances of addon manager are running because one is installed in H:\Program Files (x86)
and there is another in H:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl.
I can see the two instances in the FSX screen under "Addons" and can select either of those buttons.
What to do?
virtuali:
--- Quote from: bravotango on October 31, 2017, 06:44:52 am ---Maybe two instances of addon manager are running because one is installed in H:\Program Files (x86) and there is another in H:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl.
--- End quote ---
That seems to indicate that you installed something using an OLD installer (one that installed into the sim) AFTER you installed something using a more recent installer (one made after June 2017, which installs into any folder you like).
- Uninstall everything from FSDT. Reply YES to the question "Do you want to remove the Addon Manager "?
- Reinstall everything from FSDT using ONLY the current installer.
bravotango:
Thank you for the quick response.
But before I do that I just found I have two couatl items in the FSX.cfg file:
H:\Program Files (x86)\Addon Manager\couatl\couatl.exe.okwqqtqhzzteihqckazwatokckkozhzceitzacln=1
H:\Program Files (x86)\Addon Manager\bglmanx.dll.qzneauuqlktooqinqawhtehrbzweuztluzibnbow=1
H:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe.ecnzwlitltqkolieqarnzrircociqtwikwazazkh=1
I would bet this is the culprit but which one to delete without messing everything up. I know what the bglmanx.dll is so that's OK.
I might delete the first one and see what happens.
virtuali:
--- Quote from: bravotango on October 31, 2017, 07:13:16 am ---I would bet this is the culprit but which one to delete without messing everything up. I know what the bglmanx.dll is so that's OK. I might delete the first one and see what happens.
--- End quote ---
Nothing in your FSX.CFG is telling you anything strange or unusual or wrong. The [Trust] section you posted simply contains the HISTORY of all executable modules ever trusted, even long ago. Fact you have two entries for Couatl.exe, simply means you trusted it twice, and it was located in two different places when you did, but that doesn't mean there's a conflict, or the sim is now loading it twice.
You would have to look at the EXE.XML to know that, which lists the modules which the sim will try to load NOW.
In any case, ALL our entries (bglmanx.dll and Couatl.exe) in the [Trust] sections would have been removed if you replied YES to the question "Do you want to remove the Addon Manager ?" (and the same question about Couatl, if the uninstaller asked for it), which is why I told you to do that so, there was no need to worry about cleaning up the sections FSX.CFG, because the procedure I've suggested precisely does that.
Not that it was required to run the modules, but since some users mistakenly *refuse* to trust the modules and forget they ever did so and then wonder why the modules don't start, the above procedure it's an easy way to undo all of that and start again, without having to edit the FSX.CFG manually. This wasn't your case, since the 1 number means you *have* trusted the modules on both occasions, and it was working fine.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version