No buildings after reactivating in Scenery Library **SOLVED**

[akstirling]

Before going into the detail of my problem for the record i side with those who bemoan the complexity of these products. In response to a terrain.dll crash in P3D i deactivated the hawaiian airports in the scenery library. I have started adding them back one at a time (i.e. by putting the 'tick' back)... first to add  Honolulu .. end result no buildings showing up and a comment in Addon manager 'Active but not installed' which makes not a lot of sense to me ...

[virtuali]

Before going into the detail of my problem for the record i side with those who bemoan the complexity of these products.

Nothing in your report indicates the are any problems due to their supposed complexity.

In response to a terrain.dll crash in P3D i deactivated the hawaiian airports in the scenery library

You should probably have started with deactivating something else, likely a 3rd party add-on mesh for that area (there are several available), because such error couldn't possibly caused by the airports, and nobody ever reported it before.

. I have started adding them back one at a time (i.e. by putting the 'tick' back)... first to add  Honolulu .. end result no buildings showing up and a comment in Addon manager 'Active but not installed' which makes not a lot of sense to me ...

If it says  'Active but not installed', this seems to indicate you have an old version of the Addon Manager, because in the current version the message has been made a bit more clear, saying 'Active but not installed in the Scenery Library', which refers to its installation status in the Scenery Library of the program, not the installation status as such.

In any case, the Scenery Library is checked only when loading the sim which means, if you just enable it, you must restart the sim to see the effect of the scenery being visible.

[qqwertz]

I have exactly the same problem. all of a sudden, CYVR (and FlightBeam KDEN as well) does not show any buildings anymore (ground textures and jetways seem to be fine). When I check the addon manager it says "Active but not installed in the scenery library". However, CYVR can be found in the FSX scenery library, and the fact that the ground textures can be found indicates that FSX is aware of it.

One thing I did since I last flew to CYVR was to install P3D 2.5 and FSX Steam edition on the same PC as standard FSX (Gold). I only did a test run with the other two simulators and did not install any addons in it, as I intend to stick with FSX Gold.

I tried to de-activate and re-activate CYVR, but it didn't help. Neither did disabling the scenery in the FSX scenery library and re-enabling it.

Help would be most appreciated.
Peter

[virtuali]

I have exactly the same problem.

Your problem seems to be entirely different.

The original poster said that the scenery couldn't be enabled/disabled on the fly without restarting FSX. This is normal and it's not a problem. For performances reasons (in order not to scan constantly the scenery library when something is enabled/disabled on the fly), the Addon Manager will only rescan the scenery library during startup, not when making any changes on the Scenery Library.

all of a sudden, CYVR (and FlightBeam KDEN as well) does not show any buildings anymore (ground textures and jetways seem to be fine). When I check the addon manager it says "Active but not installed in the scenery library". However, CYVR can be found in the FSX scenery library, and the fact that the ground textures can be found indicates that FSX is aware of it.

It's possible there's a problem with your scenery.cfg, so it cannot be parsed correctly for some reason. Try to enable Logging in the Troubleshooting page of the "GSX - Settings" menu, and then post your Couatl.LOG file, to be found under the %APPDATA%\Virtuali folder, after an FSX restart after enabling Logging.

[qqwertz]

Hi Umberto,

thanks a lot for your quick response. Below you may find the log file.

Best regards,
Peter

