NZAA,

I assume the 1% and 0.1% are percentage of all frames. Those lower fps at 1% and 0.1% represent a hiccup, or interruption in the normal smooth cadence of frames...would appear as a slight pause or skip. 10fps = 100ms (1/10 sec.) frametime which is over 4X the normal cadence of 43 fps average. 1% seems like a really low percentage, but remember if you're running 30 fps normally, then 1% would be a skip every 3.3 seconds. A perfectly smooth sim is somewhat subjective, but objectively would be 1% and 0.1% never going below average fps. With vsync it would be never going below refresh rate.

26 minutes ago, somiller said:

NZAA,

I assume the 1% and 0.1% are percentage of all frames. Those lower fps at 1% and 0.1% represent a hiccup, or interruption in the normal smooth cadence of frames...would appear as a slight pause or skip. 10fps = 100ms (1/10 sec.) frametime which is over 4X the normal cadence of 43 fps average. 1% seems like a really low percentage, but remember if you're running 30 fps normally, then 1% would be a skip every 3.3 seconds. A perfectly smooth sim is somewhat subjective, but objectively would be 1% and 0.1% never going below average fps. With vsync it would be never going below refresh rate.

vsync means it never goes above the vsync rate, but it can still drop below. If a frame is late it gets skipped and you will get micro stutters and if your card is really struggling it will basically refresh every second frame and give you a fps of half vsync.

Otherwise more or less correct though the average fps and 1% and 0.1% average lows are probably calculated over much longer than a second.  So depending on the sample time used by the monitoring software you may have long periods sitting over the final average marred by quite a few seconds at a time where the frame rate drops to the 1% low. 

I check my Ram use in my last flight with TBM 930 and it was using 22 gb of my 32, but then I had One Air, Little NavMap, Spotify and my Chrome browser open in the background at the same time.

Edited March 7, 20215 yr by Ixoye

Very interesting link/video.  There is probably another question here as to what percentile cutoff for choosing low frames is significant for a given user.  The 0.1 and 1% values shown are very interesting, but it might be that the average user becomes frustrated by 5 or 10% or some other cutoff in the distribution of rendered frames (per sec).

After fighting settings and hardware but still being smashed down to single digits in FSX, then P3D3 and 4 (much lesser extent P3D5), can I just say what a pleasure it is that MSFS in most cases just gets on and uses the GPU, processor and memory available.  The need for ProcessLasso, cfg tweaks, and different setting profiles seems much less.  

May eat my words when A2A, PMDG etc finally arrive  🙂

5 hours ago, RobF2 said:

Very interesting link/video.  There is probably another question here as to what percentile cutoff for choosing low frames is significant for a given user.  The 0.1 and 1% values shown are very interesting, but it might be that the average user becomes frustrated by 5 or 10% or some other cutoff in the distribution of rendered frames (per sec).

Ideally the frametime graph should be a flat line with constant framerate and frametime. The flatter it is, the better is.

43 fps avg and 1% low 10 fps means that every 100 frames, one frame takes 100 ms to be rendered instead of 23 ms.

100 frames are rendered in 2.3 s (average) in that video. This is definitely perceivable as stuttering.

5 or 10% low 10 fps would be a stuttering mess.

Edited March 7, 20215 yr by MrFuzzy

I am using 32 gig and personally think this

is the best choice for MSFS.

Most people have other Windows open ( LNM ) and so on like me, this works pretty well with this Setup.

cheers 😉

Edited March 7, 20215 yr by pmplayer