Emmiter will not initialise
Hi there

Im having a problem with your new beta drivers, and the ones before the bf3 ones. all of the 285.* drivers

If I install the 280.26 drivers 3D vision works fine, but if I install the beta drivers, I cannot enable 3d vision at all.
The is a faint green light on the emitter, as if its installed - devmgmt.msc (device manager) shows the driver is installed and enabled.

I have disabled user Access Control
I have changed bcdedit to disable the driver integrity checks (as the 3d vision driver shows as unsigned during installation)

Still Nothing.

The Enable 3D vision application cannot detect the emitter - when i select emitter and glasses on the list - it tells me to plug it in, and install it. the next button is greyed out.
I've tested this with both cards i own and the result is the same when using the beta drivers on both.

The system isn't a gaming rig, but might as well be - Its for my development (I'm a c# developer)

i7 950 @ 3.2GHZ
12GB XMS3
Gigabyte GTX 560TI (tried also with the Asus enGT430)
750Watt Antec PSU

I will role back to the previous official release. But I want to play battlefield when that is out on the 28th (UK), and Arkham City (considering it came free with my card, plus arkham asylum looks amazing in 3D), both in 3D.
With this issue - I will not be able to activate the emitter in battlefield as it requires the latest driver to even launch.
Hi there



Im having a problem with your new beta drivers, and the ones before the bf3 ones. all of the 285.* drivers



If I install the 280.26 drivers 3D vision works fine, but if I install the beta drivers, I cannot enable 3d vision at all.

The is a faint green light on the emitter, as if its installed - devmgmt.msc (device manager) shows the driver is installed and enabled.



I have disabled user Access Control

I have changed bcdedit to disable the driver integrity checks (as the 3d vision driver shows as unsigned during installation)



Still Nothing.



The Enable 3D vision application cannot detect the emitter - when i select emitter and glasses on the list - it tells me to plug it in, and install it. the next button is greyed out.

I've tested this with both cards i own and the result is the same when using the beta drivers on both.



The system isn't a gaming rig, but might as well be - Its for my development (I'm a c# developer)



i7 950 @ 3.2GHZ

12GB XMS3

Gigabyte GTX 560TI (tried also with the Asus enGT430)

750Watt Antec PSU



I will role back to the previous official release. But I want to play battlefield when that is out on the 28th (UK), and Arkham City (considering it came free with my card, plus arkham asylum looks amazing in 3D), both in 3D.

With this issue - I will not be able to activate the emitter in battlefield as it requires the latest driver to even launch.

#1
Posted 10/17/2011 08:35 AM   
I have exactly the same problem, had to roll back to the 280.xx which means no Rage for me at the moment. I posted about it a little while ago but didn't get much help. Hopefully we'll be luckier this time!
I have exactly the same problem, had to roll back to the 280.xx which means no Rage for me at the moment. I posted about it a little while ago but didn't get much help. Hopefully we'll be luckier this time!

#2
Posted 10/17/2011 06:13 PM   
[quote name='T_L_T' date='17 October 2011 - 06:13 PM' timestamp='1318875201' post='1309445']
I have exactly the same problem, had to roll back to the 280.xx which means no Rage for me at the moment. I posted about it a little while ago but didn't get much help. Hopefully we'll be luckier this time!
[/quote]

I Hope so man :D
Battlefield is out in a week!

I'm sorry to say this, but I am glad someone else has the same problem. Thought is was just me. Haven't been able to find anyone else with the problem anywhere on the net
Do you know if its possible to use the new driver, but with the old 3d vision driver (i.e. unselecting 3d vision driver on custom install?)

I'm going to give it a try when I get back from work.
Will Report back. Doubt it will work.
[quote name='T_L_T' date='17 October 2011 - 06:13 PM' timestamp='1318875201' post='1309445']

I have exactly the same problem, had to roll back to the 280.xx which means no Rage for me at the moment. I posted about it a little while ago but didn't get much help. Hopefully we'll be luckier this time!





I Hope so man :D

Battlefield is out in a week!



I'm sorry to say this, but I am glad someone else has the same problem. Thought is was just me. Haven't been able to find anyone else with the problem anywhere on the net

Do you know if its possible to use the new driver, but with the old 3d vision driver (i.e. unselecting 3d vision driver on custom install?)



I'm going to give it a try when I get back from work.

Will Report back. Doubt it will work.

#3
Posted 10/18/2011 03:47 PM   
Thought that might work myself but no luck... Give it a go though, you may see something I missed...
Thought that might work myself but no luck... Give it a go though, you may see something I missed...

#4
Posted 10/18/2011 05:07 PM   
[quote name='T_L_T' date='18 October 2011 - 05:07 PM' timestamp='1318957631' post='1309915']
Thought that might work myself but no luck... Give it a go though, you may see something I missed...
[/quote]

Aye your right man

Tried it, no success. manually found, and launched the nvwiz file to enable 3d vision, but kicks out saying driver mismatch between 3d vision controller and display driver... No go on that.
Fully removed everything
Gone into safe mode and reinstalled the new beta drivers. Didn't plug the emitter in until the wizard was launched and waiting. It installed the USB controller. still cannot initialize it. Tried control + T, doesn't work. neither does the button.
I've gone as far as a fresh windows install - and that doesn't work.

[b]One thing i did notice was, during install the only driver not digitally signed was the 3d vision usb driver. I had to agree to install and enable it. All the others are beta drivers, but they were signed. Why is this?

I have disabled driver integrity check in BCDedit - Still the same problem.[/b]


