Comme=
nt # 82
on bug 11065=
9
from tempel.j=
ulian@gmail.com
(In reply to Andrew Eikum from comment #81)
> I've submitted a patch to Wine to throttle our c=
alls to XResetScreenSaver to
> once every five seconds: https://source.winehq.org/patches/data/169958
>=20
> However, I'd argue our previous behavior isn't obviously wrong. What w=
e were
> doing was calling XResetScreenSaver each time we received user input o=
n a
> joystick in order to delay the screensaver coming up despite no
> keyboard/mouse input. It's not obvious that this behavior was incorrec=
t. Are
> you sure you shouldn't be able to handle this behavior from a client?<=
/span >
Thank you. Subjectively, I'd say it completely solves the issue. I don't see
any noteworthy spikes in frametime graphs and I haven't noticed any suspici=
ous
stutter/blocking until now (will do some more tests to be sure).
I'd be very happy if this could be included in 4.17 to increase chances tha=
t it
gets picked up by one of the next Proton releases.
It'd be interesting to know at what calling rate the display driver starts =
to
have issues.