couatl v2.0 (build 2374)
log started on Sat Feb 14 19:58:52 2015

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 22 AddOn(s)
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon OHareX
Addon OHareX not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW not installed or missing one or more files, skipping
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e20537065616b65727320285265616c74656b204869676820446566696e6974696f6e20417564696f29)
Created OpenAL device: Generic Software on Speakers (Realtek High Definition Audio)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Current sim directory is D:/FSXStuff
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
  using Scenery/World/scenery (layer 1)
  using Scenery/BASE/scenery (layer 2)
  using ORBX/FTX_VECTOR/FTX_VECTOR_AEC/scenery (layer 3)
  using Scenery/0000/scenery (layer 4)
  using Scenery/0001/scenery (layer 5)
  using Scenery/0002/scenery (layer 6)
  using Scenery/0003/scenery (layer 7)
  using Scenery/0004/scenery (layer
  using Scenery/0005/scenery (layer 9)
  using Scenery/0006/scenery (layer 10)
  using Scenery/0007/scenery (layer 11)
  using Scenery/0100/scenery (layer 12)
  using Scenery/0101/scenery (layer 13)
  using Scenery/0102/scenery (layer 14)
  using Scenery/0103/scenery (layer 15)
  using Scenery/0104/scenery (layer 16)
  using Scenery/0105/scenery (layer 17)
  using Scenery/0106/scenery (layer 18)
  using Scenery/0107/scenery (layer 19)
  using Scenery/0200/scenery (layer 20)
  using Scenery/0201/scenery (layer 21)
  using Scenery/0202/scenery (layer 22)
  using Scenery/0203/scenery (layer 23)
  using Scenery/0204/scenery (layer 24)
  using Scenery/0205/scenery (layer 25)
  using Scenery/0206/scenery (layer 26)
  using Scenery/0207/scenery (layer 27)
  using Scenery/0300/scenery (layer 28)
  using Scenery/0301/scenery (layer 29)
  using Scenery/0302/scenery (layer 30)
  using Scenery/0303/scenery (layer 31)
  using Scenery/0304/scenery (layer 32)
  using Scenery/0305/scenery (layer 33)
  using Scenery/0306/scenery (layer 34)
  using Scenery/0307/scenery (layer 35)
  using Scenery/0400/scenery (layer 36)
  using Scenery/0401/scenery (layer 37)
  using Scenery/0402/scenery (layer 38)
  using Scenery/0403/scenery (layer 39)
  using Scenery/0404/scenery (layer 40)
  using Scenery/0405/scenery (layer 41)
  using Scenery/0406/scenery (layer 42)
  using Scenery/0407/scenery (layer 43)
  using Scenery/0500/scenery (layer 44)
  using Scenery/0501/scenery (layer 45)
  using Scenery/0502/scenery (layer 46)
  using Scenery/0503/scenery (layer 47)
  using Scenery/0504/scenery (layer 48)
  using Scenery/0505/scenery (layer 49)
  using Scenery/0506/scenery (layer 50)
  using Scenery/0507/scenery (layer 51)
  using Scenery/0600/scenery (layer 52)
  using Scenery/0601/scenery (layer 53)
  using Scenery/0602/scenery (layer 54)
  using Scenery/0603/scenery (layer 55)
  using Scenery/0604/scenery (layer 56)
  using Scenery/0605/scenery (layer 57)
  using Scenery/0606/scenery (layer 58)
  using Scenery/0607/scenery (layer 59)
  using Scenery/0700/scenery (layer 60)
  using Scenery/0701/scenery (layer 61)
  using Scenery/0702/scenery (layer 62)
  using Scenery/0703/scenery (layer 63)
  using Scenery/0704/scenery (layer 64)
  using Scenery/0705/scenery (layer 65)
  using Scenery/0706/scenery (layer 66)
  using Scenery/0707/scenery (layer 67)
  using Scenery/0800/scenery (layer 68)
  using Scenery/0801/scenery (layer 69)
  using Scenery/0802/scenery (layer 70)
  using Scenery/0803/scenery (layer 71)
  using Scenery/0804/scenery (layer 72)
  using Scenery/0805/scenery (layer 73)
  using Scenery/0806/scenery (layer 74)
  using Scenery/0807/scenery (layer 75)
  using Scenery/0900/scenery (layer 76)
  using Scenery/0901/scenery (layer 77)
  using Scenery/0902/scenery (layer 78)
  using Scenery/0903/scenery (layer 79)
  using Scenery/0904/scenery (layer 80)
  using Scenery/0905/scenery (layer 81)
  using Scenery/0906/scenery (layer 82)
  using Scenery/0907/scenery (layer 83)
  using Scenery/1000/scenery (layer 84)
  using Scenery/1001/scenery (layer 85)
  using Scenery/1002/scenery (layer 86)
  using Scenery/1003/scenery (layer 87)
  using Scenery/1004/scenery (layer 88)
  using Scenery/1005/scenery (layer 89)
  using Scenery/1006/scenery (layer 90)
  using Scenery/1007/scenery (layer 91)
  using Scenery/1100/scenery (layer 92)
  using Scenery/1101/scenery (layer 93)
  using Scenery/1102/scenery (layer 94)
  using Scenery/1103/scenery (layer 95)
  using Scenery/1104/scenery (layer 96)
  using Scenery/1105/scenery (layer 97)
  using Scenery/1106/scenery (layer 98)
  using Scenery/1107/scenery (layer 99)
  using D:/fsgux/eur/scenery (layer 100)
  using D:/fsgux/afr/scenery (layer 101)
  using D:/fsgux/asi/scenery (layer 102)
  using D:/fsgux/oce/scenery (layer 103)
  using D:/fsgux/ant/scenery (layer 104)
  using D:/fsgux/nam/scenery (layer 105)
  using D:/fsgux/csa/scenery (layer 106)
  using D:/fsgux/LocalMeshes/scenery (layer 107)
  using ORBX/FTX_VECTOR/FTX_VECTOR_EXX/scenery (layer 108)
  using ORBX/FTX_VECTOR/FTX_VECTOR_CVX/scenery (layer 109)
  using ORBX/FTX_VECTOR/FTX_VECTOR_APT/scenery (layer 110)
  using ORBX/FTX_VECTOR/FTX_VECTOR_OBJ/scenery (layer 111)
  using Scenery/AFRI/scenery (layer 112)
  using Scenery/ASIA/scenery (layer 113)
  using Scenery/AUST/scenery (layer 114)
  using Scenery/EURE/scenery (layer 115)
  using Scenery/EURW/scenery (layer 116)
  using Scenery/NAMC/scenery (layer 117)
  using Scenery/NAME/scenery (layer 118)
  using Scenery/NAMW/scenery (layer 119)
  using Scenery/OCEN/scenery (layer 120)
  using Scenery/SAME/scenery (layer 121)
  using Scenery/Cities/Oshkosh/scenery (layer 122)
  using Scenery/Cities/StMaarten/scenery (layer 123)
  using Scenery/Cities/Rio/scenery (layer 124)
  using Scenery/Cities/LasVegas/scenery (layer 125)
  using Scenery/Global/scenery (layer 126)
  using Scenery/Props/scenery (layer 127)
  using Scenery/Cities/Reno/scenery (layer 128)
  using Scenery/Cities/Istanbul/scenery (layer 129)
  using Scenery/Cities/Longleat/scenery (layer 130)
  using Scenery/Cities/Berlin/scenery (layer 131)
  using Scenery/Cities/Edwards_AFB/scenery (layer 132)
  using ORBX/FTX_NZ/FTX_NZSI_08_CUSTOM/scenery (layer 133)
  using ORBX/FTX_NZ/FTX_NZSI_07_MESH/scenery (layer 134)
  using ORBX/FTX_NZ/FTX_NZSI_06_CVX/scenery (layer 135)
  using ORBX/FTX_NZ/FTX_NZSI_05_SCENERY/scenery (layer 136)
  using ORBX/FTX_NZ/FTX_NZNI_08_CUSTOM/scenery (layer 137)
  using ORBX/FTX_NZ/FTX_NZNI_07_MESH/scenery (layer 138)
  using ORBX/FTX_NZ/FTX_NZNI_06_CVX/scenery (layer 139)
  using ORBX/FTX_NZ/FTX_NZNI_05_SCENERY/scenery (layer 140)
  using ORBX/FTX_NA/FTX_NA_PNW08_CUSTOM/scenery (layer 141)
  using ORBX/FTX_NA/FTX_NA_PNW07_MESH/scenery (layer 142)
  using ORBX/FTX_NA/FTX_NA_PNW06_CVX/scenery (layer 143)
  using ORBX/FTX_NA/FTX_NA_PNW05_SCENERY/scenery (layer 144)
  using ORBX/FTX_NA/FTX_NA_PFJ08_CUSTOM/scenery (layer 145)
  using ORBX/FTX_NA/FTX_NA_PFJ07_MESH/scenery (layer 146)
  using ORBX/FTX_NA/FTX_NA_PFJ06_CVX/scenery (layer 147)
  using ORBX/FTX_NA/FTX_NA_PFJ05_SCENERY/scenery (layer 148)
  using ORBX/FTX_GLOBAL/FTX_FTXG_AIRPORTS/scenery (layer 149)
  using ORBX/FTX_NA/FTX_AA_CZST/scenery (layer 150)
  using ORBX/FTX_NA/FTX_AA_CYSE/scenery (layer 151)
  using ORBX/FTX_NA/FTX_AA_CYBD/scenery (layer 152)
  using ORBX/FTX_NA/FTX_AA_CEN4/scenery (layer 153)
  using ORBX/FTX_NA/FTX_AA_CEJ4/scenery (layer 154)
  using ORBX/FTX_NA/FTX_AA_CEF4/scenery (layer 155)
  using ORBX/FTX_NA/FTX_AA_CBB7/scenery (layer 156)
  using ORBX/FTX_AU/FTXAU48_CUSTOM/scenery (layer 157)
  using ORBX/FTX_AU/FTXAU46_SHORES/scenery (layer 158)
  using ORBX/FTX_AU/FTXAU45_SCENERY/scenery (layer 159)
  using ORBX/FTX_AU/FTXAU05_ROADS/scenery (layer 160)
  using ORBX/FTX_AU/FTXAA_ORBXLIBS/scenery (layer 161)
  using ORBX/FTX_OLC/OLC_AA/scenery (layer 162)
  using ORBX/FTX_OLC/OLC_NA1/scenery (layer 163)
  using ORBX/FTX_OLC/OLC_EU9/scenery (layer 164)
  using ORBX/FTX_OLC/OLC_EU8/scenery (layer 165)
  using ORBX/FTX_OLC/OLC_EU7/scenery (layer 166)
  using ORBX/FTX_OLC/OLC_EU6/scenery (layer 167)
  using ORBX/FTX_OLC/OLC_EU5/scenery (layer 168)
  using ORBX/FTX_OLC/OLC_EU4/scenery (layer 169)
  using ORBX/FTX_OLC/OLC_EU3/scenery (layer 170)
  using ORBX/FTX_OLC/OLC_EU2/scenery (layer 171)
  using ORBX/FTX_OLC/OLC_EU10/scenery (layer 172)
  using ORBX/FTX_OLC/OLC_EU1/scenery (layer 173)

[virtuali]

Your log doesn't show anything wrong, although that log only shows that Couatl (thus GSX) has found the scenery, but it doesn't say anything if the Addon Manager found it.

In any case, it shows your Couatl.exe is outdated (current build is the 2378) and, since it's not possible to not have it updated if you just installed it (because the installer downloads the current version automatically), it looks like you haven't installed the scenery in a while.

So, first thing to try, is to download and install the scenery using the current installer.

Also, you scenery library order seems to be wrong, you have several sceneries that looks like being large-scale areas, on top of many airports. It's always best to put airport sceneries on top of everything else. This doesn't have anything to do with the Addon Manager not finding it, but it's best you do it anyway.

And, as I've said in my previous message, if you enable/disable the scenery in the Scenery Library, this change won't be reflected in the Addon manager, which will always require an FSX restart.

[qqwertz]

Hi Umberto,

I reinstalled all my Virtuali-powered airports and they work again. As for my scenery ordering, it should actually be along the lines that you suggest (except for AES, which always wants to be on top). I just have many airports installed.

Thanks,
Peter

[qqwertz]

Hi Umberto,

I am sorry I have to revitalize this problem again, but I keep getting problems with all Virtuali-related addons (I have GSX, KDEN, KPHL, CYVR). I am now using P3D 2.5, but it is the same problem as before: suddenly, all my Virtuali addons behave as if they were in demo mode (no buildings, blurry ground textures), even though the addon manager shows that they are active. Reinstalling the addons solves the problem, but I don't consider this an option because it means I have to spend half an hour doing this every couple of weeks. Apart from being annoying, this doesn't solve the problem that very often I discover that the scenery is not installed on approach, and some of my other addons don't like when I do not land on a proper runway. I am currently holding back on getting more sceneries from FSDreamteam etc because of this issue.

Here is the couatl log file of my latest flight to CYVR. Any help would be appreciated.

Thanks,
Peter

Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.0 (build 3156)
log started on Sat Sep 12 10:27:01 2015

connecting to SimConnect...
connected to SimConnect
bglmanx non ready yet, waiting.

[virtuali]

Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.0 (build 3156)
log started on Sat Sep 12 10:27:01 2015

You are not using the current version of the program, the one that fixed the problems with the cache regeneration we had in the past with systems too slow to regenerate their cache.

Which is odd, since you say you must keep "reinstalling the addon" (which is obviously not needed, at all), but it's impossible that, by reinstalling any FSDT addon, you would get the old version by mistake, since the Couatl.exe file is *DOWNLOADED* by the installer when it starts.

The only possible explanation why you are not getting the current Couatl.exe is that your antivirus is mistakenly blocking the download, so you are still stuck with the previous version, or the one that was contained in the installer (if the download doesn't work, the installer contains a Couatl.exe anyway, but it might not be the current version).

Do this, and don't skip ANY steps:

- Restart Windows.

- Be sure you disable all antivirus when installing

- Uninstall by replying YES to the question "Do you want to remove the Couatl scripting engine?"

- Check the sim folder and be sure the fsdreamteam\Couatl folder is not there anymore, or it's empty. The installer is supposed to remove it, but it's also possible that a defective antivirus might have blocked it from doing that too. If the folder is not empty, something is wrong, and you must remove it manually

- Reinstall using the latest version of the installer on our site.

[qqwertz]

Hi Umberto,

thanks for your quick reply. The only anti-virus protection I use is the standard Windows 10 Defender (I am using this PC for flight simulation only, there are no "serious" data on it, not even email). I have followed your suggestions and disabled the Defender and then did a complete re-installation of all Couatl powered products. As usual, they work fine after that. I will wait for a few weeks to see if the problem returns. If I don't write here again then this procedure helped

Just to make sure: the Couatl log now shows

Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.0 (build 3171)

I suppose that is the latest version?!

Thanks,
Peter

[virtuali]

As usual, they work fine after that. I will wait for a few weeks to see if the problem returns. If I don't write here again then this procedure helped.

Just to make sure: the Couatl log now shows

Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.0 (build 3171)

I suppose that is the latest version?!

Yes, you now have the latest version, as of today.