G-Sync not working when DLSS on as anti-aliasing option

User Support Hub Hardware & Peripherals
,
1

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

no

Have you disabled/removed all your mods and addons?

yes

Brief description of the issue:

when using “NVIDIA DLSS” as anti-aliasing option, the G-Sync stop working even if I still see the G-Sync indicator from the Nvidia control panel. When I go back to using “TAA” as anti-aliasing option, g-sync works fine. The effect is easier to see when in cockpit view and using the left & right quickview

Provide Screenshot(s)/video(s) of the issue encountered:

this does not show in screenshot of video

Detailed steps to reproduce the issue encountered:

easy: activate DLSS and do left / right quickview from cockpit

PC specs and/or peripheral set up if relevant:

EVGA GeForce RTX 2080 SUPER XC GAMING, ASUS ROG PG348Q

Build Version # when you first started experiencing this issue:

SU10 (the last one, the one with the DLSS option)

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

2

Check the G-sync setting in the NVIDIA Control Panel. Enable g-sync for windowed and full screen mode.

AFAIK I have not had any issues with G-sync and DLSS(QUALITY).

If that doesn’t work then maybe NVIDIA or your monitor vendor should be contacted about this. G-sync is a combination of hardware and software in the GPU and the monitor. MSFS doesn’t or shouldn’t know if G-sync is being used or if it does, it shouldn’t be able to enable or disable it. Even Windows doesn’t have direct access to G-sync, only through the NVIDIA control panel. Windows DxDiag doesn’t show anything about G-sync.

1 Like
3

Hi, juste to be clear, the issue is only happening when I change the settings in MSFS from “TAA” to “DLSS”: I am not changing anything else and when using “TAA”, I get no screen tearing. I have been using G-Sync with success since the beginning of MSFS. And like I said, the “G-Sync” indicator still show on my monitor left top corner when using DLSS even if I see tearing when I move quickly right to left / left to right.

Also, I do have the latest Nvidia driver (517.48)

4

It says it support Microsoft Flight Simulator new NVIDIA DLSS 2 update, should have worked properly …

image
image1212Ă—554 60.4 KB

In any case :

5

I don’t see any tearing with DLSS or TAA. Are you seeing Motion Blur or tearing?

6

tearing have nothing to do with GSync or DLSS.

Enable V-Sync or limit your FPS.

1 Like
7

Hi, sorry if the term tearing is not the right one but I took it from image on the web - what I see when I enable DLSS on my rig fit the examples below
image

image
image781Ă—340 50.8 KB

8

Hi, what I see when using DLSS (but not when using TAA) is similar to this example that call it tearing:

image
image781Ă—340 50.8 KB

9

Yes, I guess it should but it does not for me :frowning:

10

Hi, to your point, even if I see tearing with DLSS, the G-SYNC indicator in the top right corner of my monitor is visible

11

Hi,

dont be confused whit G-Sync and V-Sync.

V-Sync avoid Tearing, which happen if your GPU delivers images faster than your monitor can it hanlde. Then these images “tear”. G-Sync is for a dynamic sync frequency below that range.

Thus, also with G-Sync you need somewhat what prevent Tearing and that is V-Sync or a Max.Fps limit 2-3 fps below your max monitor fps.

Why its happen if you enabled DLSS ? Well, DLLS is made for exact this reason. It renders internaly with a much lower resolution and kind of clever algorithm try to create from the low resolution an image which looks near same as your native resolution. That works mostly ok ( not foy my eyes ) and the beneffit: with DLSS you can get higher fps ( if you are not cpu limited etc. ). TAA is the traditional AntiAlising where your GPU renders the images in native resolution.

PS: put DLSS under AA setting is what many game-producers do and what confuse a lot of users too. Its nothing about AA.

1 Like
12

Yeah that’s tearing, but it doesn’t happen for me. G-sync seems fine with DLSS on my monitor.

1 Like
13

DLSS does do antialiasing; it just also does upscaling which is the exciting part. :smiley:

14

I not wrote that it does is not, but it is not in special an AA algorithm… it is made because nvidia knows, that they can not produce hardware which can handle 4k … 8k… etc. … so , for performance only.

And nope… DLSS is not as good as most users say, at least not for me. Check DL DLAA and you know what I mean.

1 Like
15

I’m well aware of its limitations, I have a whole thread in the beta section on it. :wink:

1 Like
16

For clarification, monitors have a refresh rate such as 60hz 120hz, etc. The GPU sends frames to the monitor measured at FPS. V-sync minimizes screen tearing by “synchronizing” frames to the monitor’s refresh rate. A monitor with a 60hz refresh rate updates the screen every 1/60th second no matter what the GPU is sending. The monitor is not synchronized to the GPU causing tearing. This is why V-sync is needed.

On the other hand, G-sync dynamically CHANGES the monitor’s refresh rate for each frame to the FPS up to the monitor’s refresh rate. The monitor “refreshes” the screen for each frame. Hardware is needed in a monitor to support G-sync which is why G-sync capable monitors are a little more expensive. (IMHO worth it!)

17

Hello all, I forgot to indicate that I am using DX11: if I switch to DX12(beta) then I get no tearing in DLSS (like I use to get when using TAA) :slight_smile:

For those with a G-Sync monitor that do not get the problem, are you using DX12(beta) and if yes, can you try with using DX11 ?

Thanks

18

I use it with both DX11 and DX12 with no issues.

19

I use DX11.

20

Ok, my bad - made more tests and I do have the problem with both DX11 & DX12 :frowning: