I’m really enjoying flying around anywhere I want and having such true to life scenery. However, many cities in particular look like they’ve been abandoned for decades and become overrun with massive vegetation. I like flying to various state capitols in the U.S. and finding the capitol buildings but many of them have massive trees growing in them that show through. (I would have included a screenshot but I only fly in VR these days and there is no way to program a screenshot function to my controls from within the sim (and I don’t like fiddling in with the external apps).
I’m not a dev but I’ve tinkered with some programming and it seems to me there should be someway to stop trees from spawning in and around buildings. And maybe tinkering with the maximum size of trees located within urban areas (or within a certain distance of buildings) might help this problem. I realize that many cities do have some big trees around, but I think making the mistake of undersizing some trees would look a lot better than the situation as it stands now.
BTW, this has been a significant issue since the beta at least. In fact, I did post some screenshots back during the beta of buildings with trees growing out of them, so I was a bit disappointed to come back to it a year later and see the same problem.
Agreed. Some areas get downright ugly from 500 feet give or take. There shouldn’t be trees IN the road. Presumably they know where the roads are right?
Another thing I find puzzling is the roads/streets in urban areas (LA or Seattle suburbs for example) that have road markings, but don’t look anything like pavement/concrete/blacktop. The sim clearly knows it’s a road…there are cars driving on it and it has markings and it’s in or near a city, but the autogen paints it green. Surprised this doesn’t get more attention.
The size of trees in photogrametry areas are much bigger than those without for some reason. Turn the PG off and trees return to something more sensible.
That’s indeed what happens. Areas without photogrammetry look just fine, especially after SU6 and the tree LOD fixes. Photogrammetric cities however seem to have a tree scaling issue.
I had the same observation and my suspicion after some tests was confirmed by the 3rd party developer “Bijan” in this forum:
Photogrammetry trees are usually perceived as ugly, especially in old photogrammetry data like in Nuremberg. Dedicated 3D models look nicer and blend better with the landscape having no photogrammetry. Thus Asobo does the trick of hiding the photogrammetry trees beneath 3D models which are modified so they always show in the foreground. In order to more or less completely hide the PG tree blobs the 3D models must (a) be larger than the tree to be hidden and (b) they must be evergreen for the camouflage to work all year round.
The result is oversized 3D evergreen tree models in many photogrammetry cities like Nuremberg, Berlin, Vancouver, Paris etc.
Thus I am sure this is by design, and it’s the lesser evil they chose.
If you purchase Bijan’s “Seasons Enhanced” addon (for FS2024) and remove the files for the photogrammmetry exclusion polygons then you will see what happens otherwise: With his correctly sized trees you will see the photogrammetry PG tree blobs within the tree models and it looks equally poor… just a different type of poor, so to say.
Now, can this get fixed?
Just imagine trees (e.g. conifers) standing in close to the front of buildings so that you cannot see the facade behind. It’s simply impossible to get a photo of the facade from the air without the trees, agreed?
Since even newer photogrammetry models with better quality cannot get completely rid of the trees without removing parts of the buildings behind them, this is almost a “Won’t fix” issue. I say “almost” because as technology advances it might become feasible to use some (maybe AI-powered) algorithms to detect and get rid of the trees in the 3D mesh anyways and then fill in the created gaps in the facades behind and the ground below with “something plausible”, then place (only) the 3D tree model over it and maybe if the 3D tree hides the correction well enough then you might not notice it until looking very closely.
I hope I could explain this well enough.