All my tests have been in windows 7 ultimate 64bit.
This is my dev PC, for work, so I have and i7, 12Gb ram, etc etc.... I will not step down to a 32bit OS and lose support for 8GB of my RAM.

Actually, thinking about it.... TLT - what motherboard do you have?
I have an ASUS sabertooth x58. the board has the NEC USB3 controller.
The only thing i have yet to try is my two front USB2.0 ports.

I'll try those now, and report back



*****EDIT*****

OK - I looks like that was the problem. The driver doesn't seem to work at USB 3.0. upon plugging it into my front ports - it was detected by 3d setup straight away, and works.
I will try to update my NEC drivers now

Failing that - I'll buy a USB 2.0 card until NVIDIA get their act in gear and sort this. I refuse to have it plugged into my front USB port.

i will update again once i have updated the USb drivers

Driver Update did not work... however... I plugged the 3d controller into another port on the back and it works fine!
Pretty weird that it'll work in the other port on the old driver but not in the new, unless the power is regulated slightly different.
[quote name='T_L_T' date='18 October 2011 - 05:07 PM' timestamp='1318957631' post='1309915']

Thought that might work myself but no luck... Give it a go though, you may see something I missed...





Aye your right man



Tried it, no success. manually found, and launched the nvwiz file to enable 3d vision, but kicks out saying driver mismatch between 3d vision controller and display driver... No go on that.

Fully removed everything

Gone into safe mode and reinstalled the new beta drivers. Didn't plug the emitter in until the wizard was launched and waiting. It installed the USB controller. still cannot initialize it. Tried control + T, doesn't work. neither does the button.

I've gone as far as a fresh windows install - and that doesn't work.



One thing i did notice was, during install the only driver not digitally signed was the 3d vision usb driver. I had to agree to install and enable it. All the others are beta drivers, but they were signed. Why is this?



I have disabled driver integrity check in BCDedit - Still the same problem.






All my tests have been in windows 7 ultimate 64bit.

This is my dev PC, for work, so I have and i7, 12Gb ram, etc etc.... I will not step down to a 32bit OS and lose support for 8GB of my RAM.



Actually, thinking about it.... TLT - what motherboard do you have?

I have an ASUS sabertooth x58. the board has the NEC USB3 controller.

The only thing i have yet to try is my two front USB2.0 ports.



I'll try those now, and report back







*****EDIT*****



OK - I looks like that was the problem. The driver doesn't seem to work at USB 3.0. upon plugging it into my front ports - it was detected by 3d setup straight away, and works.

I will try to update my NEC drivers now



Failing that - I'll buy a USB 2.0 card until NVIDIA get their act in gear and sort this. I refuse to have it plugged into my front USB port.



i will update again once i have updated the USb drivers



Driver Update did not work... however... I plugged the 3d controller into another port on the back and it works fine!

Pretty weird that it'll work in the other port on the old driver but not in the new, unless the power is regulated slightly different.

#5
Posted 10/18/2011 11:13 PM   
Dude you are a genius! Different motherboard (gigabyte x5a ud3r) but same problem with usb 3, it uses NEC drivers too. Battlefield 3d is a go!
Dude you are a genius! Different motherboard (gigabyte x5a ud3r) but same problem with usb 3, it uses NEC drivers too. Battlefield 3d is a go!

#6
Posted 10/18/2011 11:54 PM   
I have found that usb3 has always given me problems. Its an issue with various drivers ive used. Its one of the first things i check when i have an emitter issue. If your like me and have a ratsnest of wires running into the back of the pc and you disconnect them for a monthly dusting, i find i always plug the damm emitter into usb3. One day ill put some tape on the emitter wire so i can find it amoung the rest of the wires.
I have found that usb3 has always given me problems. Its an issue with various drivers ive used. Its one of the first things i check when i have an emitter issue. If your like me and have a ratsnest of wires running into the back of the pc and you disconnect them for a monthly dusting, i find i always plug the damm emitter into usb3. One day ill put some tape on the emitter wire so i can find it amoung the rest of the wires.
#7
Posted 10/19/2011 03:13 AM   
Glad it worked for you too TLT :D See you on the battlefield!
Seems strange that it works with the Older Driver though... Ahh Well - Lol.

Good tip about the tape idea. Might bung a circular label on the end, or a dot with a marker... Just so I know which is the right one in future :D
Glad it worked for you too TLT :D See you on the battlefield!

Seems strange that it works with the Older Driver though... Ahh Well - Lol.



Good tip about the tape idea. Might bung a circular label on the end, or a dot with a marker... Just so I know which is the right one in future :D

#8
Posted 10/19/2011 08:26 AM   
Silver Sharpie Metallic !!!!!!!!!!!
I luv my Sharpies
Best thing evuhhhh

Seriously, the Sharpie Metallic (silver) permanent markers are the best thing ever for marking proprietary cables and power bricks.

http://www.amazon.com/Sharpie-Metallic-Permanent-Markers-39108PP/dp/B00009RAX4/ref=sr_1_sc_1?ie=UTF8&qid=1319026222&sr=8-1-spell
Silver Sharpie Metallic !!!!!!!!!!!

I luv my Sharpies

Best thing evuhhhh



Seriously, the Sharpie Metallic (silver) permanent markers are the best thing ever for marking proprietary cables and power bricks.



http://www.amazon.com/Sharpie-Metallic-Permanent-Markers-39108PP/dp/B00009RAX4/ref=sr_1_sc_1?ie=UTF8&qid=1319026222&sr=8-1-spell

#9
Posted 10/19/2011 12:17 PM   
Scroll To Top