3D Vision @ Windows 10
  4 / 6    
[quote=""]3D works fine for me under W10, it's the 3DTV activation which is still not up which is more worrying, blame NVIDIA, not MS. In general the performance under W10 is a lot better, Witcher 3 runs visibly faster under W10, and I can enable more options under the Ultra setting. [/quote] Not to be harsh, but that performance improvement is nearly certainly going to be placebo effect. Here is a full benchmark demonstrating no difference from Win8.1 to Win10. http://www.guru3d.com/articles-pages/windows-8-1-vs-10-graphics-performance-review,1.html It's always possible Witcher3 some sort of an outlier, but it's very unlikely.
said:3D works fine for me under W10, it's the 3DTV activation which is still not up which is more worrying, blame NVIDIA, not MS.

In general the performance under W10 is a lot better, Witcher 3 runs visibly faster under W10, and I can enable more options under the Ultra setting.

Not to be harsh, but that performance improvement is nearly certainly going to be placebo effect.

Here is a full benchmark demonstrating no difference from Win8.1 to Win10.


http://www.guru3d.com/articles-pages/windows-8-1-vs-10-graphics-performance-review,1.html


It's always possible Witcher3 some sort of an outlier, but it's very unlikely.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#46
Posted 08/11/2015 01:58 AM   
I just upgraded my non gaming laptop to windows 10. So far I am liking it. I am about to rebuild my gaming machine with new motherboard, processor and single 980 ti. I am hoping to put windows 10 on it. So I am hoping some other people will test 3d vision with windows 10 so I will know if it is a good idea to switch to windows 10 for my (3d) gaming pc.
I just upgraded my non gaming laptop to windows 10. So far I am liking it. I am about to rebuild my gaming machine with new motherboard, processor and single 980 ti. I am hoping to put windows 10 on it. So I am hoping some other people will test 3d vision with windows 10 so I will know if it is a good idea to switch to windows 10 for my (3d) gaming pc.

NZXT Noctis 450. Asus ROG Formula VIII, 6700k, NZXT Kracken x61. Avexir Core DDR4 (Red) 16g. Windows 10. Samsung Evo 1T & 2T SSD. Asus Strix 2080 ti. EVGA 1300w Modular Gold PSU.
Asus ROG Swift PG278Q Monitor: 1440p 3D Vision

#47
Posted 08/12/2015 03:10 AM   
To be totally honest, I think all focus should be on Windows 10. Microsoft is clearly all in. They want to get everyone on the same version as much as possible in order to have a single stable platform to maintain instead of, well, really, dozens. I actually do think long term it's a good strategy, and I'm still kinda amazed they did it (giving it away, I mean). Anyway, if they're creating "a single platform for everybody", it's clearly going to get *all* their real support. Windows 10 has been regularly touted as the "last version of Windows". What previous set of hackers/coders has had the possible opportunity to write fixes/hacks that could last *forever*? (Well, forever in computer terms, anyway). It's also my understanding that Windows 10 was redesigned to be FAR more modular than previous versions. That *is* the proper way to do things. Anyone think Open Source Windows 10 may ever become a thing?
To be totally honest, I think all focus should be on Windows 10. Microsoft is clearly all in. They want to get everyone on the same version as much as possible in order to have a single stable platform to maintain instead of, well, really, dozens. I actually do think long term it's a good strategy, and I'm still kinda amazed they did it (giving it away, I mean).

Anyway, if they're creating "a single platform for everybody", it's clearly going to get *all* their real support.

Windows 10 has been regularly touted as the "last version of Windows". What previous set of hackers/coders has had the possible opportunity to write fixes/hacks that could last *forever*? (Well, forever in computer terms, anyway).

