2.11 released

- LSFG 2.3 introduces X4 frame generation mode, generating three intermediate frames. The recommended usage scenario starts with the game's base framerate of 60 frames and for monitors with a high refresh rate of 240 and above, but can also be used with lower framerates (where the base mode is expected to give better results compared to "performance").
- X3 mode has been updated to further reduce artifacts on patterned textures and in dark scenes.
- Increased UI detection rate from every 4th frame to 1 for "performance" mode, as it was found that this could cause some artifacts. This led to a slight decrease in performance, so this parameter can now be changed in the config.ini file located in the installation folder.

- Initial support for G-Sync. It is recommended to enable it for full screen mode in the driver settings.

(....)

um WHAT?!

 

This is crazy....165 FPS with the PMDG 777 at Aerosoft Oslo with 50% AIG traffic. 150 FPS at iniBuilds EGLL, (165 with no traffic). 110 FPS at DD KEWR (with addon KLGA & KJFK active as well), 165 with no traffic. Minimal stuttering, minimal artifacting...truly unreal. Monitor refresh rate is 165, DX12, FG on, RTSS limited to 55 FPS using the Nvidia Reflex option (not front edge sync).

Effectively generating 165 FPS from 27.5 FPS. That's 27.5 FPS x 2 from native FG (55), then 3x in the LSFG (165). 4x is cool, but there is some noticeable artifacting. 3x has been improved massively.

For those wondering:
HDR: yes
G-Sync: yes
Night artifacts: none
Performance mode: no
Max Frame Latency: 2
Input Lag: Negligible
 

This is absolutely incredible.

1 hour ago, V1ROTA7E said:

Input Lag: Negligible

And that's with 2x3= 6x FG?😵

Sounds like IslandSimPilot got a new mic ! He goes through the steps for best results.

 

at 8:14. In NCP, make a new program for: Lossless Scaling.    (NCP | Add shows duck image). You already had one program for msfs). Now you have 2. You have Global, MSFS, and Lossless Scaling in NVP. And change the Vulcan setting in LS, and Apply.

 

Edited August 13, 20241 yr by Fielder

@V1ROTA7E,

Dude, you have a 4090, of course youre gonna get insane performance....For me, I have a 4070, i9-10850k, at the airports where I get base FPS of like 25-30 even with frame gen and I use LLS, it seems to still have some lag, the only time it seems to run smooth is when base FPS is at least 50-60.

Edited August 14, 20241 yr by Ray Proudfoot
Long quoted post removed.

I have monitor refresh rate set to 120 now. Global max fps in NCP I set to 120.

I set max fps in program settings area of  msfs of NCP to 40 (1/3 of 120). Because normally I can do 40 anywhere is MSFS. If my monitor could only do 60 Hz max refresh rate, then I would chose 30 (1/2 of 60).

With LSFG, I can double, triple, or quadruple that easy to achieve in MSFS fps of 40. Which is 80, 120, 160.

 

I haven’t tried the new version yet, but g-sync support is good news. That’s the main reason I gave up on it. I keep thinking about another thing though: how much better is 120fps compared to say 60fps? Genuine question, as I’ve locked fps to around 60 for quite a while now.

Another thing is whether high fps is smooth. One aspect of performance is how fast the sim runs ie fps. Another one is how smooth the sim runs. Based on my experience with lossless so far - when base fps falls below 30, there’s an increased chance of stutters due to poor frame time consistency.

Anyway, I’ll try this new version and run some tests in various scenarios with CapFrameX.

Edited August 13, 20241 yr by Cpt_Piett

The key is to limit what you feed into LSFG, it must be conservative!

