dxvk
for game developers
Why this scored 2
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 122
Measuring input latency on Linux: X11 vs Wayland, VRR, and DXVK
Input latency measured · for linux devs
lobstersSteady 2 · linuxhardware104d ago - 213
Measuring Input Latency on Linux: X11 vs. Wayland, VRR, and DXVK
Input latency study · for linux devs
hackernewsSteady 3 · linuxdevtools104d ago - 33
DLSS5-Autopilot — Puts DLSS 5 neural rendering into games that never shipped it. Scans your library, reads each executable, picks one of eig
Enables DLSS 5 neural frame generation in games lacking native support via runtime injection. · for game developers
githubSteadyai−16 saturated49d ago