It's also my understanding that Windows 10 was redesigned to be FAR more modular than previous versions. That *is* the proper way to do things. Anyone think Open Source Windows 10 may ever become a thing?

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#48
Posted 08/12/2015 06:13 AM   
[u]@Mournz[/u]: Running Win10 with a 980ti would be a very poor choice at the moment. 980ti would force you to use latest drivers like 353.06 and above. Branch 353 seems to introduce the problem of running WDDM 2.0 when on Win10, which translates into completely broken 3D Vision on Win10 for apparently DX11 games. We know for sure that Witcher3 and FarCry4 are DOA. See Helifax's bug report and DarkStarSword's FC4 page. [u]@QWinn[/u]: With all respect, you are new to 3D Vision, right? I've been working on 3Dmigoto for the past 1.5 years, and using HelixMod for another 1.5 years before that. If you don't think I know what I'm talking about, then I just don't know what to say. 3D Vision is in a precarious state today, it's not well supported, as has not been well supported for over 3 years. As in, NVidia fixes occasional things, but botches others while they do it. And they take *forever* to fix things. Couldn't play 3D Blu Rays for over 10 months. New drivers have broken previous fixes- enough to drive eqzitara away altogether (a former superstar, Helix's right hand man). SLI works, on some games, but not others. SLI is still broken on ROG Swift in 3D. 3D TV Play activation server is offline, for two months. See: [url]https://forums.geforce.com/default/topic/847809/list-of-3d-vision-problems/[/url] Now here you are, touting the wonders of Win10 and how the future is glorious and clear, after Win10 has been out a whole week. Meanwhile Win10+NVidia is destroying LCD panels in laptops, and is [s]DOA for DX11 games with driver 353.62.[/s] (Edit:less clear, only seems to affect a couple of games.) Now you personally may be willing to pay the price for running Win10, but suggesting that everyone should is absolutely terrible advice. If you don't care about 3D, that's totally fine, but if you do care about 3D, the fixes run better, are more stable, and have more workarounds on Win7. Anyone who cares about 3D, should be running Win7 for their gaming. If you have time to burn, running Win 8.1 and Win 10 are OK options, but I [i]promise[/i] you that you will have more problems, and need to jack around a lot more with those OSes. [i]ALL [/i]of the shaderhackers who make the actual fixes run Win7, that's where they are developed and tested. Some day Win10 will be the preferred OS and things will be stable, or 3D Vision will be completely dead, one of the two. That day is not today.
@Mournz: Running Win10 with a 980ti would be a very poor choice at the moment. 980ti would force you to use latest drivers like 353.06 and above. Branch 353 seems to introduce the problem of running WDDM 2.0 when on Win10, which translates into completely broken 3D Vision on Win10 for apparently DX11 games. We know for sure that Witcher3 and FarCry4 are DOA. See Helifax's bug report and DarkStarSword's FC4 page.


@QWinn: With all respect, you are new to 3D Vision, right? I've been working on 3Dmigoto for the past 1.5 years, and using HelixMod for another 1.5 years before that. If you don't think I know what I'm talking about, then I just don't know what to say.

3D Vision is in a precarious state today, it's not well supported, as has not been well supported for over 3 years. As in, NVidia fixes occasional things, but botches others while they do it. And they take *forever* to fix things. Couldn't play 3D Blu Rays for over 10 months. New drivers have broken previous fixes- enough to drive eqzitara away altogether (a former superstar, Helix's right hand man). SLI works, on some games, but not others. SLI is still broken on ROG Swift in 3D. 3D TV Play activation server is offline, for two months.

See: https://forums.geforce.com/default/topic/847809/list-of-3d-vision-problems/


Now here you are, touting the wonders of Win10 and how the future is glorious and clear, after Win10 has been out a whole week. Meanwhile Win10+NVidia is destroying LCD panels in laptops, and is DOA for DX11 games with driver 353.62. (Edit:less clear, only seems to affect a couple of games.)

Now you personally may be willing to pay the price for running Win10, but suggesting that everyone should is absolutely terrible advice.

If you don't care about 3D, that's totally fine, but if you do care about 3D, the fixes run better, are more stable, and have more workarounds on Win7. Anyone who cares about 3D, should be running Win7 for their gaming.

If you have time to burn, running Win 8.1 and Win 10 are OK options, but I promise you that you will have more problems, and need to jack around a lot more with those OSes. ALL of the shaderhackers who make the actual fixes run Win7, that's where they are developed and tested.

Some day Win10 will be the preferred OS and things will be stable, or 3D Vision will be completely dead, one of the two. That day is not today.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#49
Posted 08/12/2015 08:16 AM   
^^ Amen. I mean, I do get the argument that W10 is the way of the future and why waste time making fixes for legacy OS's - BUT - such an idea being a good one is predicated on working drivers and other general features being fully operational in the new OS. Fact is, they aren't. Therefore making fixes for Windows 10 is like putting high-performance tires on a car with a broken engine.
^^ Amen.

I mean, I do get the argument that W10 is the way of the future and why waste time making fixes for legacy OS's - BUT - such an idea being a good one is predicated on working drivers and other general features being fully operational in the new OS. Fact is, they aren't. Therefore making fixes for Windows 10 is like putting high-performance tires on a car with a broken engine.

|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64

#50
Posted 08/12/2015 04:52 PM   
Perhaps we could keep Windows 10 discussion to the main thread for it? That has the benefits of a) not running multiple threads on the same topic b) keeping all information on the topic in one place, should we ever need to refer to it https://forums.geforce.com/default/topic/858123/3d-vision/windows-10-megathread-please-keep-win10-discussions-here/
Perhaps we could keep Windows 10 discussion to the main thread for it? That has the benefits of
a) not running multiple threads on the same topic
b) keeping all information on the topic in one place, should we ever need to refer to it


