Overall performance has been stellar for me w/ LOD-O at 400, LOD-T at 300, RS 120, and ample GPU/CPU/VRAM headroom.  This being said I was taxiing out of HECA this morning and after pushback, for the first several hundred feet of taxi, turning the plane as needed, just amazingly smooth and stutter-free.  Right after I remarked to myself how phenomenal this was in this complex scenery I had a brief 'shudder' for lack of a better word that lasted just a fraction of a second but disturbed animation very visibibly if briefly.  By the time I got to the 23C threshold this happened another 4 to 5 times or so.  No visible disruption of vsynced 30 frame rate (looking at RTSS), no visible spikes in CPU or GPU use as I say bigtime headroom.  I think it's def happening more w/ the 787-10 (HD mod or not, doesn't matter) than for example w/ Citation Longitude.

It's not always happening but as I say often in complex airports I'll get this somewhat consistently, just a few times per flight.  For reasons I can't explain takeoff itself never involves these.  Turning during taxi may be related, but not always sometimes it's just random.   It's been a while since turning down settings so perhaps that's the culprit that just doesn't correlate w/ RTSS' display of GPU/CPU/VRAM loads which are always very modest overall.  Do you get these too? 

Wow, I think I had underestimated the amount of these shudder/stutter events.  I have noticed somewhat frequently when ATC voice fires there with be one of these events.  But because they don't all generate these shudders/stutters it helped cause me to underestimate how often these are occuring, which as I say is mostly around taxiing.  Well today I DISABLED all text-to-speech under the Sound section of general options, so turned it to OFF, not 'offline'

The next thing we did was to toggle Dev Mode on then off, save and exit Developers section of general options.  This always reduces the spinning circle indicator on the lower right part of your screen by 95%, and in doing so you get less microstutters that often happen when this event fires.  I've zendesked both of these months ago and I was just notified they were 'Solved'--we can only hope they address both of these issues.  But if they don't right now you can do these workarounds.

Long and short of it:  SMOOTHEST FLIGHT IN EVER It's probably too early to say for sure as I have grand total of one test flight showing this perfection, or so very near perfection may have had 1 or 2 ultra bried microstutters, but not sure as I was doing some other things in the background, like taking this screenshot from just after TO from KSAN, heading north over La Jolla and the lovely Torrey Pines Courses, that I think generated the stutter.

Note the benign GPU/CPU/VRAM utilization and again, truly stutter-free:

Toggling Dev mode on and off is fine but the program will then NOT log any of your flight time. Just sayin'.

3 minutes ago, dlermond said:

Toggling Dev mode on and off is fine but the program will then NOT log any of your flight time. Just sayin'.

Yes you're right that and was a reason I detailed this in zendesk and should have mentioned this here thanks.  I really hope they fix it because I'd like to have flights logged, but not at the cost of the microstutters I'm seeing:

June 05, 2021 15:14            zendesk

This is a really important finding please investigate deeply. Here's what happens: the spinning indicator presents variably--sometimes infrequently as every minute, and sometimes virtually continuously. Every time it displays a subtle microstutter occurs. Here's the very interesting part: if I enable Dev Mode, and clear the console of errors/warning/messages, then disable Dev Mode and resume flying, the white spinning indicator stops displaying completely, and performance is realiably smooth again. When I don't do this, a stutterfest can happen, and typically this is in the context of having lots of GPU and CPU headroom to exploit. I'm also finding those infamous 'FPS drops' seem to be associated with this, beyond the microstutter issue whenever the logging indicator displays. It's easy then to get reliably smooth performance by simply going into Dev Mode at the start of a flight, clearing the console, then re-disabling Dev Mode before actually starting the flight. But here's the next issue: when you go into Dev Mode, the flight WILL NOT be logged in the Pilot log! It's easy to see how testers might miss all of this because it also seems to be the case that clearing the console may not really be needed--simply toggling Dev Mode on and off gets rid of the annoying, microstuttering spinning indicator. PLEASE PLEASE work on this it's a real issue for many to most people who may be chasing red herrings when all along this issue was at the core of both weird performance problems, microstuttering, and loss of logging of flights in the Pilot Logbook.

 

One thing I've actually never seen other than when I get the Azure ATC is offline message is the spinning indicator.  I have 1.2Gbs down, my data usage is usually around 49Gig and I set manual Cache to 55 to give a little buffer to my data usage.  

Could the spinning indicator be bandwidth or cache related?  

Edit:  I also have no idea if my settings are correct but I don't get the spinning indicator with those settings.  

Edited September 26, 20214 yr by psolk

So let me get this right, are you suggesting to turn off the AZURE text to speech settings, nothing else?  There are a few options in Sound I just want to be clear what you mean.