On 4/30/20 1:28 PM, Paul Gofman wrote:
On 4/30/20 21:21, Zebediah Figura wrote:
It may then be possible to implement time using USD but that would reduce the clocks accuracy down to the server update frequency.
If Windows has updates that slow, I think this makes sense. We'd probably want to use a different channel for +timestamp, though [QueryPerformanceCounter(), I guess?]
There's probably other consequences I'm not considering...
It might be potentially usable for GetTickCount() which has resolution around 10-15ms (though dangerous probably), but QueryPerformanceCounter() is designed as higher resolution timer, every game is using it and expects better resolution. 15-16ms is a long time. But proper Unix functions for getting high resolution time should already be quick, they also end up getting time from shared memory pages maintained by kernel.
Er, right, I wasn't saying that we should implement QueryPerformanceCounter() using the shared data, but rather we should use it to implement WINEDEBUG=+timestamp. Sorry if that came out ambiguous.