Fixed various NtSetTimerResolution problems

Open Kaldaien opened this issue 2 years ago • 1 comments

I have been noticing weird timer resolution behavior in Special K's user logs for months now. I finally tracked it down to Streamline's timer code.

It requires the following corrections:

Ensure Streamline never makes the system timer resolution WORSE than it already was
Use the maximum timer resolution available if 0.5 ms is unsupported
Handle NTSTATUS checks correctly

Oct 01 '23 20:10 Kaldaien

Thanks for sharing this!

Currently shepherding this through review/QA/etc. Missed the upcoming release cut-off, but will be in later one.

Feb 28 '24 20:02 jake-nv

@jake-nv Any news on this ?

May 31 '24 12:05 toinouH

It’s in the upcoming release. I can’t give a specific date, but it’s on its way.

May 31 '24 20:05 jake-nv

Fixed in v2.4.10 (c709dd9)

Jun 04 '24 23:06 jake-nv