3D Vision @ Windows 10
  5 / 6    
I'm personally hoping that the impending "VR revolution" will push 3D back into the mainstream and with it bring a whole new raft of support. Even if games aren't being developed with 3D Vision specifically in mind, if they're coding to cater for the numerous VR headsets then we should at least have the basics of stereoscopy in there which will hopefully make any required 3D Vision conversion easier? Maybe bo3b will correct me on this - he obviously knows considerably better than I - but I live in hope...
I'm personally hoping that the impending "VR revolution" will push 3D back into the mainstream and with it bring a whole new raft of support. Even if games aren't being developed with 3D Vision specifically in mind, if they're coding to cater for the numerous VR headsets then we should at least have the basics of stereoscopy in there which will hopefully make any required 3D Vision conversion easier? Maybe bo3b will correct me on this - he obviously knows considerably better than I - but I live in hope...

i7 5930k @ 4.5GHz
Asus Sabertooth X99 Motherboard
2 x EVGA GTX 980 Ti SC @ 1380MHz/7.5GHz
Twin loop, triple rad water cooled
16GB Kingston Predator 3GHz

256GB Samsung XP941 M.2 SSD (OS)
2 x 256GB SSD RAID0 (Games)
2 x 2TB Mechanical (storage)

Asus ROG Swift PG278Q 1440p/144MHz 3D/G-sync monitor
Avermedia ExtremeCap U3 Video Capture for PS4 passthrough
Phanteks Enthoo Primo Gold case

Dual Boot OS Windows 8.1/Windows 10

#61
Posted 08/13/2015 09:03 AM   
Hey guys, mind shifting the discussion to the main Windows 10 thread, to keep it all together? https://forums.geforce.com/default/topic/858123/windows-10-megathread-please-keep-win10-discussions-here/
Hey guys, mind shifting the discussion to the main Windows 10 thread, to keep it all together?


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

#62
Posted 08/13/2015 09:58 AM   
[quote="Qwinn"]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. [/quote] Yeah you must have been in compatibility mode. When I say the sky is broken without the fix, it's at screen depth and very unpleasant to look at. It looks closer than the surrounding scenery.
Qwinn said: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.

Yeah you must have been in compatibility mode. When I say the sky is broken without the fix, it's at screen depth and very unpleasant to look at. It looks closer than the surrounding scenery.

#63
Posted 08/13/2015 04:39 PM   
Sorry PirateGuyBrush, this conversation is still ongoing here, and it's even more weird to jump threads for a response. [quote=Qwinn]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*.[/quote] Looks like we are actually talking about two different things here, maybe 3. All named 3D. It's not animus against Win10, it's looking for the best possible experience. Best experience also includes less jacking around and more gaming. I swear I actually hate the world now because a lack of enthusiasm is now considered hate. I blame Apple. Your experience with definitely a sub-optimal setup is not shared by other people. You are mostly looking at games that have native support like Deus Ex and Batman, or CM/fake-3D. Everyone is different, some people find it acceptable, some don't. Generally speaking anyone who has the option of a true-3D fix will use it as being vastly better if only because convergence is not pinned. There is also a fantastic shock value to seeing 3D in the first place, which of course wanes over time. As a new person, you will be willing to accept a lower quality threshold than the old timers. I was the same way. When I first played Dead Space in 3D, I was completely blown away. And that was with broken shadows. I played the entire game using the gimmick of pulling the convergence out far enough so that shadows would lie at screen depth. And it was awesome. Now with the Helix fix for it, that game is 5x better than even that experience. My 3D is all about true-3D fixes, and I don't hate CM, but I will only use it if there is simply no other option. These are the fixes on HelixModBlog. We do a better job than CM, and better than NVidia. When people talk about 3D on this board, this is mainly what they mean. The third 3D we are obliquely mentioning is 3D Vision Automatic, which is what makes all this possible in the first place. (CM uses a different technique). 3D Vision Automatic is the 3D Driver that makes two views possible, and [s]is in fact completely broken on Win10+353.63. That means that not only is 3D broken in games- it means we can't fix them. That is serious and new. NVidia has been dropping the ball everywhere recently, so if they don't get around to fixing this, that will mean the future is closed off to us. [/s] That doesn't change today. Today the experience is pretty great, and still worth using, as long as you aren't stuck with the latest drivers. It's getting a little worse every day that the drivers are broken, but it's still got plenty of amazing fun to be had. The future is still presently hazy, so I don't think anyone can suggest 3D without some caveats. As shaderhackers we simultaneously have awesome power and no power at the same time. We don't have to simply rely upon the meager scraps thrown us by NVidia and game devs, we can actually make our own fixes and forge our own experiences. That is huge. The bad part is that we are still dependent upon NVidia for 3D Vision Automatic, and there isn't anything we can do about that just yet. (we can possibly use Vireio) It's very hard to even guess what will happen. We know NVidia is actively working on fixing the problems, but we also know they have a poor track record. I think it's anyone's guess, and since there's nothing we can do about it anyway, we just have to wait. [quote=""]I'm personally hoping that the impending "VR revolution" will push 3D back into the mainstream and with it bring a whole new raft of support. Even if games aren't being developed with 3D Vision specifically in mind, if they're coding to cater for the numerous VR headsets then we should at least have the basics of stereoscopy in there which will hopefully make any required 3D Vision conversion easier? Maybe bo3b will correct me on this - he obviously knows considerably better than I - but I live in hope...[/quote] This is entirely possible, and if VR kicks off and becomes THE thing, we can definitely make a wrapper that would bring VR games to 3D Vision hardware using the nvapi. That would not require 3D Vision Automatic, because the game is built for 3D to begin with. Another possible game-changer is auto-stereoscopic displays. If these get more traction and improve just a bit more, that opens up the door to a lot more gamers who simply won't use shutter glasses. The next 6 months will be particularly interesting.
Sorry PirateGuyBrush, this conversation is still ongoing here, and it's even more weird to jump threads for a response.

