- #Xonotic tf2 hitsound driver#
- #Xonotic tf2 hitsound full#
- #Xonotic tf2 hitsound pro#
- #Xonotic tf2 hitsound software#
- #Xonotic tf2 hitsound windows 7#
However I did perform 50 tests for zowie and 30 tests for g100s mouse1 click latency because that was the most I was interested at. Currently I do not have neither time nor will to make it THAT accurate for each measurement. However for more or less accurate number we need 50 measurements at least to randomize input time. So it will be enough to perform only few measurements (~10) to get good idea what amount of frames it takes to react to mouse click or motion start. Frame length is ~7ms for XL2411T, so depending on input timing we will always get 7ms variance of input lag overall if enough measurements are done. So measurment done by frame counting between events has ☑ms (☑ camera frame).Īfter I have done over 150 measurements overall for mouse1 input lag, I can safely say that 10 measurements is enough to determine this value. So I performed various expiriments to check stability of framerate of the camera.
#Xonotic tf2 hitsound pro#
Win 7 Pro 64bit (with latest updates), Media Player Classic Home Cinema (MPC-HC), Quake Live 0.1.0.879Ĭount frames between LED fire and first signs of rail trail appear at the bottom region of monitor Use Media Player Classic Home Cinema (MPC-HC) from to view frame by frame. Instant mode OFF = +7ms lag to the color state, but grey reponse is still ~28ms QL Turning off scaling completely in nvidia control panel resulted in ~3ms more input lag, but it might be due to the low amount of measurements. Take a note that those are only available with 120Hz, so it might be partially due to the lower refresh rate. BenQ built in featrues Aspect, 17" and 19" are all adding 5-8ms. Lightboost tends to add couple ms, but since this is within measurement tolerance and I actually need to perform 50+ events checking I got lazy about doing more measurements.
#Xonotic tf2 hitsound windows 7#
HPET OFF = stutters + drops in frame rate + it adds HUGE input lag variace - I made 10 measurements and it was anything from 26ms to 90ms (!!!) turning HPET on/off with cmd in WIndows 7 did not make any difference QL/CSGOģ. Turning HPET ON/OFF with command line in Windows 7, while HPET is ON in BIOS. Java, Flash, IE, Print Spooler, Human Interface Device Access (:D:D:D).
#Xonotic tf2 hitsound driver#
xHCI pre-boot driver / xHCI mode / xHCI hand-off. Turbo Boost/C-States/EIST/Thermal Monitor/Etc. Maximum prerendered frames setting in nvidia control panel both for QL/CSGOĢ. Things, that do not affect input lag (or their impact is less than 2-3ms). At 170Hz input lag tended to be couple ms less. Same setup as execept I use 144Hz LCD instead of CRT.ĬRT result At 144Hz I could not find measurable difference in input lag. Start motion lag test results - 15ms for both Zowie EC2 CL (4 CPI) and Logitech G100s (measured for default 1000CPI and 400DPI, non-native DPIs are not adding measurable delay) both of them had lowest value of 10ms and highest of 17ms Sample VIDEO:ĬSGO Logitech G100s Average overall input lag 22ms. QL Logitech G100s Average overall input lag 14ms. QL ZOWIE EC2 CL Average overall input lag 28ms.
#Xonotic tf2 hitsound software#
GPU everything in nvidia driver software set to highest performance and lowest quality LCD 144Hz, 1080p, instand mode on, ama premium, brightness 100%, image mode standard Using following formula DPI = 360*2,54 / (cm360*m_yaw*QLsensitivity) ( source )Ĭamera: Casio EX-FH25 all filming is done at 1000FPS.ĬSGO max_fps=250 everything else at default Mouse: Zowie EC2 CL and Logitech G100s modded with LED, which is driven by Mouse 1 switch of the mouse directlyĪctual DPI values zowie 421dpi, g100s 937dpi PC: i5 4690, GTX760 Hawk, Z87M Gaming mb, RAM CMZ8GX3M2A1600C8R 2x8Gb, Kingston HyperX 3K SSD. Measure start motion lag for QL/CSGO from mouse movement start to first reaction on screen appear.
#Xonotic tf2 hitsound full#
Measure full input lag for QL/CSGO from click to client side effect appearing on the screen for different hardware setups and software settings. Results are relative to G300, mice with negative results are faster than it.
NEW UT ALPHA (19-08-14 build) Logitech G100s 15msįor mice button latency comparison see this picture from this blog. Tesoro Durandal Ultimate (Cherry Red) 16ms (12ms.19ms) Razer Blackwidow Tournament (Razer Green) 21ms (17.24ms) TLDR Average overall input lag from click to screenĬorsair Vengeance K65 (Cherry Red) 14ms (9ms.16ms) This post is being updated with new info when available.
0 kommentar(er)
