Blur Busters Forums

SS4 wrote:Anyone else gets a nvidia kernel crash when strobelight is running for too long?
Sometimes im gaming without lightboost but with the strobelight exe running and game crashes because of nvidia kernell . . .

Never seen this issue.
Do you overclock something in your system?

I do.

I gsync'd my asus monitor and I'm liking that I can't adjust the strength of the ULMB mode. 10% lightboost gives better motion clarity than ULMB mode.

Brama wrote:

SS4 wrote:Anyone else gets a nvidia kernel crash when strobelight is running for too long?
Sometimes im gaming without lightboost but with the strobelight exe running and game crashes because of nvidia kernell . . .

Never seen this issue.
Do you overclock something in your system?

Yah i run a mild OC on my video card but this problems only seems to happen when the lightboost.exe is running, id have to test some more but its a weird coincidence . . .

SS4 wrote:

Brama wrote:

SS4 wrote:Anyone else gets a nvidia kernel crash when strobelight is running for too long?
Sometimes im gaming without lightboost but with the strobelight exe running and game crashes because of nvidia kernell . . .

Never seen this issue.
Do you overclock something in your system?

Yah i run a mild OC on my video card but this problems only seems to happen when the lightboost.exe is running, id have to test some more but its a weird coincidence . . .

You might want to talk to ToastyX to see if he can help at all, it being his program. Or maybe someone else here has a better idea. But it might be good to go to stock clocks for now, just in case.

Well, stock clock its harder to hit over 100 FPS so i just won't run the program otherwise itl look bad . . .
But i'll run some test when i have time and mention it to toasty if i find anything good(or bad i should say lol)

I've been running at 10% since I received my VG248QE earlier in January. I play a variety of rpg, rts and largely shooters and have noticed nice difference since testing at 100% in retrospect ( also cant' handle the brightness at 100% ) On titles that can be ran at 120fps constant, its great ( I sacrifice some IQ if needed to make this happen )

There are the odd games that are locked to 60fps due to internal timing issues (Terraria and Starbound in my case) so they can be fatiguing after a short while due to the flicker. Beyond that I'm very content with 10% Lightboost performance and brightness. Still prefer the color quality and viewing angles on my QHD 27" IPS dislpay ( which is now my secondary ) but I've found Lightboost to be more than a fair compromise given the huge difference I've experienced gaming.

I really don't get why most people complain about 10% being too dim for their preference and lightboost messing up colors, perhaps this is a setup related issue? I'm using an AMD card (7970) and an XL2420TE from BenQ, and 10% is too bright for my personal taste (which is why when off-game I'm always at 144hz PWM-Free), I wish there was something like 1%. I can lower the brightness to 0% on the XL2420TE's OSD while lightboost is activated but I don't think that's a good idea, any comments on this? And so far I haven't noticed any deterioration in colors, maybe it's a setup thing or perhaps I can't perceive it.

It's because different monitors are affected by light boost differently. Colors on one monitor might be better than another, and same goes for brightness.

Most of it too is personal preference. Some have spent alot of time with IPS monitors, and so the colors by default are worse, and even more so with lightboost.

I used lighboost with my BenQ XL2411T at 10%. Loved the smooth strafing and circling. The colors where washed out though, but that could be fixed to a bearable degree with the NVIDIA control panel. However, the contrast was horrible, I know other ppl that play high speed shooters who used an additional program to get better contrast.

Well, i'm pretty sure the technology will be polished a lot in the coming months/years as it it quickly picking up steam quickly amongst gamers and its still in its first iteration.