Qwinn said: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*.

Looks like we are actually talking about two different things here, maybe 3. All named 3D.

It's not animus against Win10, it's looking for the best possible experience. Best experience also includes less jacking around and more gaming. I swear I actually hate the world now because a lack of enthusiasm is now considered hate. I blame Apple.


Your experience with definitely a sub-optimal setup is not shared by other people. You are mostly looking at games that have native support like Deus Ex and Batman, or CM/fake-3D. Everyone is different, some people find it acceptable, some don't. Generally speaking anyone who has the option of a true-3D fix will use it as being vastly better if only because convergence is not pinned.

There is also a fantastic shock value to seeing 3D in the first place, which of course wanes over time. As a new person, you will be willing to accept a lower quality threshold than the old timers. I was the same way. When I first played Dead Space in 3D, I was completely blown away. And that was with broken shadows. I played the entire game using the gimmick of pulling the convergence out far enough so that shadows would lie at screen depth. And it was awesome. Now with the Helix fix for it, that game is 5x better than even that experience.


My 3D is all about true-3D fixes, and I don't hate CM, but I will only use it if there is simply no other option. These are the fixes on HelixModBlog. We do a better job than CM, and better than NVidia. When people talk about 3D on this board, this is mainly what they mean.


The third 3D we are obliquely mentioning is 3D Vision Automatic, which is what makes all this possible in the first place. (CM uses a different technique). 3D Vision Automatic is the 3D Driver that makes two views possible, and is in fact completely broken on Win10+353.63. That means that not only is 3D broken in games- it means we can't fix them. That is serious and new. NVidia has been dropping the ball everywhere recently, so if they don't get around to fixing this, that will mean the future is closed off to us.


That doesn't change today. Today the experience is pretty great, and still worth using, as long as you aren't stuck with the latest drivers. It's getting a little worse every day that the drivers are broken, but it's still got plenty of amazing fun to be had.

The future is still presently hazy, so I don't think anyone can suggest 3D without some caveats.

As shaderhackers we simultaneously have awesome power and no power at the same time. We don't have to simply rely upon the meager scraps thrown us by NVidia and game devs, we can actually make our own fixes and forge our own experiences. That is huge. The bad part is that we are still dependent upon NVidia for 3D Vision Automatic, and there isn't anything we can do about that just yet. (we can possibly use Vireio)

It's very hard to even guess what will happen. We know NVidia is actively working on fixing the problems, but we also know they have a poor track record. I think it's anyone's guess, and since there's nothing we can do about it anyway, we just have to wait.


said:I'm personally hoping that the impending "VR revolution" will push 3D back into the mainstream and with it bring a whole new raft of support. Even if games aren't being developed with 3D Vision specifically in mind, if they're coding to cater for the numerous VR headsets then we should at least have the basics of stereoscopy in there which will hopefully make any required 3D Vision conversion easier? Maybe bo3b will correct me on this - he obviously knows considerably better than I - but I live in hope...

