Support
Email support@ivoladenius.com. One person reads it, usually within a couple of days. Telling me your Windows version and what you were doing when it went wrong saves a round trip.
Frequently asked
Do I need to know my DPI?
No, and that is deliberate. The measurement counts what your mouse actually reports, so a wrong DPI cannot spoil the result. Entering one only changes whether distances are also shown in centimetres. The method page explains why.
How long does the measurement take?
About fifteen minutes for the full set: an input check, a flick measurement and a tracking measurement. You do it once. There is a shorter session if you want a rougher answer faster — it finds the same peak with a wider confidence range, and says so.
Why does it want me to run an "input check" first?
Because mouse acceleration, or anything else that scales your input between the mouse and the app, makes every measurement meaningless. The check has you sweep a measured distance twice, once slowly and once fast. If the two disagree, something is altering the signal and the app tells you before you waste fifteen minutes.
My result is outside the range the research supports. Is it wrong?
Not necessarily. The app says when your optimum falls outside the researched band because that is a fact worth knowing, not a verdict. It means your result sits outside what was measured in the study, so there is less evidence behind it — not that you are aiming wrong.
Why does it refuse to give me a number sometimes?
Because your trials did not separate the sensitivities clearly enough to find a peak. The honest answer there is "this is the best level you actually tested", not a fitted optimum dressed up as one. Running a longer session usually resolves it.
The game I play is not in the list.
Thirteen ship. Adding one needs its yaw constant and slider range verified against the live game, not copied from a forum post — that is why the list is short and why several entries carry a warning. Mail me the game and I will look at what it would take.
Does it work with a controller?
Yes, and it measures things no public dataset covers: your stick's drift, your minimum usable deadzone, and a game's turn rate. Note that static flick drills are hidden in controller mode — a stick sets a turn rate rather than moving your view a distance, so it physically cannot flick, and those drills would be testing nothing.
Where are my scores stored, and can I delete them?
In one JSON file on your machine, and yes — Settings → Erase all my data, or delete the file. See privacy for the exact path.
Is there a Mac or Linux version?
Not yet. Windows first, because that is the platform where the raw-mouse-input guarantee this whole thing depends on is documented and verifiable.
Reporting something broken
Useful things to include: your Windows version, your mouse and its polling rate, which screen you were on, and whether the input check passed. If the app wrote a warning, quote it — the wording tells me which branch you hit.
Security
If you find a security issue, mail support@ivoladenius.com rather than posting it publicly, and give me a reasonable window to fix it. Shared drill codes are the part that accepts input from strangers, so that is the most interesting place to look.