Posts by Blur Busters
Visit the new TestUFO LCD Museum today!
The new LCD Simulator. Adjust GtG and overdrive, completely in your web browser.
You can simulate a fast 2025 IPS LCD...
...or a very old 1989 monochrome laptop LCD.
There's pros/cons tradeoffs that depending on
- Sync technology (VSYNC ON, VSYNC OFF, VRR)
- DPI settings (e.g. low vs high DPI)
- Game optimization (e.g. RawInputBuffer)
- Your display Hz
Sometimes 2000 Hz is the 'sweet spot'
Don't just test mouse lag. Test mouse jitter too.
- 1000, 2000, 4000, 8000 Hz polling
- Test with 600 Hz, 720 Hz, 1080 Hz display
- Harmonics more visible if Display Hz *nearer* Mouse Hz
- Supersample mouse Hz by 2-4x+ if prioritizing visuals
- Left = 1000 Hz poll, Right = 8000 Hz poll
MacOS users -- Help Blur Busters!
Mac Mini, MacBook Air, Pro, Neo, etc
-> Please quickly test TestUFO Beta with SMOOTHER frame pacing on Macs using instructions on MacRumors Forums:
forums.macrumors.com/threads/120h...
I miss the projector, but not its weight!
139 pounds hanging like a Sword of Damocles above my sofa, in year 1999.
I did use six 400lb concrete anchors, so I had over a 10:1 safety margin. Two of us even swang a rope under the mount to stress test it first! 👽
True Multisync, up to 135 KHz scan rate. Yes I had 1080p in 1999!
Even self-ISF-calibrated. Convergence, astig, keystone, bow, the kit and caboodle. Took hours to get 720p pixel perfect, 1080p usable.
Practically I used 1440x810. I could run 800x600 at 100 Hz, so I loved that refresh rate.
Eventually I ran CRT 3D shutter glasses on an ASUS AGP V7700 Deluxe, a GeForce 2 GTS card running Star Wars Episode 1 Racer in full 3D glory (albiet at an eye searing 30Hz/30Hz per eye).
Pod racing 600 miles per hour, 4 feet above ground, on a 92 inch screen, 25 years ago.
My unit was NEC rather than Sony.
Here's Windows 98 running on it, all 92 inches of 16:9 widescreen. Before year 2000. Yes it was CRT.
Projected from three 8" CRTs from inside my NEC XG135 CRT graphics projector (>12K MSRP, got used at 5.7K as B-Stock from AVSCIENCE)
Blown up to 92". HD. Zero blur.
When I was barely out of my teenage years -- I used to have a three-CRT projector. Some of these Sony big-box rear projection had three tiny 7 inch CRTs blowing up to 61 inches. But some were DLPs.
Me way back in year 1999:
Not necessarily. Windows updates can add TD, if it's in a collab with a display driver - Windows updates do update display drivers too and sometimes certain features/responsibilities transfers between Microsoft & GPU vendors over long term. It may have happened before. I would need to look into it.
Temporal dithering is GPU vendor not Microsoft; Also see monitor-side FRC (blue-noise/error-diffusion) and/or unbalanced inversion artifacts (chessboard patterns), not controllable computer-side.
- Temporal dither PC side
- FRC monitor side
- Inversion algorithm (on TN can be worse than FRC/dither)
Upcoming Windows 11 Supports 5000 Hz Display Refresh Rate.
You're welcome.
blurbusters.com/new-version-...
TL;DR: Lots of display progress still coming. We currently predict 2000 Hz consumer displays arriving by 2030, and 4000 Hz consumer displays arriving by 2035.
Blur Busters Area 51 Portal, where I'm also cited in 50+ research papers: blurbusters.com/area51
Strobing is a fantastic solution for lower frame rates (Hello DyAc and BFI and GSYNC Pulsar and XG2431) but not everyone can handle it, too many of us get eyestrain.
Obviously, our work is cut in front of us, to fix 100 layers of the "weak links onion" of many system and hardware stutters/blurs. It's why 500Hz OLEDs currently outperform 1000 Hz LCD.
Blur Busters Law dictates:
- Motion blur = pulsetime for strobing
- Motion blur = frametime for sample & hold
So techless nailed the ballpark retina Hz for a strobeless sample-and-hold display. A display where you want to simultaneously eliminate both motion blur AND stroboscopics AND flicker.
That's for eye tracked gazes. For fixed gaze, that's stroboscopic effects (phantom array) at that pixel step.
If you go above 8K, move to a 16K 180-degree VR display with even faster motionspeeds, and you start getting numbers much closer to 40,000 fps=Hz like the techless video.
If you add GPU motion blur to fix stroboscopics:
- 2000 Hz, 8000pps = 8 pixel motion blur
- 4000 Hz, 8000pps = 4 pixel motion blur
- 8000 Hz, 8000pps = 2 pixel motion blur
- 16000 Hz, 8000pps = 1 pixel motion blur
For perfect framerate=Hz panning on 8K at 8000 pixels/sec, at perfect 0ms GtG and no jitter:
- 2000 Hz, 8000pps = 4 pixel motion blur
- 4000 Hz, 8000pps = 2 pixel motion blur
- 8000 Hz, 8000pps = 1 pixel motion blur
Let's imagine a giant 2000Hz 8K TV on your desktop.
Retina resolution, sample and hold, no blur reduction, and big. You have a 90-degree FOV of that TV on your desk.
Motion blur puts pixels below retina resolution. Panning motion at 8000 pixels per second, one screen width/sec. Easy to eye-track.
This is assuming you zero out all 1000+ hardware & software weak links. Tiny list of examples: no jitter, no stutter, no GtG. GtG makes 500Hz OLED have clearer motion than 1000Hz LCD: You don't want 1ms GtG before/after your 1ms frametimes.
Now, let's go extreme, for the 5-digit number.
Approximate orders of magnitude, fps=Hz:
- 10 = slideshows turns into motion;
- 100 = flicker fusion (Talbot Plateau)
- 1000 = (at GtG=0.0) no motion blur for tiny 1080p screens
- 10000 = both motion blur & stroboscopics cease to be visible for wide-FOV retina resolution screens.
Techless video where human eyes can detect display imperfections up to nearly 40,000fps 40,000 Hz due to stroboscopic effect:
Retina refresh rate is extremely high! 5-digit Hz.
Kudos to techless for fantastic video (39,620 Hz, though estimated ~20,000 Hz a few years ago).
There are 4 main visibility thresholds. Expand this post to dive into rabbit hole for a moment 🕳️🐇ִֶָ
Me too! Linux needs some OS shader hooks.
May Wayland add a refresh cycle shader hook?
See blurbusters.com/open-source-...
I already have an LCD simulator and plasma TV simulator shader coming too.
Asus V7700 Deluxe with the CRT 3D glasses
Thanks for having me on the program Bob!
Blur Busters Victory -- NVIDIA Listened to Community
G-SYNC Pulsar firmware upgrade coming to support optionally extended Pulsar range as wide as 48-360 Hz
blurbusters.com/nvidia-liste...
Yes, for a single GPU, the strategic use of a framerate cap, and configuring the ShaderBeam CRT Hz to match. That can produce the best experience!