This is entirely possible, and if VR kicks off and becomes THE thing, we can definitely make a wrapper that would bring VR games to 3D Vision hardware using the nvapi. That would not require 3D Vision Automatic, because the game is built for 3D to begin with.

Another possible game-changer is auto-stereoscopic displays. If these get more traction and improve just a bit more, that opens up the door to a lot more gamers who simply won't use shutter glasses.

The next 6 months will be particularly interesting.

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

#64
Posted 08/14/2015 03:53 AM   
Not seeing 3d in the NVidia control panel on 355.60. What gives?
Not seeing 3d in the NVidia control panel on 355.60. What gives?

#65
Posted 08/14/2015 04:46 AM   
bo3b, that was a very interesting read. Thanks. However, I'm puzzled by this: "3D Vision Automatic is the 3D Driver that makes two views possible, and is in fact completely broken on Win10+353.63." The impression I get is that "3D Vision Automatic" is the foundation that you guys build on, and that you can't touch (essentially, the engine... I know a little something about that from when I did my Planescape: Torment Fixpack). But if that is completely broken, why is almost everything working fine for me? Are you just referring to DirectX 11 at this point? Oh, one other thing: "You are mostly looking at games that have native support like Deus Ex and Batman, or CM/fake-3D." I don't think any of the ones I listed are running CM/fake-3D. I think I've grasped by now how to tell the difference. Maybe I'm wrong though. But none of them actually say Compatibility Mode On when I play them, except for Witcher 3. I can also add Dragon Age: Origins and L.A. Noire to the list of games that are working absolutely beautifully in real 3D. EDIT: For the record, just downloaded and installed the latest driver. No issues or negative side effects yet, though minimal testing so far. Will report if I have any issues tomorrow night.
bo3b, that was a very interesting read. Thanks. However, I'm puzzled by this:

"3D Vision Automatic is the 3D Driver that makes two views possible, and is in fact completely broken on Win10+353.63."

The impression I get is that "3D Vision Automatic" is the foundation that you guys build on, and that you can't touch (essentially, the engine... I know a little something about that from when I did my Planescape: Torment Fixpack). But if that is completely broken, why is almost everything working fine for me? Are you just referring to DirectX 11 at this point?

Oh, one other thing:

"You are mostly looking at games that have native support like Deus Ex and Batman, or CM/fake-3D."

I don't think any of the ones I listed are running CM/fake-3D. I think I've grasped by now how to tell the difference. Maybe I'm wrong though. But none of them actually say Compatibility Mode On when I play them, except for Witcher 3.

I can also add Dragon Age: Origins and L.A. Noire to the list of games that are working absolutely beautifully in real 3D.

EDIT: For the record, just downloaded and installed the latest driver. No issues or negative side effects yet, though minimal testing so far. Will report if I have any issues tomorrow night.

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

#66
Posted 08/14/2015 04:53 AM   
@kev11106 - Try reinstalling the driver, it's working for me. @bo3b - I'm also interested in what you mean by "completely broken"? I played about half of Valiant Hearts under Win10 with no issues, and everything else I've tested has been on par with Windows 8, excluding Witcher 3. That includes multiple DX11 titles, and titles that use 3D Migoto and Helixmod fixes.
@kev11106 - Try reinstalling the driver, it's working for me.

@bo3b - I'm also interested in what you mean by "completely broken"? I played about half of Valiant Hearts under Win10 with no issues, and everything else I've tested has been on par with Windows 8, excluding Witcher 3. That includes multiple DX11 titles, and titles that use 3D Migoto and Helixmod fixes.

#67
Posted 08/14/2015 07:28 AM   
Under Win10 3D VIsion Automatic is not "completely" broken... just more broken than Windows 7/8 version of the drivers... The only game where 3D Vision Automatic FAILS is The Witcher 3. Funny is working in CM mode WITH my profile. Default profile just gives a 2D Image:)) Besides this the Switching from 3D to 2D is there (Is also present in Win7/8 so nothing really new). So, broken: Yes. Completely broken: No. Win10 has other issues especially with SLI and Frostbyte engines... At least my experience;)
Under Win10 3D VIsion Automatic is not "completely" broken... just more broken than Windows 7/8 version of the drivers...

The only game where 3D Vision Automatic FAILS is The Witcher 3. Funny is working in CM mode WITH my profile. Default profile just gives a 2D Image:))

Besides this the Switching from 3D to 2D is there (Is also present in Win7/8 so nothing really new).

