Installation
Ready to dive in? You can find the software built and ready to install, or the Github repo with all the open source code and designs.
Get the Software View the GitHub repo
Open Source Latency Testing Tool - OSLTT
In short, OSLTT is my attempt at an open source latency testing tool - similar to NVIDIA’s LDAT. At launch, the tool is able to do the same custom DirectX test as OSRTT, mouse and keyboard latency testing, in game end to end latency testing, and audio latency testing. It is still in its early stages, so please be patient with me. I’m working on it as hard as my failing mind and body allows!
This guide is also a very early iteration. The video guide is much more complete, but I’ll aim to add more here too.
Main Features
- Total system / click to photon / end to end latency measurement
- On Display Latency
- In game latency
- Mouse click / keboard keypress latency
- Audio latency
- USB C connectivity
- TRS Microphone jack AND INCLUDED MICROPHONE
- 2 pin input for remote triggering
- Built in status LED
- Auto-updater for both the program and board firmware
Main Goals
- Transparency - raw data saved so you can verify the results manually
- Accuracy - the raw sensor data is accurate to 15us (0.015s) and the processing code has months worth of checks
- Easy to use - I’ve tried to account for many issues and edge cases so for a typical display it should be plug and play. Includes USB supply stability checking, brightness calibration & processing.
I FOUND A BUG!! WHAT NOW?
I was expecting this… SUBMIT A BUG REPORT ON GITHUB
Here’s what I’ll need to help:
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. Windows 10]
- Version [e.g. 22]
**Additional context**
Add any other context about the problem here.
Alternatively, if you have a feature request you can do that on Github too! This is what I’ll need to know:
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Alternatively, ping me an email.