https://forums.geforce.com/default/topic/858123/3d-vision/windows-10-megathread-please-keep-win10-discussions-here/

#51
Posted 08/13/2015 12:01 AM   
Okay, a few things. First, I thought I had posted in another thread that it makes sense to wait till October/November to really start cracking away at Windows 10 issues, to give MS and Nvidia a chance to fix the issues themselves. Now I can't find the post I thought I'd made, and either way, I should have repeated it in the context of this thread, so sorry about that. I agree today is not "that day". THAT SAID. I decided to find out how broken 3D is on my system. Now please note, bo3b, by your metric I'm about as broken a setup as you can get. 2x980Ti in SLI running on an ROG Swift. Can you think of a less optimal setup at this particular point in time? From the details in your post, I can't. So, I decided to go through my game library and test how 3D worked in more than just the couple of games I'd tried previously. Games that appear to be working very well in True 3D on Windows 10 with 353.62, with NO tweaks of any kind from this forum, pure vanilla, 100% depth: Batman: Arkham Asylum - Gorgeous, although cannot set anti-aliasing to 8XQ option, causes crash. Batman: Arkham City - Frikkin' breathtaking. Portal - Excellent Portal 2 - Not perfect but pretty damn good Van Helsing 1 - Very nice in DX9 mode, broken in DX11 mode Van Helsing 2 - Very nice in DX9 mode, broken in DX11 mode Deus Ex: Human Revolution - everything except the UI working great but required Flugan's hack Dishonored - Not perfect but very nice, tweaking profile would probably get it perfect Fallout New Vegas - Surprisingly working great right now, last time I tried it it was broken The Stanley Parable - Excellent Witcher - Excellent Witcher 2 - Breathtaking Games that are broken on some level: Witcher 3 (really not that bad in compatibility mode, True 3D broken) So this backs up the theory stated previously that the problem is with DX11. Anything that has a DX9 mode runs perfectly well on it, while if the game also has a DX11 mode, it fails, usually spectacularly. But here's the thing. True 3D is working *beautifully* in almost every game I own, without a single hack except for Flugan's hack for Deus Ex, and that may just be necessary because the Director's Cut version apparently isn't recognizing a profile, I don't know if that alone could be responsible for the problem. Other than that, I'm having issues with exactly one game: Witcher 3, which came out recently, and which has been plagued by a whole host of other bugs (at least we got achievements back). And even that game looks decent in compatibility mode, while the true 3D mode we're arguing about is rated "Not Recommended" by NVidia all this while. And yet I was told, by you, that True 3D in Windows 10 was "completely broken". That's complete nonsense. And it betrays a severe animus against Windows 10 that frankly baffles *me*. But let's leave that aside for the moment. Even if it *were* more broken than it is, I still think focus should be on Windows 10 more than it is (again, after October/November and we know what Nvidia will fix and what they won't). Why? Because as you have stated yourself, bo3b, 3D Vision is apparently a niche market. There's fair reasons why. Not everyone can afford the $100 (sale price) for the glasses, let alone a 3D monitor. I wasn't aware at all of the 3D potential until I started shopping a few months ago for my current rig, because I never even thought to buy a monitor for more than $300. And I'm a freakin' game addict and computer geek for over 31 years. If I didn't know about it, sure as hell the average gamer doesn't. But you know what would have deterred *me* instantly from investing in it? Telling me A) You need to invest at least $2k in a system that can really run it well, minimum, and B) you have to roll back to Windows 7. At that point I'd just laugh at you. Okay, so I have to spend thousands of dollars to set up a system which I have to then maintain on an operating system which people can upgrade from *for free*, and is on its way to obsolescence. So what happens when Windows 7 is no longer supported? Will the stuff you want me to spend thousands on to get it working right still work then? Sorry, but I'm not taking that chance. That's the rub of it. The biggest problem we (and you, far longer than I) have had getting support for 3D is that not enough people play it. You ignore Windows 10, by Christmas you will probably be ignoring 80%+ of the PC gamer base in total, and probably even more of the portion of it with equipment that can do 3D properly. If you want to make absolutely sure that 3D Vision stays as obscure niche or abandoned product, ignoring "the last version of Windows" would seem to be the most spectacular way possible to do it. That is all. And I never intended to offend, by the way, bo3b. You asked for opinions, you wanted explanations as to why anyone would want to stay in Windows 10, and I gave them to you. Please don't (again) take it as a personal insult. I know you have been here way longer than me, but I also have "the most brokingest setup possible" for what is being described as "completely broken", and I'm working 99%. That means my experience is pretty damn valuable to the current conversation too, don'tcha think? And incidentally, 3D *is* extremely important to me now. I'm utterly spoiled, and pretty much in a constant state of amazement as I play. I don't think I could ever go back to 2D. So don't think it's because there's something about Windows 10 that is "more important" than 3D. There really isn't. But it simply isn't all that broken, hardly at all in fact, and DirectX 11 being completely broken on Windows 10 is something NVidia will *have* to fix as quickly as they can. Anyway, enough for now, I can think of more to say but I'll see what responses I get to that much before I continue.
Okay, a few things.

First, I thought I had posted in another thread that it makes sense to wait till October/November to really start cracking away at Windows 10 issues, to give MS and Nvidia a chance to fix the issues themselves. Now I can't find the post I thought I'd made, and either way, I should have repeated it in the context of this thread, so sorry about that. I agree today is not "that day".

THAT SAID.

I decided to find out how broken 3D is on my system. Now please note, bo3b, by your metric I'm about as broken a setup as you can get. 2x980Ti in SLI running on an ROG Swift. Can you think of a less optimal setup at this particular point in time? From the details in your post, I can't.

So, I decided to go through my game library and test how 3D worked in more than just the couple of games I'd tried previously.

Games that appear to be working very well in True 3D on Windows 10 with 353.62, with NO tweaks of any kind from this forum, pure vanilla, 100% depth:

Batman: Arkham Asylum - Gorgeous, although cannot set anti-aliasing to 8XQ option, causes crash.
Batman: Arkham City - Frikkin' breathtaking.
Portal - Excellent
Portal 2 - Not perfect but pretty damn good
Van Helsing 1 - Very nice in DX9 mode, broken in DX11 mode
Van Helsing 2 - Very nice in DX9 mode, broken in DX11 mode
Deus Ex: Human Revolution - everything except the UI working great but required Flugan's hack
Dishonored - Not perfect but very nice, tweaking profile would probably get it perfect
Fallout New Vegas - Surprisingly working great right now, last time I tried it it was broken
The Stanley Parable - Excellent
Witcher - Excellent
Witcher 2 - Breathtaking

Games that are broken on some level:
Witcher 3 (really not that bad in compatibility mode, True 3D broken)


So this backs up the theory stated previously that the problem is with DX11. Anything that has a DX9 mode runs perfectly well on it, while if the game also has a DX11 mode, it fails, usually spectacularly.

But here's the thing. True 3D is working *beautifully* in almost every game I own, without a single hack except for Flugan's hack for Deus Ex, and that may just be necessary because the Director's Cut version apparently isn't recognizing a profile, I don't know if that alone could be responsible for the problem. Other than that, I'm having issues with exactly one game: Witcher 3, which came out recently, and which has been plagued by a whole host of other bugs (at least we got achievements back). And even that game looks decent in compatibility mode, while the true 3D mode we're arguing about is rated "Not Recommended" by NVidia all this while.

And yet I was told, by you, that True 3D in Windows 10 was "completely broken".

That's complete nonsense. And it betrays a severe animus against Windows 10 that frankly baffles *me*.

But let's leave that aside for the moment. Even if it *were* more broken than it is, I still think focus should be on Windows 10 more than it is (again, after October/November and we know what Nvidia will fix and what they won't).

