40 minutes ago, Noel said:

Do you think it's significantly superior to what we got out of original Dynamic LOD?  Because of the older 9900K I really dial down TLOD on the ground, down to 20 at really tough airports, and it helps hugely.

IMO AutoFPS is much more intuitive to use. You can e.g. set TLOD minimum 20 at tough airports and while descending on approach, the app will gradually reduce TLOD until it reaches the min value at 1000 AGL. Below that it's locked. 

I find this works better than using pre-defined AGL levels, as I prefer the app to dynamically change TLOD (and OLOD) in order to reach the minimum at 1000 AGL. 

Edited February 27, 20242 yr by Cpt_Piett

46 minutes ago, Eef said:

Hello all, i'm following this thread with great interest. I have a 7800X3D & 4080. Using my 75 inch QLED TV for the SIM. 120Hz & using G-sync. What do you recommend to try regarding FG / V-Sync / DLSS / G-Sync / RTSS. I'm using the DynamicLod / AutoLOD tool and flying mostly on EHAM with the Fenix / PMDG and AIG. I already tried some combinations but then its flickering, then its stuttering. Not found the best one yet so I'm curious about your opinion 🙂 Can you guys share me your thoughts / suggestions? Thank you.

I get excellent results with FG on, V-Sync ON in NCP (but off in sim), G-Sync window and full-screen mode in NCP, RTSS locked at 60 FPS using front edge sync. 

I think that's a good starting point. From there you can experiment using different aircraft and flying into different airports to check if you can maintain a stable 60 FPS. If so, it's possible like @RJC68 mentions, to crank up the visual settings including render scale (or DLDSR). 

I like to tweak my settings to fit almost any situation - the excellent AutoFPS app makes this so much easier. With my 12900KF I can achieve a TLOD min of 100 at most airports. 

Quote

I already tried some combinations but then its flickering, then its stuttering.

Make sure that the monitor is really synced to the GPU when using G-Sync. I do it by bringing up an on-screen overlay on my monitor. If syncing doesn't happen, you'll see tearing. 

In order to minimize stuttering, I use the freeware app CapFrameX to measure the difference in frame times (frame time variance), which is a much better measure of stuttering than FPS. 

In the example below, you can see that I was able to maintain a constant 60 FPS virtually all the time during this 7.5 minute recording. Also, the frame times (the time that passes between each frames) were extremely consistent with an almost negligible frame time variation: 99-93% of the frame times were within 2ms of each other. 

IMO the biggest cause of high frame time variation is high main thread times (frame time influenced by CPU). This usually happens with too high TLOD, lots of AI traffic, complex aircraft etc etc. Hence, even with frame generation on, the CPU still has to be able to keep up with the GPU in order to reduce stuttering. 

If you have any questions re: settings or using CapFrameX, you're guaranteed to get an answer (or several) in this thread. In fact, I think it would be justified to rename this thread "The MSFS performance mega-thread" 😄  

Edited February 27, 20242 yr by Cpt_Piett

As you must know DynLOD also increases/reduces LODs with altitude changes as well.

35 minutes ago, Cpt_Piett said:

You can e.g. set TLOD minimum 20 at tough airports and while descending on approach, the app will gradually reduce TLOD until it reaches the min value at 1000 AGL

Dynamic LOD does this as well, change LODs as you climb and descend.

1 minute ago, Noel said:

As you must know DynLOD also increases/reduces LODs with altitude changes as well.

Dynamic LOD does this as well, change LODs as you climb and descend.

I know, I used that one before changing to AutoLOD. I just think that I get the same results with the AutoFPS without having to manually define altitudes. Both are great apps! If I get time later today I'll do some test-runs with the new version of DynLOD. 

Thank you very much! I'm going to try your suggestion :). What Nvidia driver version are you guys using? 

1 minute ago, Eef said:

Thank you very much! I'm going to try your suggestion :). What Nvidia driver version are you guys using? 

I'm still on 552.52, didn't see any benefits in upgrading. 

1 hour ago, Cpt_Piett said:

