4 ms·

I've heard two conflicting explanations for this a) Both screens are receiving a 144Hz signal and your 60Hz screen just happens to accept this and drop the ext

I've heard two conflicting explanations for this a) Both screens are receiving a 144Hz signal and your 60Hz screen just happens to accept this and drop the extra frames b) It works as long as it can actually hit 144Hz. As soon as anything drops it will drop to 60 instead of whatever is appropriate for a 144Hz screen. (This comes from the article on how mutter finally split the frame clock on Wayland)

vbphprubyjsgo 5y ago
> a) Both screens are receiving a 144Hz signal and your 60Hz screen just happens to accept this and drop the extra frames No shot. All 60Hz monitors created before the 120Hz+ era cannot handle a signal above 75Hz. The exception being the few that can go up to 85Hz. They cannot just drop every second frame at 120Hz; that would require timing faster than what they're capable of.