So, broken: Yes. Completely broken: No. Win10 has other issues especially with SLI and Frostbyte engines...
At least my experience;)

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#68
Posted 08/14/2015 08:50 AM   
OK, sounds like I'm confused on what is actually broken. Taking the sort of worst case scenario of 980ti+353.65+Win10 where you can't roll back, is the only game actually broken Witcher3? Any others? Helifax, can you fill me in on your finding with WDDM 2.0? That's the spot I'm the most concerned about, and it sounds like I misunderstood.
OK, sounds like I'm confused on what is actually broken.

Taking the sort of worst case scenario of 980ti+353.65+Win10 where you can't roll back, is the only game actually broken Witcher3? Any others?


Helifax, can you fill me in on your finding with WDDM 2.0? That's the spot I'm the most concerned about, and it sounds like I misunderstood.

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

#69
Posted 08/14/2015 11:38 PM   
In Windows 7 the WDDM was via Windows Update. I imagine that it's included in the W10 OS. Just stating this, because I recall Helifax saying that he shied away from installing updates. Perhaps WDDM 2.0 isn't the problem, but it's an update that you installed and Helifax didn't?
In Windows 7 the WDDM was via Windows Update.

I imagine that it's included in the W10 OS.

Just stating this, because I recall Helifax saying that he shied away from installing updates.

Perhaps WDDM 2.0 isn't the problem, but it's an update that you installed and Helifax didn't?

#70
Posted 08/15/2015 12:12 AM   
Witcher 3 is the only broken game I've encountered so far with SLI (or single) 970 + 355.60 + Win10. This afternoon I'm going to play some Lords of The Fallen, so I'll do that under Win10 to see how it goes.
Witcher 3 is the only broken game I've encountered so far with SLI (or single) 970 + 355.60 + Win10.

This afternoon I'm going to play some Lords of The Fallen, so I'll do that under Win10 to see how it goes.

#71
Posted 08/15/2015 09:05 AM   
@bo3b: Regarding the WDDM 1.3 vs 2.0. On my RAID SSD array I intalled Win10 Pro(clean). Bought another SSD on which I installed Win7 (clean) with all the freaking updates (took 1 day to make all the updates -_-) So: After you install the Nvidia Drivers 355.60 for example (both Win10 and Win7) run dxDiag. Under Display tab it will specify what version of WDDM is supported/ the driver works as well as DX levels and so on. On Windows 10 : is WDDM 2.0 On Windows 7 : is WDDM 1.1 On Windows 8.1 : is WDDM 1.3 Now repeat the same with drivers 350.12. On Windows 10 : is WDDM 1.3 On Windows 8.1 : is WDDM 1.3 On Windows 7 : is WDDM 1.1 Fascinating how on Win10 only 350.12 give proper 3D in Witcher 3 which happen to work on WDDM 1.3 like on other windows version. What is interesting is that 355.60 on Windows 7/8.1 and Witcher 3 are still rendering correct! So based on this observation I can draw the following conclusion: Using the WDDM 2.0 Driver Model breaks something related to 3D Vision Automatic. Furthermore, BF4 and DAI have problems with SLI and VRAM memory leak while on Windows 7 (same driver 355.60) the problem doesn't exist! Again the only difference that I can see is the WDDM. Now this could be a placebo effect and I am imagining things but I don't think so, since the WDDM Model dictates how drivers are interacting with the below hardware/OS Kernel etc. What is more fascinating is that Windows 10 SUPPORTS WDDM 1.3 & 2.0 BUT... I could not make the 355.60 drivers install under WDDM 1.3 Model no matter what I tried... I believe that if we manage somehow to install them under 1.3 Model, the Witcher 3 and Memory leak issues will go away...(until/if Nvidia fixes them). I haven't researched in-depth on what exactly the new WDDM Model changes, but based on a preliminary inspection, it handles the functionality of GPUs access and memory control, so it might explain why the results are what we currently see when using them in WDDM 2.0. This is my discovery so far;)
@bo3b:

Regarding the WDDM 1.3 vs 2.0.
On my RAID SSD array I intalled Win10 Pro(clean).
Bought another SSD on which I installed Win7 (clean) with all the freaking updates (took 1 day to make all the updates -_-)

So: After you install the Nvidia Drivers 355.60 for example (both Win10 and Win7) run dxDiag. Under Display tab it will specify what version of WDDM is supported/ the driver works as well as DX levels and so on.
On Windows 10 : is WDDM 2.0
On Windows 7 : is WDDM 1.1
On Windows 8.1 : is WDDM 1.3

