Open BinToss opened 2 years ago
ArecadianFox provided some FPS values via labelled chimera.bin configs https://docs.google.com/spreadsheets/d/1_bDBeSsxGjLbN4aA6p-mduVEnNB9qOMog_kpjCVRYCY/edit?usp=sharing
C# floats (Half, Single, Double, Decimal) are bit-masked slightly different than C/C++ floats (float
, double
).
See System.Runtime.InteropServices.NFloat
Something I recently learned is Chimera's FPS throttle is exactly that—a throttle. Sure, it limits the max FPS, but it does so by making the main thread sleep. While sleeping, no user input is registered and processed which leads to perceived input latency.
What we should do is uncap FPS and then use/encourage driver- or software-based¹ framerate limiting. In fact, V-Sync alternatives (e.g. Fast Sync, Adaptive Sync (maybe), FreeSync, G-Sync, et cetera) would be preferable.
¹ SpecialK offers a framerate limiter, but I can't promise it doesn't introduce significant input latency.
See https://github.com/SnowyMouse/chimera/issues/106#issuecomment-1868343405
nToss — 01/23/2021