While trying to take a long distance image of Sydney, Australia in a World Update that has had a lot of praise heaped on it for its scenery, I ended up with this juxtaposition.  Asobo has undoubtably delivered what some have said is the best scenery of any the recent popular flight simulators.  But it's not all about the scenery. Out of the box, the default aircraft are not lacking attention either.  Yes, everything is too shiny and new looking (especially around hard working landing gear) but heh, I did say out of  the box, right? 

As I did the virtual walkaround, on this calm and balmy morning, I felt the Sun gently warm my back, I could smell APU exhaust, and I could hear the high pitched whine of this Dreamliner's 5000 psi hydraulic pumps (either that or my GPU fan is going south😧.... I really should take a closer look at that!!).  The point is, look how far we have come in atmosphere, detail and immersion.  Judging by the offerings we are seeing, 2022 is going to be a good year for MSFS.  

Cheers

Terry       

   

Edited February 17, 20224 yr by Lord Farringdon

Nice shot!! Really awsome.

Long hauls still tend to dip my frames over time, but yeah, it is still mind blowing sometimes!

9 minutes ago, Victoroos said:

Nice shot!! Really awsome.

Long hauls still tend to dip my frames over time, but yeah, it is still mind blowing sometimes!

Hopefully SU8 will have that fixed for you finally

1 minute ago, blueshark747 said:

Hopefully SU8 will have that fixed for you finally

is that the idea/ in the changelog of the patch? but nice! Who knows ^^

Is  the FPS issue people are having with long flights mentioned in the beta test notes? The last developer update, they said they can't recreate the problem, and that's with volunteers flying 24-hour flights. They need to reproduce it before there is a chance of fixing it, assuming it isn't something external (local to the user) impacting the GPU.

1 hour ago, March Hare said:

Is  the FPS issue people are having with long flights mentioned in the beta test notes?

I don't have this issue, at least w/ 6h flights which is about my max.  I used to see it regularly but not after I got on to trying to estimate the processing overhead of the destination airport relative to the departure airport, and adding a little bit of headroom on top in case of a misestimate.  For example, I'm flying say out of RD's CYOW to FT's KLAS.  Both airports have considerably steep processing demands, but FT's KLAS is considerably greater.  I will see VRAM up to 11.6Gb in spots at FT's KLAS, whereas at RD's CYOW around 9.6Gb tops.  I always start my flight, just prior to engine start, by opening Dev Mode to view the MainThread in milliseconds, and after using it to configure settings, turn it back off--this toggle is done to lose the white logging spinner which creates a microstutter whenever it displays in the lower right corner of the screen.  

For my system which is more CPU bound, the golden rule is to setup the flight such that the MainThread is at ~20ms at departure as my starting configuration.  So in the example above starting at RD's CYOW, I am able to set Terrain LOD at 220, and Object LOD at 200, and still see the MainThread at ~20ms.   All other settings are at Ultra.  Being aware that KLAS is considerably more demanding than CYOW, and that Terrain LOD in particular is hard on the MainThread, I will then dial back the LODs to 150.  As additional insurance, I will reduce Buildings to HIGH.  Now, when I look at the MainThread, we're at ~17ms instead of 20ms.   We take off w/ perfectedly smooth stutter-free 30fps Vsync enabled for my 60Hz non-Gsync display.   Upon arrival at KLAS, we remain locked steady at 30fps, totally smooth.   Now when I opened Dev Mode to see how well I guessed at the greater demand at FT's KLAS, I see it's 22-23ms, so I underadjusted a bit.   Because I started at ~17ms I still had a little headroom to cope with higher MT demand at KLAS and the landing was smooth and trouble-free, even though I was hopeful I would be seeing 20ms at KLAS.  IOW, you really need to build in headroom, not just look at how things are at the departure airport.  And it's easy to be fooled by this.  Plus, there probably is some ongoing accumulation of processing overhead that is greater than at the start of a flight which is understandable and contributes to the issue.  This being said since learning this ritual i don't have poor landing performance unless I just failed to appreciate the arrival airport impact which doesn't happen often now.