Now repeat the same with drivers 350.12.
On Windows 10 : is WDDM 1.3
On Windows 8.1 : is WDDM 1.3
On Windows 7 : is WDDM 1.1

Fascinating how on Win10 only 350.12 give proper 3D in Witcher 3 which happen to work on WDDM 1.3 like on other windows version.

What is interesting is that 355.60 on Windows 7/8.1 and Witcher 3 are still rendering correct! So based on this observation I can draw the following conclusion: Using the WDDM 2.0 Driver Model breaks something related to 3D Vision Automatic.

Furthermore, BF4 and DAI have problems with SLI and VRAM memory leak while on Windows 7 (same driver 355.60) the problem doesn't exist! Again the only difference that I can see is the WDDM.

Now this could be a placebo effect and I am imagining things but I don't think so, since the WDDM Model dictates how drivers are interacting with the below hardware/OS Kernel etc.

What is more fascinating is that Windows 10 SUPPORTS WDDM 1.3 & 2.0 BUT... I could not make the 355.60 drivers install under WDDM 1.3 Model no matter what I tried...

I believe that if we manage somehow to install them under 1.3 Model, the Witcher 3 and Memory leak issues will go away...(until/if Nvidia fixes them). I haven't researched in-depth on what exactly the new WDDM Model changes, but based on a preliminary inspection, it handles the functionality of GPUs access and memory control, so it might explain why the results are what we currently see when using them in WDDM 2.0.

This is my discovery so far;)

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#72
Posted 08/15/2015 10:01 AM   
Lords of The Fallen has issues under 355.60 on both Win8 and Win10, just as a data point. Broken AO, and SLI doesn't appear to be working.
Lords of The Fallen has issues under 355.60 on both Win8 and Win10, just as a data point. Broken AO, and SLI doesn't appear to be working.

#73
Posted 08/15/2015 10:24 AM   
[quote="helifax"]Bought another SSD on which I installed Win7 (clean) with all the freaking updates (took 1 day to make all the updates -_-)[/quote] One update that you might have wanted to avoid installing is 2952664. It's the compatibility update for Windows 7 to update to Windows 10. It installs a whole bunch of unnecessary DLLs that may interfere with fixes. https://support.microsoft.com/en-us/kb/2952664 EDIT: zig11727 posted an update for W8 that people will want to avoid. [quote="zig11727"]Also there is the KB3035583 update to get Windows 10 for Windows 8.1 which is hard as hell to remove it took me hours.[/quote]
helifax said:Bought another SSD on which I installed Win7 (clean) with all the freaking updates (took 1 day to make all the updates -_-)


One update that you might have wanted to avoid installing is 2952664.

It's the compatibility update for Windows 7 to update to Windows 10.

It installs a whole bunch of unnecessary DLLs that may interfere with fixes.

https://support.microsoft.com/en-us/kb/2952664

EDIT: zig11727 posted an update for W8 that people will want to avoid.

zig11727 said:Also there is the KB3035583 update to get Windows 10 for Windows 8.1 which is hard as hell to remove it took me hours.

#74
Posted 08/15/2015 11:35 AM   
[quote=""]Lords of The Fallen has issues under 355.60 on both Win8 and Win10, just as a data point. Broken AO, and SLI doesn't appear to be working.[/quote] Weird... I just tested it under Win10/7 with 355.60 and is working for me exactly as before. I don't see halos. I did see the wrong AO which I was able to "re-sync" by Alt+tabbing out/in the game once. If you feel up to it you can also try this and see if it fixes the problem? (I know it sounds stupid but I noticed that by default it starts in CM mode. Be sure it is disabled (I didn't notice it was enabled the first minute)).
said:Lords of The Fallen has issues under 355.60 on both Win8 and Win10, just as a data point. Broken AO, and SLI doesn't appear to be working.


Weird... I just tested it under Win10/7 with 355.60 and is working for me exactly as before. I don't see halos.
I did see the wrong AO which I was able to "re-sync" by Alt+tabbing out/in the game once.

If you feel up to it you can also try this and see if it fixes the problem?
(I know it sounds stupid but I noticed that by default it starts in CM mode. Be sure it is disabled (I didn't notice it was enabled the first minute)).

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#75
Posted 08/15/2015 12:17 PM   
  5 / 6    
Scroll To Top