I finally updated to P3Dv4.5 Hotfix2-Client only

I have an Orbx setup with all the bells and whistles-all is good

However I notice a lack of vegetation especially trees compared to P3D 4.5

Anybody else have this problem?

Posted on Orbxforum and Aerosoft Lukla installation has been suggested as a possible culprit

xxd09

Edited November 6, 20196 yr by xxd09
Spelling

Thanks for prompt reply Rob

Yes -did that

Following Nicks advice over on Orbx P3Dv 4 forum-I disabled Aerosoft Lukla in its latest incarnation and all is restored!

Nick did also mention another Addon that is maybe causing problem in New Zealand area

xxd09

Edited November 6, 20196 yr by xxd09
Spelling

Does installation of Aerosoft Lukla only affect autogen trees outside of that area? Otherwise I would have expected something like that to be picked up during beta testing.

I am using Aerosoft Lukla with their custom autogen area and have not experienced any problems with autogen trees in any other areas.

The custom autogen of Lukla is the issue. For some reason, every time I enable a third party addon's custom autogen (trees or buildings or anything, for that matter), I start lacking trees globally. 99% sure that this is somehow related to OrbX and how they change your autogen files. I first discovered this issue when trying to enable a rendition of Albuquerue with custom vegetation autogen, then found that Richer Sim's Caribbean sceneries, TropicalSim's 3D light autogen for their sceneries had the same effect.

Not sure how to fix it except to get rid of all third party autogen except OrbX...

It should not be necessary any longer if P3D v4.5 is installed, however, I'm still using Autogen Configuration Merger tool by SceneryDesign.org 

Install once and forget, it handles multiple autogen libraries. I've not had missing autogen since I've started using it.

8 minutes ago, F737NG said:

It should not be necessary any longer if P3D v4.5 is installed, however, I'm still using Autogen Configuration Merger tool by SceneryDesign.org 

Install once and forget, it handles multiple autogen libraries. I've not had missing autogen since I've started using it.

So whenever I missed the trees, it's always when I added the new autogen through addon.xml. I'm not sure I ever tried it with ACM, but given the troubles I have with the addon.xml method, I'm somewhat hesitant to do it the ACM way. It seems much more permanent. I have resorted to not adding any additional autogen configurations anymore, as all of them cause issues for me.