Why? Because as you have stated yourself, bo3b, 3D Vision is apparently a niche market. There's fair reasons why. Not everyone can afford the $100 (sale price) for the glasses, let alone a 3D monitor. I wasn't aware at all of the 3D potential until I started shopping a few months ago for my current rig, because I never even thought to buy a monitor for more than $300. And I'm a freakin' game addict and computer geek for over 31 years. If I didn't know about it, sure as hell the average gamer doesn't.

But you know what would have deterred *me* instantly from investing in it? Telling me A) You need to invest at least $2k in a system that can really run it well, minimum, and B) you have to roll back to Windows 7. At that point I'd just laugh at you. Okay, so I have to spend thousands of dollars to set up a system which I have to then maintain on an operating system which people can upgrade from *for free*, and is on its way to obsolescence. So what happens when Windows 7 is no longer supported? Will the stuff you want me to spend thousands on to get it working right still work then? Sorry, but I'm not taking that chance.

That's the rub of it. The biggest problem we (and you, far longer than I) have had getting support for 3D is that not enough people play it. You ignore Windows 10, by Christmas you will probably be ignoring 80%+ of the PC gamer base in total, and probably even more of the portion of it with equipment that can do 3D properly. If you want to make absolutely sure that 3D Vision stays as obscure niche or abandoned product, ignoring "the last version of Windows" would seem to be the most spectacular way possible to do it. That is all.

