I run and cycle and always wear a HRM. Most of the time I don't need to look at it as I know from my effort what's it's going to be. However, if I notice that for some reason it's not, then there's a good chance that something's not right and, in my case, I probably need a few days rest. Hence, I can take immedaite action to remedy the issue.

Point being that it's the same with the FPS counter - better to react immediately and have a good chance at identifying an issue, than to wait until it becomes really noticable, then have work out what's going on...

I changed my setting so that MSFS can deliver 60fps around the Vancouver Area while flying the DA62. To achieve this I had to reduce my setting from all setting be at the maximum to Global Rendering Quality: Medium. I have a program that allows me to change the display refresh rate with a key stroke. I have 4 presets 23hz, 29hz, 50hz and 60hz. So while flying I was switching from one display refresh rate to another and therefore from one locked frame rate to another. I had the Judder reduction filter turned on and set to Max on my TV. The Judder reduction filter works for all refresh rates except 59 and 60. 60hz was smooth so long as the 60fps was maintained, the judder reduction filter was off. While flying around doing step turns and panning the Main thread and GPU where around mid 70's low 80's so not a lot of over head to increase setting above medium which both level of detail setting at 50! With a key stroke I change the refresh rate to 50hz. While flying around doing step turns and panning at 50hz with judder reduction filter on, IMO is better looking than 60hz with no judder reduction filter. Plus the CPU and GPU are in the low 60's so more room to increase those setting. Next With a key stroke I changed to 30hz on the fly and for some unknown reason this appears better than 50hz. In both instances the Judder reduction filter is on. Main observation here is that the Main thread and the GPU are in the Mid to high 30's so lots of overhead to increase setting. And finally, With a key stroke I change to 23hz which look exactly like and a smooth as 30hz. which both look exactly as smooth as 60hz. The main observation at 23hz is that the CPU main core and GPU are at high 20's/low 30's hence at 23hz I can fly with all the setting maxed out and achieve the same fluid and smooth game play that I can achieve at 60hz. There are a couple of caveats. Fast panning at 23hz will overcome the Judder reduction filters ability to smooth the image. I have tweaked this out TrackIR. But in its defence fast panning at 60hz can drop the the FPS below 60fps and that causes stutters. There are definitely pros and cons to either approach. IMO on my system (i9 10900K with all cores at 5.2ghz, HT of on physical core9, RTX 3090, samsung 970 EVO 3 x 1TB and 32GB G.Skill 4000mhz C15)

The choice is perfectly smooth at 23hz (with the right display) with all the setting maxed or perfectly smooth at 60hz with the setting neutered. Chose your poison.