Blur Busters Forums

Chief Blur Buster wrote: ↑

20 Feb 2019, 18:50

Assume you've already read
- Motion Blur Reduction FAQ
- Crosstalk FAQ
- Blur Busters Strobe Utility

If you messed up
- Run ToastyX "reset-all.exe" (removes all your Large Vertical Totals)
- Use monitor's "Factory Reset" feature.
And you can easily start over again.

Some quick pointers.

1. Strobe tuning an XL2546 doesn't benefit it nearly as much as the 144Hz BenQs like XL2411/XL2720/etc
Using Custom Resolution tricks doesn't benefit XL2546 nearly as much as the 144Hz BenQs like XL2411/XL2720/etc
You can use the 182Hz trick at http://www.blurbusters.com/crosstalk but here's an easier way.

2. If you're trying to fix strobe crosstalk, lower your Hertz!. 240Hz strobing at 240Hz will not be crosstalk-free.
This is the #1 numero uno easiest way to reduce strobe crosstalk, period

3. The lower your Hz, the less strobe crosstalk.
120Hz = nearly zero strobe crosstalk (easier for GPUs that can't reach 180fps)
144Hz = slight strobe crosstalk
180Hz = acceptable strobe crosstalk (common sweet spot)
240Hz = worse strobe crosstalk (but lowest lag)

4. Hertz headroom helps a lot, so don't feel bad about using lower Hz for blur reduction.
A 240Hz monitor will do 120Hz strobing better than a 144Hz monitor can do 120Hz strobing.
So you've got a superior monitor than any of the 144Hz BenQs for brightest & crosstalk-free motion blur reduction.

5. For simplicity of experimenting with an XL2546, simply create custom refresh rates without worrying about large vertical totals (for now). Figure out how the strobe crosstalk behaves. You can create multiple refresh rates for all the different preferred tradeoffs. Try testing 120Hz blur reduction or 144Hz blur reduction with some games that tends to run at lower frame rates, and see how they look.

6. Convert your refresh rate to large vertical total later (often little difference on the XL2546, this merely should be the last step) since XL2546 blur reduction behaves better with purely refresh rate experimentation only.

Remember, you want to optimize for frame rate = refresh rate = strobe rate so create your refresh rate for specific games based on your 0.1% worst frametimes, then optimize from there. (Unless input latency is important, then higher Hz the better, 240Hz DyAc is the lowest lag). If optimizing for least strobe crosstalk, lower Hz is typically better.