Blur Busters Forums

Maybe im misunderstanding too but Eizo does not show more than 120 lighted fps, the 240 includes the time when the LED are off so basically any 120 hz lightboost monitor could be considered turbo 240. I think the major difference is that instead of a software hack like toasty to get the strobe effect its included in the monitor.

Hm, when I had a CRT, I would run 60FPS content in 120Hz mode (Doom 3 was capped at 60, and most emulators.) I don't remember any weirdness; it was smooth as butter with no artifacts whatsoever.

SS4 wrote:Maybe im misunderstanding too but Eizo does not show more than 120 lighted fps, the 240 includes the time when the LED are off so basically any 120 hz lightboost monitor could be considered turbo 240. I think the major difference is that instead of a software hack like toasty to get the strobe effect its included in the monitor.

Actually, EIZO uses 240 strobes per second to stay true to the Turbo240name and reduce flickering. However, it is 120 dominant strobes (about 2.5 milliseconds) with 120 minor strobes in between (less than 0.5 milliseconds). This is not ideal, as those are repeat strobes onthe same refresh, but it supposedly reduces flicker a bit, in tradeoff without producing too excessively strong a double image effect during fast motion. It is there, slightly, in motion tests.

RealNC wrote:Hm, when I had a CRT, I would run 60FPS content in 120Hz mode (Doom 3 was capped at 60, and most emulators.) I don't remember any weirdness; it was smooth as butter with no artifacts whatsoever.

There is a double edge artifact during LightBoost, but it can be subtle if you aren't looking for it. See www.testufo.com 60fps vs 120fps, while LightBoost is enabled.

RealNC wrote:Hm, when I had a CRT, I would run 60FPS content in 120Hz mode (Doom 3 was capped at 60, and most emulators.) I don't remember any weirdness; it was smooth as butter with no artifacts whatsoever.

Doom 3 actually uses 64 Hz engine timing and is capped at 64 fps which can cause severe timing problems at 60 Hz with vsync. For me it ran smoothly except for large skips forward in time once per second. Strangely it ran very smoothly capped at 64 fps with my monitor set to 75 Hz.

The "64 Hz bug" plagues the Gamebryo engine and is responsible for all the microstuttering problems in Bethesda games as well as Divinity 2 and others. Why John Carmack of all people would use this in his own engine completely escapes me.

Chief Blur Buster wrote:Actually, EIZO uses 240 strobes per second to stay true to the Turbo240name and reduce flickering. However, it is 120 dominant strobes (about 2.5 milliseconds) with 120 minor strobes in between (less than 0.5 milliseconds). This is not ideal, as those are repeat strobes onthe same refresh, but it supposedly reduces flicker a bit, in tradeoff without producing too excessively strong a double image effect during fast motion. It is there, slightly, in motion tests.

So that's why they are advertising it as 240 Hz. None of the advertising really hints at how it works, they just keep throwing the "240 Hz" label out there without explaining how it's different from existing blur reduction technologies.