New 3D Vision R265 Drivers now available
  1 / 2    
Hi

The new CD 1.45 kits are now live.

Notebook http://www.nvidia.com/object/geforce-3d-vision-notebook-winvista-win7-cd-1.45-whql-driver.html
Desktop http://www.nvidia.com/object/geforce-3d-vision-winvista-win7-cd-1.45-whql-driver.html
(note there is an error as on 1/19/2011 on each page which states the GPU driver verison is 266.21. its not, its 266.58)

Here are some key things in this driver release:
[list]
[*]Adds support for new 3D Vision LCDs: Acer GN245HQ and Acer HN274H 3D Vision LCDs with built in 3D Vision IR emitters
[*]Adds support for new 3D Vision All-in-On PC: ASUS ET2400XVT
[*]Now supports Window Mode 3D for select games and applications including Google Earth, World of Warcraft, and many APAC iCafe games (please see release highlights on the desktop GPU link below)
[*]Fixed a problem with Call of Duty “iron sights mode” (zooming down the weapon) when using 3DTV Play
[*]Improved scaling quality with video streaming content from 3DVisionLive.com over previous 266.35 Beta driver
[/list]

Any question? Please ask.
Hi



The new CD 1.45 kits are now live.



Notebook http://www.nvidia.com/object/geforce-3d-vision-notebook-winvista-win7-cd-1.45-whql-driver.html

Desktop http://www.nvidia.com/object/geforce-3d-vision-winvista-win7-cd-1.45-whql-driver.html

(note there is an error as on 1/19/2011 on each page which states the GPU driver verison is 266.21. its not, its 266.58)



Here are some key things in this driver release:


  • Adds support for new 3D Vision LCDs: Acer GN245HQ and Acer HN274H 3D Vision LCDs with built in 3D Vision IR emitters
  • Adds support for new 3D Vision All-in-On PC: ASUS ET2400XVT
  • Now supports Window Mode 3D for select games and applications including Google Earth, World of Warcraft, and many APAC iCafe games (please see release highlights on the desktop GPU link below)
  • Fixed a problem with Call of Duty “iron sights mode” (zooming down the weapon) when using 3DTV Play
  • Improved scaling quality with video streaming content from 3DVisionLive.com over previous 266.35 Beta driver




Any question? Please ask.

#1
Posted 01/19/2011 05:53 PM   
Also, if you already installed the 266.58 GPU driver, here is the link to the 3D Vision Controller Driver.

http://www.nvidia.com/object/geforce-3d-vision-winvista-win7-266.21-whql-driver.html
Also, if you already installed the 266.58 GPU driver, here is the link to the 3D Vision Controller Driver.



http://www.nvidia.com/object/geforce-3d-vision-winvista-win7-266.21-whql-driver.html

#2
Posted 01/19/2011 05:57 PM   
I've downloaded the drivers uninstalled the older ones and when running to install the graphic drivers it says that hardware can't be found, any idea's?
I've downloaded the drivers uninstalled the older ones and when running to install the graphic drivers it says that hardware can't be found, any idea's?

#3
Posted 01/19/2011 06:34 PM   
[list][*]Now supports Window Mode 3D for select games and applications including Google Earth, World of Warcraft, and many APAC iCafe games (please see release highlights on the desktop GPU link below)[/list]
andrew?
1.> does windowed 3d mode suport 3dtv or 3dvision only?

2.> did u test vsync problem of 3dtv play in dx 10 and dx11 s3d mode ?
new driver 1.45 still has tearing problem
  • Now supports Window Mode 3D for select games and applications including Google Earth, World of Warcraft, and many APAC iCafe games (please see release highlights on the desktop GPU link below)

andrew?

1.> does windowed 3d mode suport 3dtv or 3dvision only?



2.> did u test vsync problem of 3dtv play in dx 10 and dx11 s3d mode ?

new driver 1.45 still has tearing problem

i7 8700K @4.9
GTX1080Ti
Asrock Z370 Gamming K6
Windows10 64bit
LG OLED UHD 3dtv 55E6K

#4
Posted 01/19/2011 06:43 PM   
[quote name='andrewf@nvidia' date='19 January 2011 - 11:57 AM' timestamp='1295459862' post='1179884']
Also, if you already installed the 266.58 GPU driver, here is the link to the 3D Vision Controller Driver.

http://www.nvidia.com/object/geforce-3d-vision-winvista-win7-266.21-whql-driver.html
[/quote]

