[Desktop][Bug] Render errors since 7.1.0 update

[darkblood14]

Since update 7.1.0 it seems that the UI has some render glitches, especially when switching tabs, especially on screens that have charts in them but it is not limited to it.

Steps to reproduce the behavior:

1. Launch the app
2. Move the cursor around on screen and switch tabs (e.g. Fitness Trend since it has the moving tooltip)
3. Notice the black rendered areas or partially rendered UI elements.

Expected behavior UI elements are drawn correctly on screen with no duplicates or partial renders.

Video as it explains the problem much better: https://youtu.be/v8jrxTNmHqE

Environment

• OS: Edition Windows 11 Version 23H2 Installed on ‎28-‎Sep-‎22 OS build 22631.3593 Experience Windows Feature Experience Pack 1000.22700.1003.0 GPU: RTX 4070, latest drivers 555.85 (occurs on previous versions as well).

• Desktop app version 7.1.0

Notes:

• Tried reinstalling and resetting the app, even on a fresh install seems to act the same.
• Tried fully uninstalling Nvidia drivers (DDU) but no dice.
• Downgrading to 7.0.0 Beta 5 fixes the issue so it might be from the library update in 7.1.0.
• Since I see no issue here regarding this problem it might be that it is a specific combo on my machine so maybe it's not worth investing effort but might be a good idea to track it.

[thomaschampagne]

Strange behavior. Do you encounter the issue on another computer?

[darkblood14]

Hey, nope, on a laptop using a mobile nvidia card seems to work just fine but I think I might have found something. I didn't want to reply until I dug a little deeper and I remembered Microsoft Teams also having a similar issue in the past, for that one there is a setting within the app to disable Hardware Acceleration which fixes this problem (which might not even be from HW acceleration).

After a bit more google search I managed to get the desktop app to behave by turning g-sync on and keeping HW acceleration on (haven't tried anything more than rebooting the app so far so not sure if it is a real fix or it just somehow got the driver to reset which got it to not act like that, although just forcing a driver reset doesn't do the trick, G-Sync must be off it seems).

So for now I would say turning off G-Sync seems to be a workaround in case others have this issue.