I’ve examined Bijan’s thread and acknowledge that he (or she) has made a contribution to the tree issue for various specific locations and may have tinkered with settings to reduce size of trees either locally or globally, (which is all very well), but, unless someone can confirm the addition of said hack or add on can resolve the issues, I see no specific answer to my own concerns buried in the contributions and comments, eg, a simple means for an individual to edit or resize any offending trees they may discover in their own back yard, so to speak.
Also, and I think this is a very pertinent point, mere days after investing between £69 and £199 in purchasing the software, why would a brand new customer, (or a customer upgrading from FS2020), even have to consider what appears to me as resorting to an 'unofficial ’ hack to finnesse or improve a brand new product that really shouldn’t have this frustrating kind of an issue?
I mean, yes, sure, the concept of allowing “the community” to create innovative add ons and hacks is cool, but should Asobo be permitted to just sit on their hands and rely on members to clear up or make work arounds for their own failings?
The tree thing initially spoiled my enjoyment of FS2020 until I found ways of working around the issue(s) and it really grinds my gears that I’m facing what seems to be an even bigger failing in this offering, especially considering all the hype and bull about this version enjoying the benefits of a ‘digital twin’ of planet earth.
Members. If you are saying Bijan’s add on will resolve the issue I have highlighted, please reassure me that adding such a DIY fix isn’t going to compromise the officicial installation. (I’m assuming Bijan is a regular punter and not a paid up member of Asobo or MS but, again, sure, enlighten me if I’m wrong about that).
And Microsoft / Asobo; please add a basic switch or button or setting to enable a user to edit the size and siting of trees or, in a more radical way, at least give us the opportunity to turn trees off entirely.