Should I install this newer 3D Vision Controller Driver if I already have the 266.58 drivers installed with the older controller?
[quote name='andrewf@nvidia' date='19 January 2011 - 11:57 AM' timestamp='1295459862' post='1179884']

Also, if you already installed the 266.58 GPU driver, here is the link to the 3D Vision Controller Driver.



http://www.nvidia.com/object/geforce-3d-vision-winvista-win7-266.21-whql-driver.html





Should I install this newer 3D Vision Controller Driver if I already have the 266.58 drivers installed with the older controller?

#5
Posted 01/19/2011 07:19 PM   
Please, test any Driver before release. Try to see any video using Firefox and maximize tu full screen... the result is:
COMPUTER DO NOT RESPOND AND MUST RESTART WINDOWS !!!!!!!!!!

Also magicbright (using Samsung 2233RZ) is at full bright and I will have to visit the doctor to repair my eyes!!!. Only 5 minutes since installed this driver, and I hope not more surprises... (what I say?, it is not a surprise).
Please, test any Driver before release. Try to see any video using Firefox and maximize tu full screen... the result is:

COMPUTER DO NOT RESPOND AND MUST RESTART WINDOWS !!!!!!!!!!



Also magicbright (using Samsung 2233RZ) is at full bright and I will have to visit the doctor to repair my eyes!!!. Only 5 minutes since installed this driver, and I hope not more surprises... (what I say?, it is not a surprise).

- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)

#6
Posted 01/19/2011 07:19 PM   
Well I went ahead and just uninstalled the older controller driver an installed this one without any apparent issues.
Well I went ahead and just uninstalled the older controller driver an installed this one without any apparent issues.

#7
Posted 01/19/2011 07:24 PM   
Oh my. For me it seems EDID is now completely broken an my projector is no longer recognized. Now I can use whatever resolutions I want without annoying red text though. And no stupid maximum depth. The only problem is, the way I setup 1280x720@120Hz right now has left/right eye inverted, guess my timings are a bit off :P

EDIT: Alright, reinstalled the drivers, now cleaning the old settings and EDID works, but it's all broken in the same way as it was on the beta drivers. The drivers, while using EDID, somehow breaks the native! resolution of 1280x720@120Hz, confusing the projector which reverts to some 1280x1024@75Hz mode. 3D will therefore not work at all. (on edit2: removed some silly rant I put here /wink.gif' class='bbc_emoticon' alt=';)' /> )



EDIT2: Andrew, and other NVIDIA employees, if you're willing to listen, I might know the cause of this, see below...

On the 1.38 CD gfx drivers (260.99), when I go to Adjust Desktop size and position, only 3 of my 4 displays show, HOWEVER I can choose the scaling mode for all of the 3, and one of them is my projector. By default on these drivers, the projector is set to use the display's built-in scaling, this works fine. When I however choose one of the nvidia scaling modes, everything breaks the same way as on the newer drivers. (This might be because native resolution is detected as 1920x1080, while it is actually 1280x720).

Now on drivers > 1.38 CD, including the 1.45 CD, when I go to the Adjust Desktop size and position section, all 4 of my displays show up. I can however NOT set the scaling mode of the projector. The other 3 monitors have a default of NVIDIA scaling with fixed-aspect ratio. Now the latter makes it likely the same scaling mode is used for my projector, which is also why the proper resolution is broken.

From the above I can conclude there are 2 main things to fix:
1. Give the option to change scaling on the projector. (It's connected through VGA, I cannot use HDMI for it for several reasons)
2. Make the drivers recognize the correct native resolution. If it is wrong in projector EDID itself, please override it for the H5360 in the driver

Another thing you might add to the nvidia scaling options is the resolution to actually scale to. Maybe people want to scale to something else than native resolution; why not let them? Either put a resolution box at the scaling options, or add options for scaling everything to desktop resolution instead of native resolution.
Oh my. For me it seems EDID is now completely broken an my projector is no longer recognized. Now I can use whatever resolutions I want without annoying red text though. And no stupid maximum depth. The only problem is, the way I setup 1280x720@120Hz right now has left/right eye inverted, guess my timings are a bit off :P



EDIT: Alright, reinstalled the drivers, now cleaning the old settings and EDID works, but it's all broken in the same way as it was on the beta drivers. The drivers, while using EDID, somehow breaks the native! resolution of 1280x720@120Hz, confusing the projector which reverts to some 1280x1024@75Hz mode. 3D will therefore not work at all. (on edit2: removed some silly rant I put here /wink.gif' class='bbc_emoticon' alt=';)' /> )