And I never intended to offend, by the way, bo3b. You asked for opinions, you wanted explanations as to why anyone would want to stay in Windows 10, and I gave them to you. Please don't (again) take it as a personal insult. I know you have been here way longer than me, but I also have "the most brokingest setup possible" for what is being described as "completely broken", and I'm working 99%. That means my experience is pretty damn valuable to the current conversation too, don'tcha think?

And incidentally, 3D *is* extremely important to me now. I'm utterly spoiled, and pretty much in a constant state of amazement as I play. I don't think I could ever go back to 2D. So don't think it's because there's something about Windows 10 that is "more important" than 3D. There really isn't. But it simply isn't all that broken, hardly at all in fact, and DirectX 11 being completely broken on Windows 10 is something NVidia will *have* to fix as quickly as they can.

Anyway, enough for now, I can think of more to say but I'll see what responses I get to that much before I continue.

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#52
Posted 08/13/2015 12:15 AM   
Oh, one odd thing requiring mention: Deus Ex Human Revolution, Director's Cut has an option to "Enable DirectX 11". I've been playing with it *on* this whole time. This is the single exception I have to everything being broken in DX11 mode, and I don't know if Flugan's hack is responsible for it actually working.
Oh, one odd thing requiring mention: Deus Ex Human Revolution, Director's Cut has an option to "Enable DirectX 11". I've been playing with it *on* this whole time. This is the single exception I have to everything being broken in DX11 mode, and I don't know if Flugan's hack is responsible for it actually working.

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#53
Posted 08/13/2015 12:22 AM   
[quote=""]Games that appear to be working very well in True 3D on Windows 10 with 353.62, with NO tweaks of any kind from this forum, pure vanilla, 100% depth: Fallout New Vegas - Surprisingly working great right now, last time I tried it it was broke [/quote] That's odd. Sure you don't have the helix fix still installed somehow? Uninstalling a game through steam usually doesn't delete the fix. The reason I ask is - New Vegas has always had broken skies with 3D vision. Anyway, interesting that's it's working for you under W10. It was broken for me both with and without the helix fix with 353.62 under W10. The right eye image was half black. Makes me wonder if my W10 upgrade screwed up somehow.
said:Games that appear to be working very well in True 3D on Windows 10 with 353.62, with NO tweaks of any kind from this forum, pure vanilla, 100% depth:

