HTML/JS gauges have more 'fade-in' of changes than 2020

[MSFS 2024] Bug Reports Aircraft
1

Version: 1.2.8.0

Frequency: Consistently

Severity: Low

Marketplace package name: n/a

Context: - testing with the LS4 freeware glider. html/js writeable textures in MSFS2024 seem to have much more fade-in of display changes than MSFS2020, i.e. if a texture is displaying a ‘4’ and html/js code changes that to ‘3’, the previous value persists for half a second as the new value takes effect.

Similar MSFS 2020 issue: this effect wasn’t noticeable in MSFS2020, but it’s unpleasant in MSFS2024.

Bug description:

As attached pic, if a gauge is updated once per second, the updated value ‘fades-into’ the display instead of replacing the previous content.

Repro steps:

HTML/JS gauge, create a text area, once-per-second update that html element with an incremented integer.

Attachments:

See the “21.3” and “2040” overwriting the previous “21.4” and “2090”

image

2

Anti-aliasing and frame generation settings (& possibly others) are affecting this.

Nowadays there’s a lot of post-processing happening across multiple rendered frames, ruining a lot of things like this.

3

I noticed this on my installation as well (Nvidia GeForce RTX 3070 Laptop GPU - 8 GB RAM)
If I use the recommended “Quality” setting from Nvidia for MSFS 2024, the fade in/out is basically unacceptable. As a test I went with Nvidia’s “Performance” setting and the fade in/out disappeared entirely.

4

Seen this as well with things that blink, they fade in and out instead of on and off. Why I still don’t use DLSS.

5

Hello @B21

I agree this seems related to temporal anti aliasing.
Can you turn off anti aliasing and confirm this no longer happens?

Regards,
Sylvain