EDIT2: Andrew, and other NVIDIA employees, if you're willing to listen, I might know the cause of this, see below...



On the 1.38 CD gfx drivers (260.99), when I go to Adjust Desktop size and position, only 3 of my 4 displays show, HOWEVER I can choose the scaling mode for all of the 3, and one of them is my projector. By default on these drivers, the projector is set to use the display's built-in scaling, this works fine. When I however choose one of the nvidia scaling modes, everything breaks the same way as on the newer drivers. (This might be because native resolution is detected as 1920x1080, while it is actually 1280x720).



Now on drivers > 1.38 CD, including the 1.45 CD, when I go to the Adjust Desktop size and position section, all 4 of my displays show up. I can however NOT set the scaling mode of the projector. The other 3 monitors have a default of NVIDIA scaling with fixed-aspect ratio. Now the latter makes it likely the same scaling mode is used for my projector, which is also why the proper resolution is broken.



From the above I can conclude there are 2 main things to fix:

1. Give the option to change scaling on the projector. (It's connected through VGA, I cannot use HDMI for it for several reasons)

2. Make the drivers recognize the correct native resolution. If it is wrong in projector EDID itself, please override it for the H5360 in the driver



Another thing you might add to the nvidia scaling options is the resolution to actually scale to. Maybe people want to scale to something else than native resolution; why not let them? Either put a resolution box at the scaling options, or add options for scaling everything to desktop resolution instead of native resolution.

Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|

#8
Posted 01/19/2011 08:17 PM   
Acer H5360 deph problem finally solved... better later than never. Thanks.
Acer H5360 deph problem finally solved... better later than never. Thanks.

- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "MSI GTX 660 TI"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)

#9
Posted 01/19/2011 09:24 PM   
I just tried these drivers, they won't set up 3D Vision on my 2010 Samsung plasma HDMI 1.4. The 3D Vision is there, but it's disabled for all HDMI1.4 displays.
Andrew, I paid good money for my 3D Vision kit only to find there are no drivers that work after CD1.33/258.xx. All drivers including CD1.45 work perfectly with all HDMI1.4 displays, so there is no reason to cheat customers out of 3D Vision software support just because they happen to have HDMI 1.4 instead of HDMI1.3.
PLease contact marketing and tell them to stop disabling 3D Vision for HDMI1.4 displays.
I just tried these drivers, they won't set up 3D Vision on my 2010 Samsung plasma HDMI 1.4. The 3D Vision is there, but it's disabled for all HDMI1.4 displays.

Andrew, I paid good money for my 3D Vision kit only to find there are no drivers that work after CD1.33/258.xx. All drivers including CD1.45 work perfectly with all HDMI1.4 displays, so there is no reason to cheat customers out of 3D Vision software support just because they happen to have HDMI 1.4 instead of HDMI1.3.

PLease contact marketing and tell them to stop disabling 3D Vision for HDMI1.4 displays.

#10
Posted 01/19/2011 10:11 PM   
Andrew, sorry if I sound like I'm just griping for no reason, but couldn't you people at nvidia use a little more care to make sure you are using the right numbers for your drivers. This driver thing is getting a little confusing for dummies like me. Isn't there some way to make it a little less confusing? For example, yesterday I downloaded and installed the 266.58 graphics and 3d vision drivers to replace the 260.99 graphics and 3d vision drivers I had previously been using. Well, the 260.63 3d vision controller driver(emitter driver) no longer worked with the new 266.58 graphics and 3d vision drivers.
So I got on the forum and "Bloody" was nice enough to tell me that I needed to try the 266.35 beta 3d vision controller driver(emitter driver). This driver did work, though I noticed under control panel--programs and features that it listed the driver as being 266.21!
Now I read this post about R265 Drivers(I have no idea what R265 is supposed to mean) and it says that a new emitter driver for the 266.58 graphics and 3d vision drivers is available that is WHQL and I'm thinking I had better replace the beta 266.35 emitter driver that was listed as 266.21 with the WHQL emitter driver that is mistakenly called 266.21 but is really ???.??!
What is the difference between the beta 266.35 emitter driver and the ???.?? WHQL emitter driver.
How is a driver WHQL certified if the version numbers for it aren't even right?
Also in the installation instructions for the CD kit (more confusing numbers!) the word "promoted" is mistakenly used instead of "prompted".
Maybe a little proof-reading is in order?
Please try to remember that when nvidia is catering to the large number of customers they service that details like these become more important than if you were just writing yourself a post-it note.
Please take time to either explain this driver numbering mess to your customers, or better yet, simplify it so that even a dummy like me can figure it out.
Andrew, sorry if I sound like I'm just griping for no reason, but couldn't you people at nvidia use a little more care to make sure you are using the right numbers for your drivers. This driver thing is getting a little confusing for dummies like me. Isn't there some way to make it a little less confusing? For example, yesterday I downloaded and installed the 266.58 graphics and 3d vision drivers to replace the 260.99 graphics and 3d vision drivers I had previously been using. Well, the 260.63 3d vision controller driver(emitter driver) no longer worked with the new 266.58 graphics and 3d vision drivers.

