Limited by render thread

Just to clarify, when I said their scenery is ‘terrible’, I did mean for polygon and texture counts and size, and not quality. Clearly Google data is of great quality, but it’s meant to be run in their app, not a flight simulator of the complexity of MSFS. Google Maps doesn’t need high frame rates or the processing horsepower that MSFS needs. In this application, it’s terrible. For performance.

If someone rips models out of Google, optimizes them in Blender, and brings them into MSFS properly, that’s one thing. But the majority of Google scenery packs out there are made by unskilled kiddies who watched a basic YouTube tutorial and decided they wanted their home town in sim, then shared their work on one of these 3rd party sites.

There are some airports that just have horrible performance, even with stock data. EDDF is a known one. Another complete slug is Charles de Gaulle. KLAX and KJFK are also poor performers. Nothing seems to have been done about them so far.

1 Like