The Italian WU seemed to introduce this issue; cities with already very good PG pre-update (eg Napels), were given an apocalyptic make-over by hyper-generation of ugly trees. They posted than an update saying it was solved, but it isn't. There are many PG cities with too many trees and the latest city update seems to have the same issues, as described in this video and highlighted in the comments:

(18) Microsoft Flight Simulator - BEFORE and AFTER - City Update 1 Comparison - YouTube

Oddly, not all cities seem to have the issue. When will they finally fix this extremely annoying bug?

 

Trees is one thing, what I personally do not get is how the heck you can knowingly replace more or less good looking autogen bridges with this word not allowed from photogrammetry. Especially in Cologne, the Hohenzollernbrücke had a pretty decent 3d model in the non-photogrammetry rendition of the city and now with photogrammetry, we get this ugly blob with solid box below the bridge. Ridiculous...

My own recent experience with PG cities and trees goes to the opposite extreme. In the last WU for USA, PG was added to the city of Charleston, West Virginia, near where I live. The City of Charleston itself looks absolutely amazing and totally realistic. Asobo could not possibly have done a better job with the city itself. However -- for dozens of square miles surrounding the city, there are no trees at all. No trees at all on lush West Virginia mountains where, before the WU, trees were dense and ubiquitous. Also, the mountains themselves are horribly discolored in ugly shades of yellow and purple and brown, with unnaturally straight lines dividing one discolored area from another. If I turn PG off, the trees surrounding Charleston, WV, return and the discolorations go away. I don't understand why Asobo's beautiful work on downtown Charleston should so affect the area encircling the city. If you want to see what I'm talking about, take off from KCRW (Yeager Airport in Charleston) and head west toward Huntington, WV. Once you reach an altitude of several thousand feet, take a 360-degree look around. Again, before the last WU for USA -- or with PG turned OFF -- the area looks perfectly fine. 

They really need to sort those bridges out. How anyone can accept them as solid blocks is beyond me.

For oversized photogrammetry trees, please make sure to vote here:

https://forums.flightsimulator.com/t/trees-are-still-hilariously-large/433239

https://forums.flightsimulator.com/t/oversize-trees-in-photogrammetry-areas/402152

For the solid photogrammetry bridges, vote here:

https://forums.flightsimulator.com/t/fix-photogrammetry-bridges-so-that-they-are-not-solid-underneath/326917

I had to remove Bijan's seasons mod because the SU10 made the trees look horrible.

1 hour ago, Waldo Pepper said:

I had to remove Bijan's seasons mod because the SU10 made the trees look horrible.

I had removed it awhile back after noticing that it removed the 'Hollywood' sign but left it's shadow marks.

I forget who posted this method here first, but if you change all the minimum and maximum entries in this file, the trees will all be shorter everywhere.

10-asobo_species.xml

I opened the default file and the flightsim.to patch file side by side in order to see how it's done. So I could  see exactly how to easily make yet another file producing even shorter trees. It's easy, but takes awhile, because you have to change the min and max for every line in the file for all the different types of trees. Boring!

https://flightsim.to/file/392/tree-height-modification-for-mfs2020-shorter-realistic-trees