And I flew just now in dense scenery area with heavy clouds and traffic. I fed 40 fps into LSFS (limiting it to 40 in NCP program settings: flightsimulator. You have to feed in a conservative fps that you can get for sure normally without scaling or FG in MSFS. In my case 40. If you don't set a limit, artifacts will happen.

With LSFG, it is smooth as glass under heavy scenery / clouds / traffic using a modest 2X scaling to get a stable 80 fps

There are other modest scenery areas, traffic off, and no weather where I could tripple or quad X scale.

 

 

Edited August 13, 20241 yr by Fielder

18 minutes ago, Fielder said:

You have to feed in a conservative fps that you can get for sure normally without scaling or FG in MSFS.

Good point. My base fps without native FG will probably be 30 or below in dense scenery with AI traffic. I’m talking about worst case situations eg KLAX, KJFK, OMDB etc. Not sure if lossless will save the day here…

We also have to keep this in mind:

Quote

The recommended usage scenario starts with the game's base framerate of 60 frames and for monitors with a high refresh rate of 240 and above, but can also be used with lower framerates

 

Edited August 13, 20241 yr by Cpt_Piett

I can't use LSFG if I have traffic slider in MSFS options set to 100

The number one hit on fps in MSFS for me is that traffic slider!

1 minute ago, Fielder said:

The number one hit on fps in MSFS for me is that traffic slider!

Agree! 1. AI traffic 2. TLOD. 

I'll do some testing with AIG at 50%. 

Whenever i i scale with latest lossless msfs freezes 

Is that due to latest nvidia driver?

Thanks

Mike

Heathrow, Fenix at gate 594, cockpit view, noon, clear skies. 4K, DX12, FG, DLSS+DLAA, TLOD 50.

First some tests without lossless:

• No AI traffic: FPS max 110
• AIG 50% traffic (119 aircraft nearby): FPS max 80
• AIG 100% traffic (294 aircraft nearby): FPS max 59

I have a high-end system, so lossless is not needed except for the 3rd scenario with 100% traffic. If I lock FPS with RTSS that gives the best frame time consistency. FPS varied a lot but stayed above 50, so I locked there. 

Without lossless, 1 min CapFrameX session: 

It turned out that I can't run a CapFrameX session with lossless active. Hence no frame time consistency comparison. Instead, I panned around in cockpit view with and without lossless at x2 ie 100 FPS. I should really have recorded a video to compare, as describing smoothness with words is tricky. 

Panning around cockpit without lossless: quite a few stutters and pauses

With lossless: basically the same ie stutters and pauses

Another thing is that G-Sync is not active with lossless. Refresh rate without lossless changes with fps and with lossless it is fixed at native refresh rate of 120. Could be because my display is only G-Sync compatible. 

TL;DR: 

In very demanding scenarios, lossless does not give an advantage in terms of smoothness. In less demanding scenarios, I'm not sure if I need lossless as I can get a smooth 60+ FPS. My intention with this post is not to rain on everyone's parade. I do think lossless scaling can be useful - except for those tricky situations where the sim is severly mainthread limited.  

1 hour ago, Cpt_Piett said:

In very demanding scenarios, lossless does not give an advantage in terms of smoothness. In less demanding scenarios, I'm not sure if I need lossless as I can get a smooth 60+ FPS. My intention with this post is not to rain on everyone's parade. I do think lossless scaling can be useful - except for those tricky situations where the sim is severly mainthread limited.  

We have nearly the same system, so I'm not sure why your numbers are so much lower. I'm also using AutoFPS & it's at 100+50 with a framerate target of 54. Like I said before, I'm using FG and locking the max framerate to 55 in RTSS using NVIDIA Reflex as the limiter mode. My panel is also G-Sync Compatible (AW34DWF), and there is no screen tearing. The stuttering is near nonexistent due to the frame rate limit. In the RTSS Frametime graph OSD, the frametimes appear to be quite erratic, but actual panning is extremely smooth with no hitching or stuttering. I'd recommend locking your RTSS frames at 40 (20 native, x2 with native frame gen) then using LSFG at 3x to give you 120 FPS rendered. Locking at the low target should help keep your CPU load under control with traffic and heavy scenery.

In your same exact scenario conditions (time set at 1200UTC & Live weather active) these are the results. This was set up different ways to reach a target of 120 FPS.

No traffic, Native FG, No LSFG: 90 FPS

No traffic, Native FG, LSFG @ 3x: 69/206 - minor, but noticeable input lag. (exceeds monitor refresh rate)

No traffic, Native FG, RTSS Locked at 40, LSFG Active @ 3x: 40/120 - minor artifacting, minor hitching.

No traffic, Native FG, RTSS Locked at 60, LSFG Active @ 2x: 30/120 - clearest image, minor hitching while panning quickly.

No traffic, Native FG, RTSS Locked at 30, LSFG Active @ 4x: 30/120 - actually not that bad, however noticeable artifacts, noticeable input lag, smoothest overall (no hitching).

No traffic, Native FG *disabled*, RTSS Locked at 30, LSFG Active @ 4x: 30/120 - nearly the same as above, just a bit "snappier" with less input lag. Enabling Front Edge Sync improved image clarity and did not add any noticeable input lag.

------------

AIG traffic at 50%, Native FG, No LSFG: 60 FPS

AIG traffic at 50%, Native FG, LSFG @ 3x: 60/178 - minor, but noticeable input lag, minor hitching, minor artifacts near screen edge. (exceeds monitor refresh rate)

AIG traffic at 50%, Native FG, RTSS Locked at 40, LSFG Active @ 3x: 40/120 - no artifacts, minor inputlag, no hitching (except while panning quickly)

AIG traffic at 50%, Native FG, RTSS Locked at 60, LSFG Active @ 2x: 59/117 - no artifacts, no input lag, no hitching (except while panning quickly)

AIG traffic at 50%, Native FG, RTSS Locked at 30, LSFG Active @ 4x: noticeable artifacts, noticible input lag, however smoothest while panning with hat switch.

AIG traffic at 50%, Native FG *disabled*, RTSS Locked at 30, LSFG Active @ 4x: 28/110 nearly the same as above

-------------

So for MY system, using the monitor's native refresh rate of 165, the best settings (in all scenarios) is:
 

FPS Locked in RTSS at 55
Native FG Enabled
LSFG at 3x

With or without AIG at 50%: 55/165 - No hitching, No artifacts, No input lag.

Edited August 14, 20241 yr by V1ROTA7E