7 hours ago, tfm said:

Noooo please not another of those long-winded videos replete with ads and cheerful banter! Nearly 10 minutes in this video for what presumably is a checklist of steps that would take 20 seconds to read.

Could you just write a list of the steps needed?

From the video comments:

Step 1: 2:41 clean up the cache in MSFS. Options>General Options>Data[scroll down]>Rolling Cache>Delete>Apply & Save.

Step 2: 3:11 exit MSFS>Launch Nvidia Control>Manage 3D settings>[scroll down]Shader Cache size> Disable>Exit & Save Settings.

Step 3: 3:45 open Appdata>Local>Nvidia>Keep Folders but Delete ALL files [or sub folders] within DX Cache and GL Cache folders.

Step 4: 4:31 type in Disk Cleanup App>Open Disk Cleanup>Delete ALL in DirectX Shader Cache

Step 5: 5:04 Restart PC

Step 6: Open back Nvidia>Manage 3D settings>set Shader Cache Size to Default.

4 minutes ago, Bert Pieke said:

From the video comments:

Step 1: 2:41 clean up the cache in MSFS. Options>General Options>Data[scroll down]>Rolling Cache>Delete>Apply & Save.

Step 2: 3:11 exit MSFS>Launch Nvidia Control>Manage 3D settings>[scroll down]Shader Cache size> Disable>Exit & Save Settings.

Step 3: 3:45 open Appdata>Local>Nvidia>Keep Folders but Delete ALL files [or sub folders] within DX Cache and GL Cache folders.

Step 4: 4:31 type in Disk Cleanup App>Open Disk Cleanup>Delete ALL in DirectX Shader Cache

Step 5: 5:04 Restart PC

Step 6: Open back Nvidia>Manage 3D settings>set Shader Cache Size to Default.

Thank you so much! 🙏 

So if I understand correctly, if we are using FG, we should NOT be capping FPS with RTSS. ONLY via the NVIDIA CP? 

11 hours ago, Sethos said:

...But alas, it won't end here. You will, again, refute the claim, not do any relevant tests, post the same completely useless CapFrameX graph for the umpteenth time showing you haven't understood a thing and Noel's CapFrameX circus will continue. Have a fine day Noel and I genuinely feel sorry for all the future unsuspecting individuals who will have to face yet another CapFrameX gospel session from a guy who clearly has no interest in furthering his knowledge on the subject.

RTSS's edge sync method was recommended to people without DLSS FG capabilities for its superior frame pacing which becomes relevant when you don't have the horsepower to run higher rates.  Back when you did your original attack you stated this was old hat, consoles have done this at 30 FPS (duh, because superior FTV does matter when frame rates are relatively low). My only challenge to you that you ignored was simply to TRY IT, before aggressively discounting it ad hoc to others which is what you were doing, and that dialogue had NOTHING to do with DLSS FG at the time you went on your original attack trying to discourage others from simply trying RTSS edge sync to see for themselves.  I continue to encourage people to try it who don't have RTX40xx capabilities.  I DID NOT try to get the OP to do this here, though once again several here that do use the method, like McDaniel above, aren't bothered by PC latency associated with RTSS edge sync and FG.  Why do you suppose that is?  Are they lying or pretending too?  I may be a piece of work, but you're just flat out rude and vindictive.

On 10/9/2023 at 7:50 AM, Noel said:

"I must thank @Noel specifically for the advice in this thread - since MSFS was released, the advice in that thread has given me the smoothest experience so far, with higher settings to boot!"   @MrBitsFlyer

11 hours ago, McDaniel said:

I personally use the same approach as Noel, for me personally, smoothness is the holy grail, and in msfs2020 I don't feel or see a draw back. Msfs2020 has never been so smooth and performent like these days.

Why GFE overlay shows Render Latency instead of PC Latency here, I have no idea--I chose Latency in its filters, and that's what appears.  The latency issue doesn't come into play anyway that is why others who actually tried and continue to use RTSS edge sync did not complain nor comment about latency, and the last few to try this were using DLSS FG, dunno about MrBits and McD.  I'm late to the DLSS FG party but have used it enough to state emphatically latency is a non-issue from a perception POV and I'm sure that is why others continue to use it.  In fact I'd give you 10:1 odds in a double-blinded test, in MSFS only, if you could discern the 48ms difference in latency associated w/ FG when edge sync is employed.  The mouse thru molasses is beyond silly, as if initiating a mouse move in which the pointer moves 48/1000's of one second later can translate to 'sluggish' in any honest person's mind.  I think you're lying now or pretending.  If you hadn't read about it or measured it yourself you'd not have been deterred by latency, just like myself and the others who do use RTSS edge sync.

So yes it's not going to end here and is why I am passionate about this for those w/o FG capabilities especially.  As stated in my original post linked in MrBitsFlyer's comment above once you can crank out 60+ frames ultra low FTV becomes less important in the perception of smooth animation.

 

48 minutes ago, iFlySimX said:

So if I understand correctly, if we are using FG, we should NOT be capping FPS with RTSS. ONLY via the NVIDIA CP? 

Have you been using RTSS edge sync?  If so, were you plagued by input latency?  This is the known issue with RTSS with regard to DLSS FG.  In case you're not familiar input latency refers to the time interval between when an input is initiated by you, and when the associated action commences.  For example, do you notice a delay when you move the mouse, a controller, or hit a key, when using FG w/ RTSS edge sync employed?

18 hours ago, Noel said:

Have you been using RTSS edge sync?  If so, were you plagued by input latency?  This is the known issue with RTSS with regard to DLSS FG.  In case you're not familiar input latency refers to the time interval between when an input is initiated by you, and when the associated action commences.  For example, do you notice a delay when you move the mouse, a controller, or hit a key, when using FG w/ RTSS edge sync employed?

Should it be BACK edge sync or FRONT edge sync?

16 minutes ago, iFlySimX said:

Should it be BACK edge sync or FRONT edge sync?

It doesn't matter iFly, either one does the same thing. 

21 hours ago, Bert Pieke said:

Step 6: Open back Nvidia>Manage 3D settings>set Shader Cache Size to Default.

I would leave the Shader Cache disabled. It's a relict of old old times where CPU, Ram and HDDs where really slow. But with todays hardware you will not

(I didn't) notice a difference in loading MSFS, perhaps a few ms delay.

And you get rid off the problem with outdated shaders.

Well, as I made an account here why not share something regarding RTSS which hasn't been reported here afaik. I've made a post in MSFS-forums about this: RTSS w/ NVIDIA REFLEX (pictures included). In short, RTSS has an option in setup where user can choose the framerate limiter mode (async, front, back, reflex). We should be using the reflex-mode here with fixed-sync monitors instead of the others which cause several problems as detailed in this thread. As a result, most of the lag vanishes as it should due to reflex being in control.

All the best & take care :3

 

With Nvidia Reflex enabled in RTSS, I get stutters again. Perhaps it has also something to do with Gsync, because it's not a fixed sync monitor.

The (measured) average PC latency is reduced by approximately the half with Reflex, but this did not justify the introduced stutters for me. I personally can live with the higher latency, but for that I'm getting absolute smooth flights.