Fallout New Vegas - Surprisingly working great right now, last time I tried it it was broke


That's odd. Sure you don't have the helix fix still installed somehow? Uninstalling a game through steam usually doesn't delete the fix. The reason I ask is - New Vegas has always had broken skies with 3D vision.

Anyway, interesting that's it's working for you under W10. It was broken for me both with and without the helix fix with 353.62 under W10. The right eye image was half black. Makes me wonder if my W10 upgrade screwed up somehow.

#54
Posted 08/13/2015 01:54 AM   
Just fired it up to check. The sky doesn't look particularly better than it does in 2D, but I wouldn't call it "broken" in any game breaking way. It's just there. The rest of the environment is very sharp 3D though. I have yet to install Helix mod on anything, haven't really needed it, though the next time I play a game I can afford to tweak (I don't want to mess with Deus Ex right now, given Flugam's patch) I will do so. It is odd, because last weekend I tried F:NV it wasn't working at all. It may be as simple as that I was still stuck in compatibility mode and I since seem to have turned that off / unlocked True 3D mode fully. Give it a try tonight. Maybe some patch got snuck in through Windows 10 Update.
Just fired it up to check. The sky doesn't look particularly better than it does in 2D, but I wouldn't call it "broken" in any game breaking way. It's just there. The rest of the environment is very sharp 3D though.

I have yet to install Helix mod on anything, haven't really needed it, though the next time I play a game I can afford to tweak (I don't want to mess with Deus Ex right now, given Flugam's patch) I will do so.

It is odd, because last weekend I tried F:NV it wasn't working at all. It may be as simple as that I was still stuck in compatibility mode and I since seem to have turned that off / unlocked True 3D mode fully.

Give it a try tonight. Maybe some patch got snuck in through Windows 10 Update.

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#55
Posted 08/13/2015 02:32 AM   
There's no reason that anyone that wants to run Windows 10 couldn't and shouldn't use it. What's being said is that efforts for fixes currently, are going to remain focused on the Windows 7 platform, At least until the dust settles on W10 and NVidia's drivers. So if you want to use community fixes, it would be wise to remain with Windows 7 for compatibility reasons for the time being. There are what, four or five different version of the dx9 for W7 wrapper made by Helix. Each one only works with certain games. Who exactly is going to update those wrappers to W10 compatibility? Helix is out of the picture. Chiri's 3Dmigoto is ever evolving for dx11 games, but resources are limited to a few gifted individuals of the community. The brunt of the work and coding is done by bo3b, who took over the project after Chiri stepped aside. If bo3b say's to avoid W10 for the time being, any avid 3D gamer would heed his advice.
There's no reason that anyone that wants to run Windows 10 couldn't and shouldn't use it.

What's being said is that efforts for fixes currently, are going to remain focused on the Windows 7 platform, At least until the dust settles on W10 and NVidia's drivers.

So if you want to use community fixes, it would be wise to remain with Windows 7 for compatibility reasons for the time being.

There are what, four or five different version of the dx9 for W7 wrapper made by Helix. Each one only works with certain games. Who exactly is going to update those wrappers to W10 compatibility? Helix is out of the picture.

Chiri's 3Dmigoto is ever evolving for dx11 games, but resources are limited to a few gifted individuals of the community. The brunt of the work and coding is done by bo3b, who took over the project after Chiri stepped aside. If bo3b say's to avoid W10 for the time being, any avid 3D gamer would heed his advice.

