3 hours ago, turbomax said:

I agree, got a lousy 4090 for Christmas because I confess I was too lazy for all those optimisation experiments. Enjoying my new 100 fps without doing anything else, I am done with tuning or overclocking, once and for all (until next round of 7000x3D CPUs next month)😊. Will be interesting to see if/what fps increase this process lasso thingamajig can still provide. I fly mostly VR so Gsync/Vsync is no option. now back to FrameGeneration "nirvana" or is it already Shangrila?

Well your laziness cost somebody a couple grand but that doesn't matter so lucky for you.  Process Lasso thingamajig will give you exactly zero FPS change, but you didn't need that anyway, right? 😅

12 hours ago, somiller said:

Ah, found those settings...but do you use front edge sync or back edge sync?

Thanks!

They seem to be the same, but I use Front Edge.  This is really the key to this amazing discovery--Process Lasso is only addressing a couple of possible contributions to microstutters though most here seem to be fixated on that. 

24 minutes ago, Fiorentoni said:

MSFS is so incredibly well optimized that any further generalized tweaking (mind: not system-specific problems like faulty hardware or a faulty driver etc.) is as sensible as pouring snakeoil over your GPU.

I was very happy w/ MSFS' incredibly well optimization until I discovered true perfect performance every time from gate to gate in any plane anywhere. Despite two years of very decent performance it wasn't until these simple steps were discovered that real perfection ensued.

Thanks for the warning on XP12 I'll not waste "an hour-long analysis of XP12" like you did 😂

21 hours ago, Noel said:

Cool bonus:  you can toggle the limiter on and off while flying w/o stopping by using RTSS' HotkeyHandler.dll.  You can see I use Num * button on to toggle the limiter off and on.  This is useful to see where you would be unlocked.  And if I'm at an ultra demanding airport where the unlocked rate is essentially to my lock at 33/34 I'll run unlocked until up and away, then a simple button press returns me to limited (with its superior FTV and lower demand on hardware):

 

Reference the above hot key, I've allocated a key to the toggle 'frame rate limiter', but I see no effect when pressing it within the sim. 

Just to clarify, once the key has been pressed within the sim, the frame rates should go from locked, eg, 30fps, to unlocked (and vice versa) ?

6 minutes ago, garydpoole said:

Reference the above hot key, I've allocated a key to the toggle 'frame rate limiter', but I see no effect when pressing it within the sim. 

Just to clarify, once the key has been pressed within the sim, the frame rates should go from locked, eg, 30fps, to unlocked (and vice versa) ?

Yep--you need to SELECT HotkeyHandler.dll from the Plug-in's tab--this is not intuitive so you probably missed it.  If that wasn't it take care to not accidentally shut down RTSS it's easy to do.

For reasons I don't understand the B78X HD doesn't perfectly do this--sometimes it will be several frames over the limit off and on, but all other planes work predictably in this regard.

4 hours ago, Ohmsquare said:

Just out of curiosity, do you use head tracking? Unfortunately I have found that 33-34 FPS is generally too low for that and too far from anything that could be called smooth, regardless of the frame time variance achieved (even using RivaTuner with the tweaks in the OP) . 

 

Nope, no head tracking.  Remember:  the 33-34 FPS is only where I keep the lock as for flat screen viewing it's no worse than 50 FPS w/ ultra low FTV, and allows (due to Passive Waiting) to not run CPU/GPU maxed out as there is no advantage whatsoever.  Up in the air it's easy to get 50-70 FPS depending on scenario but there is simply no visual benefit including rapid panning in cockpit which is already perfect at 33-34.  People find that hard to swallow, but that is my sincere take having done it over and over.

8 minutes ago, Noel said:

Yep--you need to SELECT HotkeyHandler.dll from the Plug-in's tab--this is not intuitive so you probably missed it.  If that wasn't it take care to not accidentally shut down RTSS it's easy to do.

 

For reasons I don't understand the B78X HD doesn't perfectly do this--sometimes it will be several frames over the limit off and on, but all other planes work predictably in this regard.

Thanks, but as I said, I have allocated the hot key (via HotkeyHandler.dll), it just doesn't seem to do anything in the SIm when I press it ?

Btw, a/c is Fenix A320. 

22 hours ago, Noel said:

NV Control Panel:  all default global, except Low Latency is set to Ultra

I don't know how many times I have to tell simmers this doesn't do what they think it does. 🤦‍♂️

7 hours ago, f.skywalker said:

@Noel

Hello Noel,
I also use PL.
Can you attach a picture of your settings in the PL to me, how you did the distribution of the cores.
I also use the Intel 9900K.
I am interested in how the cores for the MSFS are and how you have configured other addons. (FSTL.........)

Many thanks from EDDM
Frank

As you can see from the right scroll bar there are a slew of entries below the bottom of what you see.  The top processes are system processes that don't accept affinity reassignments so those show Cores 0-7, but everything below that is set at 0-6.  You can 'group select' these so very simple to do.  Technically you really only need to do the processes on the Active Process tab however this can change so simple enough to do all processes that might run:

 

 

 

23 minutes ago, garydpoole said:

Thanks, but as I said, I have allocated the hot key (via HotkeyHandler.dll), it just doesn't seem to do anything in the SIm when I press it ?

Btw, a/c is Fenix A320. 

Don't know what to tell you if you show you have actually selected the .dll, and didn't inadvertently shut down RTSS, then it should work, or does for me and others where I learned about this from.  Are you 100% certain you have no other limiters operative? In-sim, NVCP?  The B78X HD does work but I notice it can hover above the lock a few FPS.  To be sure, because it fooled me, yours looks like this?

Edited December 30, 20223 yr by Noel

2 hours ago, Luis Hernandez said:

In my case, the magical number is somewhere between 32 and 36 FPS (1/4 of my max refresh rate in my Freesync monitor). 

Did you learn the migrating tear line that comes w/ RTSS limiter w/ Edge Sync doesn't happen w/ Freesync?  

So far, I've never found the tearline in P3D v5. I'm working on MSFS because is not as smooth as I'd like to, specially during view transitions.

20 minutes ago, Noel said:

Don't know what to tell you if you show you have actually selected the .dll, and didn't inadvertently shut down RTSS, then it should work, or does for me and others where I learned about this from.  Are you 100% certain you have no other limiters operative? In-sim, NVCP?  The B78X HD does work but I notice it can hover above the lock a few FPS.  To be sure, because it fooled me, yours looks like this?

My bad - I assumed that having a tick meant that the dll was enabled, didn't realise that I had to actually click the tick (it was there but greyed out).

All working fine now. Thanks for your assistance and sorry for wasting your time !

7 minutes ago, garydpoole said:

My bad - I assumed that having a tick meant that the dll was enabled, didn't realise that I had to actually click the tick (it was there but greyed out).

All working fine now. Thanks for your assistance and sorry for wasting your time !

It is not intuitive and caused me to contact the developer!  Glad it worked!

46 minutes ago, Noel said:

As you can see from the right scroll bar there are a slew of entries below the bottom of what you see.  The top processes are system processes that don't accept affinity reassignments so those show Cores 0-7, but everything below that is set at 0-6.  You can 'group select' these so very simple to do.  Technically you really only need to do the processes on the Active Process tab however this can change so simple enough to do all processes that might run:

Thank you very much,