In fact, I think it would be justified to rename this thread "The MSFS performance mega-thread" 😄  

Indeed! Between this, the DLDSR and AutoFPS threads, I've found a ton of things that I want to try to address what feels to me to be suboptimal performance on my 2x4k resolution.

And back to the title of this thread, in addition to poor performance I too was noticing lots of flickering in the FBW A320 so I'm hoping something I try will improve that. I did enable RTSS locking last night with front edge syncing, but didn't do enough testing, and didn't get back to the A320 yet, enough to draw any solid conclusions.

Also @RJC68 thanks for the clarification!

 

Edited February 27, 20242 yr by GregP

16 minutes ago, Cpt_Piett said:

I'm still on 552.52, didn't see any benefits in upgrading. 

Do you know something we don't LOL

I am running the latest driver 551.61, I actually found the last 2 drivers to offer much better performance, I was however running a much older version from last summer

1 hour ago, Cpt_Piett said:

IMO the biggest cause of high frame time variation is high main thread times (frame time influenced by CPU). This usually happens with too high TLOD, lots of AI traffic, complex aircraft etc etc. Hence, even with frame generation on, the CPU still has to be able to keep up with the GPU in order to reduce stuttering. 

The other thing I have been experimenting with is I have a batch file I created to run the various pieces of software I need for each flight, I currently have it configured so that when FSLTL runs the core affinity for this one program is shifted to the E-Cores on my i712700K as I know traffic can have a CPU hit.

echo Starting FSLTL with AffinityMask . . .
d:
cd \MSFS\Mods\Aircraft\fsltl-traffic-injector
start "FSLTL" /affinity F0000 "D:\MSFS\Mods\Aircraft\fsltl-traffic-injector\fsltl-trafficinjector.exe"
TIMEOUT 5

 

Edited February 27, 20242 yr by RJC68

5 hours ago, RJC68 said:

Do you know something we don't LOL

Haha unlikely 😅 The hotfix driver and the release one after that were great (less stuttering). The most recent one didn’t seem interesting to me (read release notes), especially since I started using DDU again…

5 hours ago, RJC68 said:

The other thing I have been experimenting with is I have a batch file I created to run the various pieces of software I need for each flight

Would you mind sharing it with us Richard? I guess it has to be edited.

45 minutes ago, Cpt_Piett said:

Would you mind sharing it with us Richard? I guess it has to be edited.

Yes Sir,

Will post the contents shortly

Edited February 27, 20242 yr by RJC68

1 minute ago, RJC68 said:

@Reset XPDR I had a little bit of time to run a few further tests,

Like me I think you’re jumping between many different threads my friend 😅

@Cpt_Piett Here you go

You would need to tweak the paths too match your own and use the following to figure out what numbers are your E-Cores

https://bitsum.com/tools/cpu-affinity-calculator/

@ECHO OFF
echo.
echo Starting Spad
start "Spad" "C:\Program Files\SPAD.neXt\spad.next.exe"
TIMEOUT 12

echo Starting FSLTL with AffinityMask . . .
d:
cd \MSFS\Mods\Aircraft\fsltl-traffic-injector
start "FSLTL" /affinity F0000 "D:\MSFS\Mods\Aircraft\fsltl-traffic-injector\fsltl-trafficinjector.exe"
TIMEOUT 5

echo Starting HWINFO
start "Hwinfo64" "E:\Backups\hwi_722\HWiNFO64.exe"
TIMEOUT 5

echo Starting Auto FPS
start "Auto Fps" "C:\Users\richa\AppData\Roaming\MSFS2020_AutoFPS\bin\MSFS2020_AutoFPS.exe"
TIMEOUT 5

echo Starting MSFS2020
start "Flight Simulator" "C:\Users\richa\Desktop\Microsoft Flight Simulator.lnk"
TIMEOUT 5

echo.

Edited February 27, 20242 yr by RJC68

1 minute ago, Cpt_Piett said:

Like me I think you’re jumping between many different threads my friend 😅

Oh Words not allowed !!!!!