#56
Posted 08/13/2015 03:01 AM   
Just to experiment, I installed the Helixmod shaderfix file for Fallout New Vegas, and it's impressive. I do like it better, and will leave it installed. And yeah, the sky does look better. I see the fix also attempts to tweak the PIP-BOY, but I didn't really see any difference, it looked great both before and after.
Just to experiment, I installed the Helixmod shaderfix file for Fallout New Vegas, and it's impressive. I do like it better, and will leave it installed. And yeah, the sky does look better. I see the fix also attempts to tweak the PIP-BOY, but I didn't really see any difference, it looked great both before and after.

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#57
Posted 08/13/2015 03:02 AM   
"What's being said is that efforts for fixes currently, are going to remain focused on the Windows 7 platform, At least until the dust settles on W10 and NVidia's drivers." That's perfectly fair. As I said, I wouldn't bother working on Windows 10 stuff for a couple months just to let the official fixes get put in place. That makes perfect sense, and if that's all that was meant, I'm sorry if I seemed argumentative. I just had the impression that Windows 10 was going to be ignored long term, which I think would be a mistake, as a lot of people will be on it and the best way to get 3D to thrive will be to keep it open to as many players as possible. That's all. Sorry if I hurt any feelings or offended anyone in any way. And bo3b, the work you do here is definitely top notch and very appreciated. Thanks for all your help so far. And when I get some time I will look into your shaderhack tutorial thread. Maybe I can lend a hand at some point down the line. I've been coding since I was 11 (am 45 now), though never with graphical stuff, but never too late to start.
"What's being said is that efforts for fixes currently, are going to remain focused on the Windows 7 platform, At least until the dust settles on W10 and NVidia's drivers."

That's perfectly fair. As I said, I wouldn't bother working on Windows 10 stuff for a couple months just to let the official fixes get put in place. That makes perfect sense, and if that's all that was meant, I'm sorry if I seemed argumentative. I just had the impression that Windows 10 was going to be ignored long term, which I think would be a mistake, as a lot of people will be on it and the best way to get 3D to thrive will be to keep it open to as many players as possible. That's all. Sorry if I hurt any feelings or offended anyone in any way. And bo3b, the work you do here is definitely top notch and very appreciated. Thanks for all your help so far.

And when I get some time I will look into your shaderhack tutorial thread. Maybe I can lend a hand at some point down the line. I've been coding since I was 11 (am 45 now), though never with graphical stuff, but never too late to start.

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#58
Posted 08/13/2015 03:33 AM   
My main concern with Windows 10 is legacy issues from windows 8.1 and being restricted to drivers that have issues with alot of configurations and games at this point. This may be more in nvidia's court so hopefully they are getting their act together.
My main concern with Windows 10 is legacy issues from windows 8.1 and being restricted to drivers that have issues with alot of configurations and games at this point.

This may be more in nvidia's court so hopefully they are getting their act together.

i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
EVGA 1080TI SLI
Samsung SSD 840Pro
ASUS Z97-WS
3D Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)

#59
Posted 08/13/2015 05:06 AM   
The key words there are "at least". I do not speak for them nor do I do any of the work on the wrappers. But I do know that Windows 8 was a mess. Windows 8.1 was a little better, but still suffered compatibility issues with the wrappers. Even though dx11 was supposed to add native support for gaming and video, it was poorly implemented and not widely used by developers. If Microsoft and developers would have embraced it, this would be a non-issue. So only time will tell what happens with Windows 10/dx11/dx12 in regards to support for stereoscopic gaming from Microsoft, Developers, Nvidia and our community.
The key words there are "at least".

I do not speak for them nor do I do any of the work on the wrappers.

But I do know that Windows 8 was a mess.

Windows 8.1 was a little better, but still suffered compatibility issues with the wrappers.

Even though dx11 was supposed to add native support for gaming and video, it was poorly implemented and not widely used by developers. If Microsoft and developers would have embraced it, this would be a non-issue.

So only time will tell what happens with Windows 10/dx11/dx12 in regards to support for stereoscopic gaming from Microsoft, Developers, Nvidia and our community.

#60
Posted 08/13/2015 06:37 AM   
  4 / 6    
Scroll To Top