So I got on the forum and "Bloody" was nice enough to tell me that I needed to try the 266.35 beta 3d vision controller driver(emitter driver). This driver did work, though I noticed under control panel--programs and features that it listed the driver as being 266.21!

Now I read this post about R265 Drivers(I have no idea what R265 is supposed to mean) and it says that a new emitter driver for the 266.58 graphics and 3d vision drivers is available that is WHQL and I'm thinking I had better replace the beta 266.35 emitter driver that was listed as 266.21 with the WHQL emitter driver that is mistakenly called 266.21 but is really ???.??!

What is the difference between the beta 266.35 emitter driver and the ???.?? WHQL emitter driver.

How is a driver WHQL certified if the version numbers for it aren't even right?

Also in the installation instructions for the CD kit (more confusing numbers!) the word "promoted" is mistakenly used instead of "prompted".

Maybe a little proof-reading is in order?

Please try to remember that when nvidia is catering to the large number of customers they service that details like these become more important than if you were just writing yourself a post-it note.

Please take time to either explain this driver numbering mess to your customers, or better yet, simplify it so that even a dummy like me can figure it out.

#11
Posted 01/20/2011 09:44 AM   
[quote name='b4thman' date='19 January 2011 - 10:24 PM' timestamp='1295472256' post='1180048']
Acer H5360 deph problem finally solved... better later than never. Thanks.
[/quote]

So your H5360 is working without issues? WTF is wrong on my computer then? :P Only CD 1.38 and lower work correctly, like I said before...
[quote name='b4thman' date='19 January 2011 - 10:24 PM' timestamp='1295472256' post='1180048']

Acer H5360 deph problem finally solved... better later than never. Thanks.





So your H5360 is working without issues? WTF is wrong on my computer then? :P Only CD 1.38 and lower work correctly, like I said before...

Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|

#12
Posted 01/20/2011 04:39 PM   
I don't know if the 266.21 emitter driver is actually any newer or different than the 266.35 beta emmiter driver. The 266.35 beta emitter seems to work fine with 266.58 so far so I think I'll leave well enough alone.
I don't know if the 266.21 emitter driver is actually any newer or different than the 266.35 beta emmiter driver. The 266.35 beta emitter seems to work fine with 266.58 so far so I think I'll leave well enough alone.

#13
Posted 01/20/2011 11:47 PM   
I just updated to the latest Video Driver, 3D vision driver, and 3D vision controller, and my monitor will no longer enter the 3D mode.

I have an ASUS VG236, and whenever I try to run the setup wizard or any other game in 3D, the picture just flickers both images, and my monitor shows in red letters that it is in an incompatible 3d format.

Is anyone else running into this issue?
I just updated to the latest Video Driver, 3D vision driver, and 3D vision controller, and my monitor will no longer enter the 3D mode.



I have an ASUS VG236, and whenever I try to run the setup wizard or any other game in 3D, the picture just flickers both images, and my monitor shows in red letters that it is in an incompatible 3d format.



Is anyone else running into this issue?

#14
Posted 01/21/2011 12:47 AM   
[quote name='b4thman' date='19 January 2011 - 09:24 PM' timestamp='1295472256' post='1180048']
Acer H5360 deph problem finally solved... better later than never. Thanks.
[/quote]

Can you explain a little more what depth problem for the h5360 is fixed now?
[quote name='b4thman' date='19 January 2011 - 09:24 PM' timestamp='1295472256' post='1180048']

Acer H5360 deph problem finally solved... better later than never. Thanks.





Can you explain a little more what depth problem for the h5360 is fixed now?

#15
Posted 01/21/2011 07:17 AM   
  1 / 2    
Scroll To Top