speancer wrote: ↑05 May 2020, 05:12
Do all other motion blur reduction technologies impact brightness that much?
Not all of them. There's also bright ULMB implementations (i.e. only 25% loss in brightness, most 25" 240Hz panels can do ULMB with little brightness loss) but most 27" ULMB dims quite a lot. It's simply a matter of voltage-boosting the strobe backlight flashes to compensate for the briefness of the strobe backlight flash. DyAc uses a heavy amount of voltage-boosting to an extent that it successfully fully compensates for the brightness loss.
speancer wrote: ↑05 May 2020, 05:12
So, does DyAc do exactly the same thing like ULMB with no brightness penalty, or is it a better technology overall? From what I see, it's better, because it's presented as also being able to reduce ghosting.
DyAc and ULMB behave the same way. 120Hz for 120Hz, it will look relatively identical, except significantly brighter. That said, be noted you may get a bit more strobe crosstalk at 240Hz than at 120Hz, due to the way LCD GtG overlaps multiple refresh cycles. DyAc is one of the better full-240Hz-capable strobe backlight modes.
speancer wrote: ↑05 May 2020, 05:12
What I also seek is how to reduce ghosting; right me if I'm wrong - it's how that trailing behind moving objects is called, correct? When you move the camera with your mouse and look at an opponent's model (or any other object), it leaves a phantom-like trail behind. From what Zowie is advertising, DyAc also fights off ghosting. They present it here, please have a look
Yep, that's ghosting/coronas.
We've got images of ghosting at
LCD Motion Artifacts 101
You will still have something similar called strobe crosstalk (The faint afterimage you see in ULMB, like at
Strobe Crosstalk FAQ). In the best case, it's much fainter than the ghosting/coronas in non-strobed mode (non-DyAc non-ULMB). In the worst case, it is worse than the ghosting/coronas in non-strobed mode.
For BenQ (XL2540 and XL2546), it definitely is less than non-strobed. If you want brighter, definitely XL2546 over XL2540 as the DyAc-branded mode is brighter than the XL2540 version (about the same brightness as the ULMB you are seeing).
speancer wrote: ↑05 May 2020, 05:12
About flicker-free being disabled, does it hurt eyes or something? I guess there's a reason why basically all monitors are flicker-free?
Everybody sees differently. That said, some of us here have motion blur eyestrain so the motion blur reduction compensates fully (lesser evil to enable a perfect synchronized flicker that is tuned to intentionally eliminate motion blur). There are people here who get headaches from PWM dimming but not headaches from motion blur reduction. Everybody is different -- some see stutters more, some see tearing more, some see flicker more, some see motion blur more, etc. You may be picky about different things.
I've always used 400 DPI for Counter-Strike, for years, I did not notice any stuttering with ULMB enabled in CS:GO.
speancer wrote: ↑05 May 2020, 05:12
And back to DyAc, I've seen a thing or two about something called strobe crosstalk around here. Is that negative effect only visible if FPS drops to at least 1/2 of refresh rate?
No, you will always get duplicate images on impulsed displays for frame rates far below Hz, on all impulsed displays (CRT/plasma/phosphor/strobing/ULMB/DyAc/ELMB/whatever that uses flicker technologies to eliminate motion blur).
Strobe crosstalk (fps=Hz) and multi-strobed images (fps below Hz) have different causes despite looking similar. And they can both happen simultaneously (3 images -- 2 multi-strobed images combined with 1 additional faint image caused by strobe crosstalk).
Duplicate images is caused by flashing the same frame multiple times. It is fixable by increasing frame rate, or decreasing refresh rate to match frame rate.
Strobe crosstalk is caused by LCD GtG being too slow to fit in one strobe flash (pixel response overlapping multiple refresh cycles). It is a law-of-physics issue.
One or the other can happen, or both can happen at the same time.
Not everybody is picky about it.
speancer wrote: ↑05 May 2020, 05:12
What happens if FPS fluctuates below and above the refresh rate with DyAc enabled? Let's say I have that 240 Hz display with uncapped FPS, it goes from 200 to over 400 FPS from time to time, will that result in any problems with DyAc? Or, for example, if I cap frame rate at the refresh rate value (like you advice for best motion quality), will drops below 240 FPS result in any negative effects with DyAc enabled?
Please do more homework with ULMB. Play more with ULMB. The behaviors of ULMB is exactly the same as the behaviors of DyAc, except DyAc is brighter and lower lag.
"Result in any problems with DyAc" has no simple answers -- no Yes or No answer -- I can only ask you to see for yourself. The moral of the story is that there are general recommendations such as fps=Hz for motion quality, or overkill framerates (fps>Hz) for lower-lag. For some people, all frame rates are all playable with strobing (ULMB or DyAc). Everybody is picky in different ways. Some people dislike strobing only because of lag. Others dislike strobing only because it looks too jittery with their favourite low-DPI that they normally use non-strobed.
For other people who hate stutters, only fps=Hz looks beautiful. Basically ultra-high-DPI mouse + fps=Hz matching = the only way to get things TestUFO-smooth in videogames.
Also, don't forget to see
HOWTO: Using ULMB Beautifully or Competitively.
Now, mind you, ULMB doesn't benefit CS:GO nearly as much as crosshairsless games as seen in the FAQ above, due to the fixed-gaze situation (motion blur reduction only helps eye-tracking situations, not fixed-gaze situation). But XL2546 DyAc makes it low-lag enough and bright enough, that some pros now keep it turned on. Also, it can help with aim control during spraying an enemy in a game -- the recoil and the vibrations -- all that can create display motion blur that makes it hard to continually aim a spray. The motion blur reduction can help with that too.
You already have ULMB. Test it out some more in solo/bot play. Sure, the lower-Hz 165Hz ULMB is more laggy and dimmer than DyAc. Test raising mouse DPI from 400dpi to 1600dpi or 3200dpi (And lowering in-game sensitivity), combined with cleaner mouse feet and higher-resolution mousepad (needed or 1600dpi feels worse than 400dpi). You need one of those new high end sensors that does high-DPI accurately. Now test a few slow mouseturns, and you'll see mouseturns become TestUFO-smooth/sharp. Slow mouseturns as smooth as keyboard strafe left/right, without coarse/granular effects (the step-step-step effect).
Get familiar with your ULMB. Stutter mechanics are identical to DyAc. Pretend that there's no lag penalty. Pretend it's much brighter. If it grows on you ("if only if it were brighter and less laggy"), then definitely pay the premium for DyAc.
There are some ULMB implementations as bright as DyAc but BenQ has been more consistent and careful slapping the "DyAc" label only on their brightest strobed implementations, so the "DyAc" label is consistently universally bright, whereas "ULMB" can be anywhere from very dim to very bright (Depending on monitor model).