Outstanding work, and fingers crossed the ticket gets marked as “Solved”, and gets added to their list.
Good find! That explain not intentional downgrade from the Q@A, it’s a bug, these started since release to patch, trees\building there is always tweaking on these it did reduce LOD indirectly.
Actually from alpha to release it was reduced, and on patch 2, this was not intentional LOD reduce, because of the height vs LOD bug.
Wow nice find
Another great find from you, after getting to the core of the building height bug.
They really should pay you for all the actual beta testing you are doing for them.
Cool. Thank you. Is there anything we can do in the mean time to keep the tree draw distance up? I don’t particularly care if the trees are too tall, though I understand that others do.
The problem is not only the size of tree, there are too much trees in lot of places. This impact the realism and performance.
Bushes are taken for trees, shaded roads are taken for rows of trees, shaded areas in town are taken for trees …
It’s not just with trees. The draw distance of objects seems to be directly related to their size. So small cones on a runway disappear much earlier than a windsock, which disappears earlier than a hangar…
Nice find. I hope Asobo can analyze this.
There is no much we can do for now but Asobo identifying and resolving the problem in their code. In the meantime, you can still use the Trees-Fix-75pct_max community fix to lower the size of the tree along with Trees LOD set to HIGH or ULTRA depending if you fly more over Decideous (mostly plains) or Conifer (mostly mountains) respectively.
Just going to keep them default for now. The draw distance is much better. Personally I like to see them in the distance while flying.
(sorry SurlierMovie919 the forum limits to referencing 10 people max!)
Thank you all for your kind words!
I’m glad their latest feedback snapshot is mentioning next patch (#4) will fix the buildings.
However there remains a lot of “tree and LOD” related posts which investigation isn’t even started:
There is valuable information in all these discussions but this is all spread out and buried in various posts. This is one of the reason I’ve tried investigating and documenting at least a single problem related to trees and ring distance which I hope will be helping Asobo finding a solution faster.
We also must try getting their attention to the information I’ve disclosed in raising the vote count above their minimum threshold (the 30th in their list is 142 votes and this discussion is only at 50% of this threshold).
Let’s help us all: please cast your vote to this discussion and tell your friends!
I swear sometimes I think developers are just better off opening their code up to the community. Imagine if you all had access to everything you needed to tweak to your hearts content?! The scenery modders, The A320 team, the G36 team, the G1000 team, everything would be done within a few months
EDIT: Removed “guys” because it’s 2020.
I thank you for your vote of confidence!
You might be onto something though because history shows the most prolific mod creativity often come with the most open platform.
However I imagine in this case, one of the first thing I’ll probably do is making sure you’d get the Reality XP GTN 750/650 and the Reality XP GNS 530/430 V2 in FS2020!
it is also called SmallPartRejectRadius, it exists since FSX - I tried to add it in FS2020 .cfg too , but it doesn’t seem to work ! SmallPartRejectRadius - fix disappearing traffic in FSX Steam • C-Aviation !!
I didnt catch anything while scanning through the other posts and forgive me if this has already been addressed but is this tree height and tree LOD issue also dealing with photogrammetry trees? Or are those 2 completely separate issues? For me it seems, that thr photgrammetry areas have a lot of issues with trees not rendering in until you are almost on top of them, even with your LOD set to 3 and higher.
Also: Microsobo needs to hire you ASAP
These are handled differently but they share a common LOD problem: LOD rings are usually too short.
Is there a way to turn trees off completely? Setting them to low helps yet there are still trees everywhere in the desert. For example
The AI interprets shadows on the sat/aerial images as trees and creates entire forests where there is nothing but bare rocks and sand
This is AI at work and in my opinion this can probably be solved only if:
- Zendesk bug report so that they use enhanced inference rules about terrain nature (long term).
- Probably using the SDK and adding an ‘exclusion’ polygon over the area (short term)