Hey guys, I've got some troubling news. Turns out, driver 349.90 breaks every single game I've tried in 3D. This includes 3D Vision ready games like Tomb Raider (broken shadows), Witcher 2 (multiple issues) and Arkham City (shadows+bloom). Helixmod doesn't seem to hook in to any games I've tested, leaving them in their unfixed state after patches are installed. A few 3D Migoto features seem to work, but not many (and games using it end up mostly in their pre-fixed state).
This is a pretty big deal, and we need to act fast to bring this to nVidia's attention. If these changes get merged into the current steam of driver updates, we could be in trouble. If it's not fixed, it could also mean 3D dies with Win7/8. Or at least is significantly cripped, unless we can find a workaround for these new issues. I've made a thread on the driver feedback forums here, I encourage you to post in it to draw attention to it.
https://forums.geforce.com/default/topic/820731/geforce-drivers/349-90-breaks-3d-vision-entirely-/
It would also be fantastic if we could get a few people to install Windows 10 on a secondary hard drive, and to confirm (or hopefully debunk) my findings. You can get it at the link below, I recommend disconnecting all other hard drives while installing (to be safe).
http://windows.microsoft.com/en-au/windows/preview-iso
Hey guys, I've got some troubling news. Turns out, driver 349.90 breaks every single game I've tried in 3D. This includes 3D Vision ready games like Tomb Raider (broken shadows), Witcher 2 (multiple issues) and Arkham City (shadows+bloom). Helixmod doesn't seem to hook in to any games I've tested, leaving them in their unfixed state after patches are installed. A few 3D Migoto features seem to work, but not many (and games using it end up mostly in their pre-fixed state).
This is a pretty big deal, and we need to act fast to bring this to nVidia's attention. If these changes get merged into the current steam of driver updates, we could be in trouble. If it's not fixed, it could also mean 3D dies with Win7/8. Or at least is significantly cripped, unless we can find a workaround for these new issues. I've made a thread on the driver feedback forums here, I encourage you to post in it to draw attention to it.
https://forums.geforce.com/default/topic/820731/geforce-drivers/349-90-breaks-3d-vision-entirely-/
It would also be fantastic if we could get a few people to install Windows 10 on a secondary hard drive, and to confirm (or hopefully debunk) my findings. You can get it at the link below, I recommend disconnecting all other hard drives while installing (to be safe).
http://windows.microsoft.com/en-au/windows/preview-iso
A couple extra notes:
-The time to act on this is now. Windows 10 is coming this year, and nVidia are still preparing for it. It's going to be a lot easier to get them to course-correct on 3D now, than after mainstream release when they've got thousands more people flooding them with support issues
-Most of us won't be migrating to Windows 10 immediately, quite possibly not for a few years. But all OSes have a limited life, and we'll have to shift eventually. DX11 came out in 2009, and the first big DX11 exclusive (Battlefield 3) came out in 2011. There's no telling what the pace of DX12 adoption may be, but it's coming sooner or later. We need to do everything we can to make sure Windows 10 supports 3D at least as well as 7/8 does.
Games tested so far:
Witcher 2 - Broken shadows, broken bloom
Arkham City - Broken shadows, bloom
Tomb Raider 2013 - Broken shadows, 3D couldn't be enabled in settings - I'm guessing this means the driver was doing the 3D automatically, rather than the engine
Contrast (with helixmod fix) - Helixmod didn't kick in, so game was in it's pre-fixed state
Never Alone (with helixmod fix) - Same as above
Defence Grid 2 (with 3dmigoto fix) - Shadows were disabled (as they should be), but shader fixes weren't applying and the toggle for low convergence wasn't working
Shadow of Mordor (with 3dmigoto fix) - Looked pretty much as it did before the fix, also very unstable (with or without 3dmigoto)
-The time to act on this is now. Windows 10 is coming this year, and nVidia are still preparing for it. It's going to be a lot easier to get them to course-correct on 3D now, than after mainstream release when they've got thousands more people flooding them with support issues
-Most of us won't be migrating to Windows 10 immediately, quite possibly not for a few years. But all OSes have a limited life, and we'll have to shift eventually. DX11 came out in 2009, and the first big DX11 exclusive (Battlefield 3) came out in 2011. There's no telling what the pace of DX12 adoption may be, but it's coming sooner or later. We need to do everything we can to make sure Windows 10 supports 3D at least as well as 7/8 does.
Games tested so far:
Witcher 2 - Broken shadows, broken bloom
Arkham City - Broken shadows, bloom
Tomb Raider 2013 - Broken shadows, 3D couldn't be enabled in settings - I'm guessing this means the driver was doing the 3D automatically, rather than the engine
Contrast (with helixmod fix) - Helixmod didn't kick in, so game was in it's pre-fixed state
Never Alone (with helixmod fix) - Same as above
Defence Grid 2 (with 3dmigoto fix) - Shadows were disabled (as they should be), but shader fixes weren't applying and the toggle for low convergence wasn't working
Shadow of Mordor (with 3dmigoto fix) - Looked pretty much as it did before the fix, also very unstable (with or without 3dmigoto)
Running Windows 10 build 10041 and 349.90 driver. I have a Asus VG278H Monitor with built in 3Dvision emitter and a GTX 980.
No problem with Arkham Origins, Dead Space 3 (Helix fix), Assetto Corsa, rFactor, Raceroom Racing Experience, iRacing.
Also using 3DTV play with Total Media Theatre 6 to watch 3D blueray movies on a Acer H5360BD projector.
Running Windows 10 build 10041 and 349.90 driver. I have a Asus VG278H Monitor with built in 3Dvision emitter and a GTX 980.
No problem with Arkham Origins, Dead Space 3 (Helix fix), Assetto Corsa, rFactor, Raceroom Racing Experience, iRacing.
Also using 3DTV play with Total Media Theatre 6 to watch 3D blueray movies on a Acer H5360BD projector.
I happen to be in the middle of some major HDD consolidation and restructuring - As such I have a a couple of free HDD's. I planed to install Win 10(x64) on one of them - It might take me till tomm sometime to report back with any usable info.
As for the issue at hand I can offer 2 points of insight
1) The generalized observation (that i'm sure you already made) in regards to the fact that this is still a preview build and of course the current NV drivers are still beta/'wip's' and as such, will change many more times before release.
That was the optimistic approach, one that works fairly well regarding most previews/beta's/wip's etc.. But this is Nvidia's Driver Team & anyone that has waded through the murky waters of at least 2 GPU generation cycles will know that this approach id seriously flawed.
Ironically, MS's track record (Post Win'XP') regarding new OS launches and compatibility has been somewhat of a pain in the ass at best and a real nightmare at worst - especially as it pertains to the Graphics SubSystem. (Not that NV was a saint then either, the 'Vista' launch was atrocious)
2) They (MS) seem to have it nailed down fairly well this go-around, what with DX12 & The ability to mix various GPU's (Yup, ATI and Nvidia products working together under the hood of Win 10) Of course that remains to be seen as of yet and there is plenty of room for both ATI & NV to 'break' this feature artificially via their respective driver sets.
All that said, if it's broken that bad, there is NO WAY Nvidia is unaware of this! If/Since they are aware, the resulting action becomes a very purpose-full decision, which, for me at least, would really do my LOYALTY and My WALLET in, and I have been buying, selling, using & promoting NV's products (exclusively) for the better part of 17 years.
They crippled a few systems of mine starting with the 344.xx's driver sets where I have 3 GTX285's as dedicated PhysX GPU's that are Sub '400' series and therefore I am frozen in time with my drivers. Yeah, I could take them out, get new ones etc.. and so on - but why should I have too? I get WHY the newer drivers don't work/can't be used with sub '400' series GPU's installed as primary cards, but should still be an option for PhysX.
So, worry or not worry, act or don't - But when the next driver comes out and it's STILL broken, no matter how much noise we make they won't listen. They are quite aware of 'US' already and if, by now, they still don't get it/ or care to get it, they WON'T.
Well, i'll let you know, but PirateBGuy - you are no slouch, if the results of your efforts conclude the worst, there is little doubt to be had about the state of these particular NV driver's and the Win 10 preview.. it's what happens next that is crucial.. A one-off fluke is one thing, but 2 driver sets in a row is pretty much confirmation.. we shall see - how often are they releasing drivers for win 10?
Anyway, Hope this isn't a sign of things to come.
~Nutz
Oh, and thanks for bringing this to our attention!
I happen to be in the middle of some major HDD consolidation and restructuring - As such I have a a couple of free HDD's. I planed to install Win 10(x64) on one of them - It might take me till tomm sometime to report back with any usable info.
As for the issue at hand I can offer 2 points of insight
1) The generalized observation (that i'm sure you already made) in regards to the fact that this is still a preview build and of course the current NV drivers are still beta/'wip's' and as such, will change many more times before release.
That was the optimistic approach, one that works fairly well regarding most previews/beta's/wip's etc.. But this is Nvidia's Driver Team & anyone that has waded through the murky waters of at least 2 GPU generation cycles will know that this approach id seriously flawed.
Ironically, MS's track record (Post Win'XP') regarding new OS launches and compatibility has been somewhat of a pain in the ass at best and a real nightmare at worst - especially as it pertains to the Graphics SubSystem. (Not that NV was a saint then either, the 'Vista' launch was atrocious)
2) They (MS) seem to have it nailed down fairly well this go-around, what with DX12 & The ability to mix various GPU's (Yup, ATI and Nvidia products working together under the hood of Win 10) Of course that remains to be seen as of yet and there is plenty of room for both ATI & NV to 'break' this feature artificially via their respective driver sets.
All that said, if it's broken that bad, there is NO WAY Nvidia is unaware of this! If/Since they are aware, the resulting action becomes a very purpose-full decision, which, for me at least, would really do my LOYALTY and My WALLET in, and I have been buying, selling, using & promoting NV's products (exclusively) for the better part of 17 years.
They crippled a few systems of mine starting with the 344.xx's driver sets where I have 3 GTX285's as dedicated PhysX GPU's that are Sub '400' series and therefore I am frozen in time with my drivers. Yeah, I could take them out, get new ones etc.. and so on - but why should I have too? I get WHY the newer drivers don't work/can't be used with sub '400' series GPU's installed as primary cards, but should still be an option for PhysX.
So, worry or not worry, act or don't - But when the next driver comes out and it's STILL broken, no matter how much noise we make they won't listen. They are quite aware of 'US' already and if, by now, they still don't get it/ or care to get it, they WON'T.
Well, i'll let you know, but PirateBGuy - you are no slouch, if the results of your efforts conclude the worst, there is little doubt to be had about the state of these particular NV driver's and the Win 10 preview.. it's what happens next that is crucial.. A one-off fluke is one thing, but 2 driver sets in a row is pretty much confirmation.. we shall see - how often are they releasing drivers for win 10?
Anyway, Hope this isn't a sign of things to come.
~Nutz
Oh, and thanks for bringing this to our attention!
Very interesting. Thank you for the infos. Did this happen before with a WIP driver by Nvidia? Or is it the first time? I hope they will fix it, even that I am not planning to change to Windows 10 so quickly.
Very interesting. Thank you for the infos. Did this happen before with a WIP driver by Nvidia? Or is it the first time? I hope they will fix it, even that I am not planning to change to Windows 10 so quickly.
If you hover over the title the [img]https://forums.geforce.com/templates/default/images/forums/icon-pencil.png[/img] icon will appear, click it and you can edit the title if you wish. :)
So did this wind up being yet another botched Driver install 3D Vision is becoming infamous for or are you running a different build of WinX(or is it WindX ... Lol) than Mmed1?
If you hover over the title the icon will appear, click it and you can edit the title if you wish. :)
So did this wind up being yet another botched Driver install 3D Vision is becoming infamous for or are you running a different build of WinX(or is it WindX ... Lol) than Mmed1?
UPDATE: I ran DDU, completely removed the driver and reinstalled. This time, everything seems to be working properly. I guess Windows Update screwed something up. I've never seen a driver update screw things to that extent, but at least it was a passing glitch, rather than an OS/driver level disaster. I'll continue to keep an eye on it (I'm not using it as my daily OS), and report anything new.
Shadow of Mordor crashes a few seconds after loading a saved game/benchmark, but that happens in 2D without the fix, so we can assume that will get fixed. Good news!
UPDATE: I ran DDU, completely removed the driver and reinstalled. This time, everything seems to be working properly. I guess Windows Update screwed something up. I've never seen a driver update screw things to that extent, but at least it was a passing glitch, rather than an OS/driver level disaster. I'll continue to keep an eye on it (I'm not using it as my daily OS), and report anything new.
Shadow of Mordor crashes a few seconds after loading a saved game/benchmark, but that happens in 2D without the fix, so we can assume that will get fixed. Good news!
DDU works great, the only thing I do not like about it, is that it installs PAExec.
It worries me that this can easily be used as a back door to my PC.
[quote="D-Man11"]DDU works great, the only thing I do not like about it, is that it installs PAExec.
It worries me that this can easily be used as a back door to my PC.[/quote] Interesting, care to expand on that? I can't find it listed under programs, wondering if it's worth removing it.
I've been using WinPatrol ever since I got my first PC. It's nice because it will alert you to new programs and asks if you want to grant or deny permission for that program.
My anti virus didn't flag it but Winpatrol alerted me, PAExec is a remote desktop viewer.
DDU's author mentions support, so I imagine it's for that and that it's legit.
Nevertheless, I would prefer it to be optional.
http://www.poweradmin.com/paexec/
I'm using an older version of DDU, but if it's still a part of the install you can find it by using Windows search function.
I've been using WinPatrol ever since I got my first PC. It's nice because it will alert you to new programs and asks if you want to grant or deny permission for that program.
My anti virus didn't flag it but Winpatrol alerted me, PAExec is a remote desktop viewer.
DDU's author mentions support, so I imagine it's for that and that it's legit.
Nevertheless, I would prefer it to be optional.
http://www.poweradmin.com/paexec/
I'm using an older version of DDU, but if it's still a part of the install you can find it by using Windows search function.
Does the program get removed when you uninstall DDU through add/remove programs though? I don't see any reason to leave any programs that I use once to stay in memory anyways.
Does the program get removed when you uninstall DDU through add/remove programs though? I don't see any reason to leave any programs that I use once to stay in memory anyways.
Where would I find it? DDU doesn't have an installer as such, it's always been an extract-and-run kind of program, which I usually put in a folder on the desktop, and delete when no longer required.
Where would I find it? DDU doesn't have an installer as such, it's always been an extract-and-run kind of program, which I usually put in a folder on the desktop, and delete when no longer required.
A quick forum search shows him using it in his other program, Give Me Power.
So I'm now thinking I may have inadvertently added this in myself when I loaded a thumbdrive with files from my downloads folder to transfer to a second computer.
I think I misclicked it, when I was using DDU to change drivers because it was all in the same folder. Ooops....sorry for the false alarm...
https://forums.geforce.com/default/topic/754605/geforce-drivers/givemepower-gmp-v2-0-0-0-released-06-19-14-/post/4245718/#4245718
A quick forum search shows him using it in his other program, Give Me Power.
So I'm now thinking I may have inadvertently added this in myself when I loaded a thumbdrive with files from my downloads folder to transfer to a second computer.
I think I misclicked it, when I was using DDU to change drivers because it was all in the same folder. Ooops....sorry for the false alarm...
This is a pretty big deal, and we need to act fast to bring this to nVidia's attention. If these changes get merged into the current steam of driver updates, we could be in trouble. If it's not fixed, it could also mean 3D dies with Win7/8. Or at least is significantly cripped, unless we can find a workaround for these new issues. I've made a thread on the driver feedback forums here, I encourage you to post in it to draw attention to it.
https://forums.geforce.com/default/topic/820731/geforce-drivers/349-90-breaks-3d-vision-entirely-/
It would also be fantastic if we could get a few people to install Windows 10 on a secondary hard drive, and to confirm (or hopefully debunk) my findings. You can get it at the link below, I recommend disconnecting all other hard drives while installing (to be safe).
http://windows.microsoft.com/en-au/windows/preview-iso
-The time to act on this is now. Windows 10 is coming this year, and nVidia are still preparing for it. It's going to be a lot easier to get them to course-correct on 3D now, than after mainstream release when they've got thousands more people flooding them with support issues
-Most of us won't be migrating to Windows 10 immediately, quite possibly not for a few years. But all OSes have a limited life, and we'll have to shift eventually. DX11 came out in 2009, and the first big DX11 exclusive (Battlefield 3) came out in 2011. There's no telling what the pace of DX12 adoption may be, but it's coming sooner or later. We need to do everything we can to make sure Windows 10 supports 3D at least as well as 7/8 does.
Games tested so far:
Witcher 2 - Broken shadows, broken bloom
Arkham City - Broken shadows, bloom
Tomb Raider 2013 - Broken shadows, 3D couldn't be enabled in settings - I'm guessing this means the driver was doing the 3D automatically, rather than the engine
Contrast (with helixmod fix) - Helixmod didn't kick in, so game was in it's pre-fixed state
Never Alone (with helixmod fix) - Same as above
Defence Grid 2 (with 3dmigoto fix) - Shadows were disabled (as they should be), but shader fixes weren't applying and the toggle for low convergence wasn't working
Shadow of Mordor (with 3dmigoto fix) - Looked pretty much as it did before the fix, also very unstable (with or without 3dmigoto)
No problem with Arkham Origins, Dead Space 3 (Helix fix), Assetto Corsa, rFactor, Raceroom Racing Experience, iRacing.
Also using 3DTV play with Total Media Theatre 6 to watch 3D blueray movies on a Acer H5360BD projector.
As for the issue at hand I can offer 2 points of insight
1) The generalized observation (that i'm sure you already made) in regards to the fact that this is still a preview build and of course the current NV drivers are still beta/'wip's' and as such, will change many more times before release.
That was the optimistic approach, one that works fairly well regarding most previews/beta's/wip's etc.. But this is Nvidia's Driver Team & anyone that has waded through the murky waters of at least 2 GPU generation cycles will know that this approach id seriously flawed.
Ironically, MS's track record (Post Win'XP') regarding new OS launches and compatibility has been somewhat of a pain in the ass at best and a real nightmare at worst - especially as it pertains to the Graphics SubSystem. (Not that NV was a saint then either, the 'Vista' launch was atrocious)
2) They (MS) seem to have it nailed down fairly well this go-around, what with DX12 & The ability to mix various GPU's (Yup, ATI and Nvidia products working together under the hood of Win 10) Of course that remains to be seen as of yet and there is plenty of room for both ATI & NV to 'break' this feature artificially via their respective driver sets.
All that said, if it's broken that bad, there is NO WAY Nvidia is unaware of this! If/Since they are aware, the resulting action becomes a very purpose-full decision, which, for me at least, would really do my LOYALTY and My WALLET in, and I have been buying, selling, using & promoting NV's products (exclusively) for the better part of 17 years.
They crippled a few systems of mine starting with the 344.xx's driver sets where I have 3 GTX285's as dedicated PhysX GPU's that are Sub '400' series and therefore I am frozen in time with my drivers. Yeah, I could take them out, get new ones etc.. and so on - but why should I have too? I get WHY the newer drivers don't work/can't be used with sub '400' series GPU's installed as primary cards, but should still be an option for PhysX.
So, worry or not worry, act or don't - But when the next driver comes out and it's STILL broken, no matter how much noise we make they won't listen. They are quite aware of 'US' already and if, by now, they still don't get it/ or care to get it, they WON'T.
Well, i'll let you know, but PirateBGuy - you are no slouch, if the results of your efforts conclude the worst, there is little doubt to be had about the state of these particular NV driver's and the Win 10 preview.. it's what happens next that is crucial.. A one-off fluke is one thing, but 2 driver sets in a row is pretty much confirmation.. we shall see - how often are they releasing drivers for win 10?
Anyway, Hope this isn't a sign of things to come.
~Nutz
Oh, and thanks for bringing this to our attention!
---- Core System Components ----
(MBD) EVGA® Classified™ (x58) E760
(CPU) Intel® i7™ '980x' (OC'd) @ 4.8Ghz
(CPU) Corsair® (CPU) Cooling™ (H50)
(MEM) Corsair® (MEM) Dominator(GT)™ 12GB @ 2000Mhz
(PSU) PC)P&C™ (PSU)'T12W' @ 1200w
(CSE) Cooler Master® Stacker™ (830)
---- (3D) Graphics Sub'Sys ----
(2x) EVGA® GTX'970 (SC) - Nvidia® SLi™
(1x) EVGA® GTX'660 (Ti) - Nvidia® PhysX™
(1x) ACER® (GN) 246(HL) - Nvidia® 3DVision™
(1x) ASUS® (VG) 248(QE) - Nvidia® 3DVision™
(1x) ACER® (GN) 246(HL) - Nvidia® 3DVision™
---- Audio & System Control ----
(1x) ASUS® - Xonar™ (HDAV1.3)
(1x) VL'Sys® - MPlay202+ 'GUI' & (RF) Remote
---- Storage (HDD's) & Media (ODD's) PB & REC ----
(1x) (SSD) Samsung® - 850(PRO) '3D'Vertical™
(1x) (2TB) Seagate® - Hybrid Series™
(4x) (2TB) W.Digital® - 'Blacks'™
(2x) (ODD) LG® BluRay™ - 'Play'n'Burn'
---- Nvidia® (WHQL) Drivers (x64) In Use ----
(NV®)DR - v347.88 (WHQL) - Primary (GTA V)
(NV®)DR - v350.12 (WHQL) - Testing (Stable)
(NV®)DR - v353.06 (WHQL) - All Other Titles
Intel Core i7-3820, 4 X 3,60 GHz overclocked to 4,50 GHz ; EVGA Titan X 12VRAM ; 16 GB Corsair Vengeance DDR-1600 (4x 4 GB) ; Asus VG278H 27-inch incl. 3D vision 2 glasses, integrated transmitter ; Xbox One Elite wireless controller ; Windows 10HTC VIVE 2,5 m2 roomscale3D VISION GAMERS - VISIT ME ON STEAM and feel free to add me: http://steamcommunity.com/profiles/76561198064106555 YOUTUBE: https://www.youtube.com/channel/UC1UE5TPoF0HX0HVpF_E4uPQ STEAM CURATOR: https://store.steampowered.com/curator/33611530-Streaming-Deluxe/
So did this wind up being yet another botched Driver install 3D Vision is becoming infamous for or are you running a different build of WinX(or is it WindX ... Lol) than Mmed1?
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Shadow of Mordor crashes a few seconds after loading a saved game/benchmark, but that happens in 2D without the fix, so we can assume that will get fixed. Good news!
It worries me that this can easily be used as a back door to my PC.
My anti virus didn't flag it but Winpatrol alerted me, PAExec is a remote desktop viewer.
DDU's author mentions support, so I imagine it's for that and that it's legit.
Nevertheless, I would prefer it to be optional.
http://www.poweradmin.com/paexec/
I'm using an older version of DDU, but if it's still a part of the install you can find it by using Windows search function.
3D Vision/TRIDEF User
SHIELD portable/tablet/tv
So I'm now thinking I may have inadvertently added this in myself when I loaded a thumbdrive with files from my downloads folder to transfer to a second computer.
I think I misclicked it, when I was using DDU to change drivers because it was all in the same folder. Ooops....sorry for the false alarm...
https://forums.geforce.com/default/topic/754605/geforce-drivers/givemepower-gmp-v2-0-0-0-released-06-19-14-/post/4245718/#4245718