NVIDIA Driver 332.21 fixes surround 1440p 120Hz (and LightBoost?)

Posted Jan 7, 2014 by

Reports have come in that NVIDIA graphics drivers 332.21 fixes surround monitor issues with very custom configurations!

This includes surround LightBoost (inconsistent reports), and surround 1440p 120Hz with overclockable 120Hz monitors (confirmed reports) including the popular QNIX QX2710 Evolution 2.

About Mark Rejhon

Also known as Chief Blur Buster. Founder of Blur Busters. Inventor of TestUFO. Read more about him on the About Mark page.

9 Comments For “NVIDIA Driver 332.21 fixes surround 1440p 120Hz (and LightBoost?)”

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Sort by:   newest | oldest | most liked
mrfix
Member
mrfix

I’ve got dual GTX-690s running in quad-SLI with the 332.21 driver, with three ASUS VG278HE monitors @ 5760×1080 in 2D surround, and these drivers don’t allow me to enable Lightboost with Strobelight Beta 4.

I’m running Windows 8 64-bit. If you need any more information, let me know. 🙂

I’m using the “I’m going to run in 3D mode with my emitter and just disable 3D instead” in the meantime. 🙂

Like0Vote Down 
10 years 3 months ago
Mark Rejhon
Author
Mark Rejhon

Bad news for LightBoost, it seems. I’ve edited the post accordingly.
Well, it does work for 1440p 120Hz surround.

That said, there has been success reports via the LightBoost Hardware Modification HOWTO to get LightBoost working in triple surround mode, without needing to wait for fixed drivers.I got inconsistent reports.

Like0Vote Down 
10 years 3 months ago
apoc se7en
Member
apoc se7en

I’ve been trying to get my 1440p surround tempest overlords to oc in surround since Nvidia drivers screwed things up. I was ecstatic to read 332.21 fixed this. Unfortunately, it doesn’t seem to be working for me. I use NVIDIA patcher, CRU, set each over clock independently, but when I try to join the monitors in surround, it fails unless I have the default framerate listed in CRU – then it will only go into surround at 59.95hz. Any thoughts? Thanks in advance.

Like0Vote Down 
10 years 1 month ago
mrfix
Member
mrfix

Yeah, using the emitter works for me, so it’s OK, but I’d rather be able to enable LightBoost in software, of course. 🙂

Like0Vote Down 
10 years 3 months ago
GitDat
Member
GitDat

How do you enable the emitter? I must’ve missed this trick 🙂

Like0Vote Down 
10 years 3 months ago
GitDat
Member
GitDat

It works! Thanks 🙂 But now my frame rate has been cut in half. I usually get 120 fps minimum on BF4 but with this method I’m around 60 fps. I just can’t win! lol

Like0Vote Down 
10 years 3 months ago
Mark Rejhon
Author
Mark Rejhon

Frame rate display is often false in 3D mode.
FRAPS reports incorrect frame rates when trying to measure 3D stereoscopic mode during 2D mode (Control+T)
If it still looks equally smooth as with LightBoost enabled, then you’re all golden.

If frame rate really does look twice as slow, try disabling-and-reenabling Control+T, as well as changing VSYNC modes. Also try exit-and-reenter (Alt+Tab).

Like0Vote Down 
10 years 3 months ago
Mark Rejhon
Author
Mark Rejhon

Do you have the 3D glasses and the 3D Vision emitter?

If so, you just have to follow the standard 3D Vision surround setup instructions, and use the Control+T method of enabling/disable LightBoost. This may require uninstalling the Strobelight modes, and reinstalling the NVIDIA drivers (or using the newer Strobelight Beta 4). Once you make sure 3D stereoscopic surround is working, hit Control+T to disable stereoscopic. You’ll still have LightBoost 2D in surround mode still running.

Try this approach out, if you prefer not to do the Hardware modification approach.

Like0Vote Down 
10 years 3 months ago
GitDat
Member
GitDat

I tried these drivers this morning along with the ToastyX strobelight beta4 in Surround and couldn’t get Lightboost to initialize 🙁

Like0Vote Down 
10 years 3 months ago
wpDiscuz

Recent Content

Blur Buster Forums

Blur Busters Forums

TestUFO Motion Tests

TestUFO Motion Tests