Vegetation and/or Autogen Buildings are Missing

Steps to resolve:

1.  Check your settings in Prepar3D. In Prepar3D go to Options -> Graphics -> World and check that the autogen building/vegetation sliders are not pushed too far to the left (which would mean that only a few items or nothing get displayed
2.  Update your Orbx Libraries. Open Orbx Central and select My Products -> Other -> Orbx Libraries and click Verify files.
3.  Check if you're seeing the smaller churches in populated areas (UK) or typical red farm buildings in rural areas (US) or powerlines (not meaning big POIs like Westminster Cathedral or Space Needle!). If you see those smaller objects, the problem is fixed!

If not, this will lead you to our next step:

Background: Some sceneries out there add their entries through the so-called "add-on.xml" entries in Prepar3D. Problem is that some of them add new autogen descriptions through that method which may eliminate some of the autogen from other sceneries like TrueEarth for Prepar3D! This was caused by a few developers assuming that additional autogen entries are possible (as described in the SDK) while in fact, it was only possible to overwrite all previous entries with new ones (this will be hopefully fixed in a future Prepar3D version making this post obsolete). Even worse the problem will NOT show in the sceneries actually causing it. While everything looks fine there, they cause disappearing autogen in other sceneries that can cover entirely different parts of the world!

Known sceneries causing this problem so far are:

Aerosoft's Chania -> Fixed with an update. Check Aerosoft's support page.

Aerosoft's Lukla Mount Everest - Extreme -> Fixed with an update. Check Aerosoft's support page.

However, there may be other addons out there that are causing this issue.

In Prepar3D, Select Options -> Addons and uncheck all scenery addons you find there. Then restart Prepar3D.

After that, you should see everything in TrueEarth as it is supposed to be! Check a previously faulty area and see if the error is fixed.

By reactivating one addon after another (and restarting Prepar3D each time!) you can find out which addon sceneries are causing the problem. We are aware this is a very cumbersome task, so please report if you find any other sceneries causing this issue and let us know so we can contact the applicable developers about it!