If your Smode GPU frame rate does not drop, your display device may experience issues if it does not support the pixel clock correctly in its EDIDs.
To detect this, use the Glitch layer and reduce its default 100% opacity to avoid hardware damage.
If the glitch frequency is visually stable, your display screen accepts your pixel clock.
If the glitch is not visually stable, it might be a 'ghost frame drop' (aka frame drop not detected by Smode), introduced by your display device's output chain.
This behavior may be due to a display device attempting to reclock the frequency or interpolate it to its native one.
It could also result from signal converters or incorrect EDIDs set in the video matrix.
Otherwise, try using different EDIDs or consider changing your hardware.
Smode does not have frame drop, display device correctly support glitch, but it is not enough on multi GPU
First of all, check the
Requirements topic.
Due to Windows Desktop Compositing (WDM), the entire desktop is refreshed (presented) simultaneously.
In the case of multiple GPUs, the driver must ensure that all applications on all displays present in a synchronized manner.
Using the same and strictly equal EDID pixel clock on different displays connected to different GPUs is subject to a small clock drift between GPUs.
This can introduce sporadic ghost frame drop issues.
Note that using custom EDIDs with small differences helps to reproduce this issue in a more deterministic way.
Mixing 50.00Hz and 50.01Hz EDIDs will allow this issue to be reproduced every 10 seconds.
The more the EDID frequencies are equal, the longer the delay to reproduce the issue, and its duration will grow.
