Just recently have noticed that my autogen trees have virtually disappeared over my VFR photoscenery of the UK and France, buildings and other structures are fine.

When I reviewed the Prepar3D.cfg I found that this had altered:_

[sCENERY]
POP_FREE_AUTOGEN=1
AUTOGEN_BATCH_LOD=2
AUTOGEN_TREE_MAX_DRAW_DISTANCE=1500.000000
AUTOGEN_TREE_MIN_DISTANCE_TO_LOD=0.000000
IMAGE_COMPLEXITY=3

On comparing the Prepar3D.cfg with my backup I found this entered:_

[sCENERY]
POP_FREE_AUTOGEN=1
AUTOGEN_BATCH_LOD=2
AUTOGEN_TREE_MAX_DRAW_DISTANCE=9500.000000
AUTOGEN_TREE_MIN_DISTANCE_TO_LOD=2500.000000
IMAGE_COMPLEXITY=3

So I modified the .cfg to read as above, did a test flight and still no autogen trees appeared. on checking the .cfg file again the [sCENERY] entries had changed back to this again:-
[sCENERY]
POP_FREE_AUTOGEN=1
AUTOGEN_BATCH_LOD=2
AUTOGEN_TREE_MAX_DRAW_DISTANCE=1500.000000

AUTOGEN_TREE_MIN_DISTANCE_TO_LOD=0.000000
IMAGE_COMPLEXITY=3

What is altering my .cfg every time I load a flight??

Using P3D v2.5, VFRPhotoscenery for UK, UK2000 airports, SLX to load, AutogenConfiguratorMerger was installed some months back when I had no trees appearing in VFRFrance scenery installed. Computer specs:-

Intel i5-2500K @ 3.30GHz Sandy Bridge
MSI Z77A-G45 Motherboard
8GB DDR3 Ram
ASUS NVIDIA GeForce GTX 960
500GB Hybrid SSD Hard drive (main), secondary 500GB HDD, third backup 320 GB HDD plus external SDD of 500GB
OCZ 750 watt PSU
Coolmaster DM-690 case
Logitech Mk260 wireless keyboard and mouse
Windows 10 Home 64bit
FSUIPC4 v4.957 and Nvidia driver 372.90

 

Nigel

Disregard above thread, have upgraded to v3.4 to cure the  problem!