2015-09-09, 21:35
Not sure if it's just logged twice or it actually retries a second time, but on #0908:
The DelayedMessage is "Pause during refresh rate change" and I can't see it being paused for double the time it's configured to - infact if I wasn't reading the log I couldn't see any difference.
Might also be normal with the refactor...
(Speaking of that - I'm wondering if there's really no way to detect automatically when the display has switched to the new resolution/refresh rate/3D mode/...?)
Code:
21:08:50 69350.546875 T:1472197632 NOTICE: Thread JobWorker start, auto delete: true
21:08:50 69350.562500 T:1966575616 NOTICE: Display resolution ADJUST : 1920x1080 (1920x1080) @ 25.00 - Full Screen (29) (weight: 0.000)
21:08:50 69350.671875 T:1451222016 NOTICE: Thread DelayedMessage start, auto delete: true
21:08:50 69350.992188 T:1966575616 NOTICE: Display resolution ADJUST : 1920x1080 (1920x1080) @ 25.00 - Full Screen (29) (weight: 0.000)The DelayedMessage is "Pause during refresh rate change" and I can't see it being paused for double the time it's configured to - infact if I wasn't reading the log I couldn't see any difference.
Might also be normal with the refactor...
(Speaking of that - I'm wondering if there's really no way to detect automatically when the display has switched to the new resolution/refresh rate/3D mode/...?)
