I believe this is a limitation of blending Photogrammetry and Satellite imagery.

It's two sets of data, taken on different days, potentially different months in potentially different seasons from different altitudes and angles.

Take a photo of your own street in mid December and then try to blend it with an image of your own street taken in June and this is probably how it would appear. 

I am slewing due South West 225 degrees from KCRW Chuck Yeager (Charleston West Va.) to KTYS McGhee Tyson Airport (Knoxville, Tennessee). 

======

Over KCRW

--------------------------

Further along going South West still

------

Still heading South west, you can see McGhee Tyson below on the right

-----------------

Directly over McGhee Tyson

 

KCRW by ORBX

KYTS by FSXcenery (Simmarket)

Solution Found (in a roundabout way)

I want to thank everyone who opened my eyes to many issues regarding the photogrammetry problem I experienced after WU10. To re-state: Charleston, WV, got a photogrammetry makeover in WU10. The city looks great, but the photogrammetry trashed a twenty mile radius outside and surrounding the city.

I thought I was faced with only two possible solutions, neither of which was appealing. I could either (1) turn off photogrammetry to make the area surrounding Charleston look good again, or (2) delete WU10. But I didn't want to do either of these options because WU10 was a good addition to the sim, especially the enhanced elevation data.

At this point I discovered something very odd and surprising -- something that I bet even you true experts don't know. It seems that the "3D Photogrammetry Cities" file included with WU10 contains photogrammetry only for the tiny number of new photogrammetry cities added with WU10. If you delete this file entirely, all the remaining photogrammetry cities in the USA -- the vast majority -- are unaffected. So I deleted the file and that returned the Charleston suburbs to their pre-WU10 appearance. However, I'm continuing to enjoy the photogrammetry of the remaining 99% of the cities that had photogrammetry prior to WU10.

Some users expressed a similar experience with the new Boise, Idaho, photogrammetry. So you might do a search for, and then delete, the "3D Photogrammetry Cities" file which is part of WU10. There is no need to delete WU10 entirely and lose all the other improvements it brings nationwide.

Edited June 22, 20223 yr by David Mills

7 hours ago, David Mills said:

Solution Found (in a roundabout way)

I want to thank everyone who opened my eyes to many issues regarding the photogrammetry problem I experienced after WU10. To re-state: Charleston, WV, got a photogrammetry makeover in WU10. The city looks great, but the photogrammetry trashed a twenty mile radius outside and surrounding the city.

I thought I was faced with only two possible solutions, neither of which was appealing. I could either (1) turn off photogrammetry to make the area surrounding Charleston look good again, or (2) delete WU10. But I didn't want to do either of these options because WU10 was a good addition to the sim, especially the enhanced elevation data.

At this point I discovered something very odd and surprising -- something that I bet even you true experts don't know. It seems that the "3D Photogrammetry Cities" file included with WU10 contains photogrammetry only for the tiny number of new photogrammetry cities added with WU10. If you delete this file entirely, all the remaining photogrammetry cities in the USA -- the vast majority -- are unaffected. So I deleted the file and that returned the Charleston suburbs to their pre-WU10 appearance. However, I'm continuing to enjoy the photogrammetry of the remaining 99% of the cities that had photogrammetry prior to WU10.

Some users expressed a similar experience with the new Boise, Idaho, photogrammetry. So you might do a search for, and then delete, the "3D Photogrammetry Cities" file which is part of WU10. There is no need to delete WU10 entirely and lose all the other improvements it brings nationwide.

Good idea.

In the past when I deleted anything from the main store folder, MSFS upon loading would just download the area again. I always used the content manager to delete any scenery areas. There is a thread on improving performance that shows that deleting just a few PG (WU) files with the CM, results in better fps.

How did you delete the area and which files did you delete?

I would also prefer to be at pre WU10 for the area. I do have a backup, so I can test.

Thanks for sharing.

Jose

10 hours ago, CFIJose said:

Good idea.

In the past when I deleted anything from the main store folder, MSFS upon loading would just download the area again. I always used the content manager to delete any scenery areas. There is a thread on improving performance that shows that deleting just a few PG (WU) files with the CM, results in better fps.

How did you delete the area and which files did you delete?

I would also prefer to be at pre WU10 for the area. I do have a backup, so I can test.

Thanks for sharing.

Jose

I deleted the 3D Photogrammetry Cities file (of WU10) using the Content Manager. The Charleston area now looks good again -- and I did indeed notice a significant increase in performance, even when flying in areas thousands of miles away. I have no explanation for this FPS improvement, but I'll very happily accept it.

I did of course have to forfeit the photogrammetry of Charleston, WV. But in a very lucky coincidence, the KCRW ORBX airport package I recently purchased adds very accurate buildings and bridges and stadiums and other structures to downtown Charleston. So as is often the case, an initial frustration led to good advice from this forum, which in turn led to my ending up with better graphics and better performance than ever! All you guys -- and Jane! -- are fantastic.