![]() ~$5 for some single supply op amp and a switch/button. ~$5 for three types of resistors and one capacitor (which probably isn't necessary) I'm not going >$30 on things which I won't end up using for something else. I'm okay with buying more hardware as long as it's reasonable. Two crt monitors (sony cpd-g520p, sony gdm-fw900)Ģ lcd monitors (old ****ty viewsonic tn from ~2009, asus vg248qe with gsync mod)Ī laptop (thinkpad x220, 60hz ips screen)Ī ninox aurora (which will come. Windows 7, 8.1, xp (if you want), linux (need to update 239562 things tho) If you want be to test anything, let me know here.Īn arduino leonardo + various simple electronics for interfacing with photodiodesĪ gtx 970 (nvidia reference model from best buy) ![]() There is a bit of randomness in the spacing between each measurement so that the measurements aren't happening in sync with the framerate, which would likely give biased results that are consistently higher or lower than the average of a several independent measurements.ĭefault fps_max 100 adds between 0-10ms of input lag (expected behavior) over the lag with uncapped framerate of ~2000fps ![]() It takes ~10 measurements a second.Įach measurement is done by staring at a dark part in-game, twitching the cursor so that the screen goes to a bright part, waiting and measuring how long it takes for the photodiode to response, and twitching the cursor back. When I press the button, the program begins taking measurements. (anyone good with electronics and/or arduino, please let me know if there's anything to be improved/fixed) so a few days of messing with electronics led to this thing: At first, I was reluctant and doubted that it would allow more precision than the high speed cam, but soon I realized that due to CRT's low persistence and the phosphor's fast rise time, actually it would work very well. This made things a lot easier when scrolling through the video frames, but still it was quite tedious and I never made really more than 20 measurements from a single video clip.Ī few days ago, Sparky, in the blurbusters thread, suggested I use a photodetector on the arduino to replace the video camera and thus automate the measurements. With it, I can just press a button to make the "cursor" instantly twitch up to 127 pixels in any direction, and at the same time, an LED would light up. So I got an LED, a button, and an Arduino Leonardo board, which is capable of acting as a USB mouse, to automate the mouse slamming. But it was just tedious slamming the mice together and counting video frames. The results were quite promising and I could measure with precision and accuracy around 1-2ms, limited by the fact that i recorded at 1000fps, and that it is difficult to determine the exact frame where the mouse begins movement. As I did not want to buy another one and take it apart, attempt to solder, etc., I decided to forgo the button-click-to-gun-fire measurements, and instead simply measure motion lag by slamming my dead g100s onto my new g100s, and seeing how many video frames it took to see a response on my screen.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |