Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)
Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)
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
[quote="helifax"]Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)[/quote]
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you
helifax said:Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you
[quote="clod21a"][quote="helifax"]Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)[/quote]
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you[/quote]
Cool,
I am not responsible for any other versions posted here, except the ones on the main page:)
helifax said:Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you
Cool,
I am not responsible for any other versions posted here, except the ones on the main page:)
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
[quote="clod21a"][quote="helifax"]Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)[/quote]
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you[/quote]
I cant confirm this, 0.63 is working fine, may you forgot to enable prerendered frames 1 or did something other fault.
helifax said:Version 0.61 works perfectly fine on the latest patch 1.10.
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you
I cant confirm this, 0.63 is working fine, may you forgot to enable prerendered frames 1 or did something other fault.
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
So apparently StereoFlagsDX10 values ranging from 0x0000C000 to 0x0000F000 prevent the CS lights from disappearing but this introduces other issues and of course the recent fixes need some tweaks to work with these flags. Also I think the higher values may possibly affect (or fix?) some other things as well as have a bigger performance impact in some areas. The screenshot was taken plainly without 3DMigoto.
I hope Helifax still has the nerves to go through this game again and come out on top with an excellent if not perfect fix :]
So apparently StereoFlagsDX10 values ranging from 0x0000C000 to 0x0000F000 prevent the CS lights from disappearing but this introduces other issues and of course the recent fixes need some tweaks to work with these flags. Also I think the higher values may possibly affect (or fix?) some other things as well as have a bigger performance impact in some areas. The screenshot was taken plainly without 3DMigoto.
I hope Helifax still has the nerves to go through this game again and come out on top with an excellent if not perfect fix :]
@Kaimasta great to see someone else experimenting with the profiles :)
I would ask that you please add your observations to this page (the performance impact is a worthwhile observation even if it doesn't seem like much):
http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings
(The anti-spambot answer is Helix of course ;-)
StereoFlagsDX10 = 0x0000C000 is one we know thanks to prior experimentation and some documentation nvidia provided - that's STEREO_COMPUTE_ENABLE + STEREO_COMPUTE_SAME_RESOURCES_AS_GRAPHICS.
I think some worthwhile experiments to try would be to take a look at the games I've noted under "known values" and see what breaks if you disable those flags.
Also, I recently discovered that having compatibility mode in a profile changes some of the other flags, even outside of CM, e.g. StereoFlagsDX10 = 0x00000008 is always enabled for CM profiles. I know that other flags must be set based on my experiments removing CM from the Far Cry Primal profile, but I haven't gone through to work out which.
StereoFlagsDX10 = 0x0000C000 is one we know thanks to prior experimentation and some documentation nvidia provided - that's STEREO_COMPUTE_ENABLE + STEREO_COMPUTE_SAME_RESOURCES_AS_GRAPHICS.
I think some worthwhile experiments to try would be to take a look at the games I've noted under "known values" and see what breaks if you disable those flags.
Also, I recently discovered that having compatibility mode in a profile changes some of the other flags, even outside of CM, e.g. StereoFlagsDX10 = 0x00000008 is always enabled for CM profiles. I know that other flags must be set based on my experiments removing CM from the Far Cry Primal profile, but I haven't gone through to work out which.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Did some quick tests and as it can be seen some values have a minor FPS impact depending on the location but this may not be the case in other games or on other GPUs so it definitely needs more testing.
Settings were maxed on my gtx 970 apart from anti-aliasing which was set on FXAA and ambient occlusion set on SSAO (screenshot was taken with the same settings). As for graphical differences I can't really say except that CS lights are fixed when using higher values so I'll leave that to Helifax since he knows the game better.
Indoor starting area:
0x00004000: 30-40 fps
0x00005000: 28-39 fps
0x00006000: 30-40 fps
0x00007000: 28-39 fps
0x0000C000: 30-45 fps
0x0000D000: 30-44 fps
0x0000E000: 29-44 fps
0x0000F000: 30-44 fps
Outdoor on the first planet:
0x00004000: 25-32 fps
0x00005000: 22-28 fps
0x00006000: 25-32 fps
0x00007000: 22-28 fps
0x0000C000: 26-34 fps
0x0000D000: 24-30 fps
0x0000E000: 26-34 fps
0x0000F000: 23-29 fps
Did some quick tests and as it can be seen some values have a minor FPS impact depending on the location but this may not be the case in other games or on other GPUs so it definitely needs more testing.
Settings were maxed on my gtx 970 apart from anti-aliasing which was set on FXAA and ambient occlusion set on SSAO (screenshot was taken with the same settings). As for graphical differences I can't really say except that CS lights are fixed when using higher values so I'll leave that to Helifax since he knows the game better.
nice find Kaimasta!!!
Just test and it's true CS Lights are fixed (without 3D Migoto runing), almost 90-95% of them, and get more performance...BUT this just add some pixels arround the character with some ligts. Minor problem i think. Hope DSS / Helifax take a look some day.
I remind you that the game is shared in the ORIGIN account for Shaderhackers...
I will donate some money (at the end of this month) for help DSS/Helifax and thank them all the hard work that are they doing for this community.
Just test and it's true CS Lights are fixed (without 3D Migoto runing), almost 90-95% of them, and get more performance...BUT this just add some pixels arround the character with some ligts. Minor problem i think. Hope DSS / Helifax take a look some day.
I remind you that the game is shared in the ORIGIN account for Shaderhackers...
I will donate some money (at the end of this month) for help DSS/Helifax and thank them all the hard work that are they doing for this community.
i7 4970k@4.5Ghz, SLI GTX1080Ti Aorus Gigabyte Xtreme, 16GB G Skill 2400hrz, 3*PG258Q in 3D surround.
Awesome find there!
[s]I will eventually give this fix another look, in the light of the new discovery:) I don't have an ETA on it though...[/s]
Actually, no.. I am not going to revisit this. If I do, it will not be released publicly, for reasons.
I will eventually give this fix another look, in the light of the new discovery:) I don't have an ETA on it though...
Actually, no.. I am not going to revisit this. If I do, it will not be released publicly, for reasons.
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
[quote="Kaimasta"]Did some quick tests and as it can be seen some values have a minor FPS impact depending on the location but this may not be the case in other games or on other GPUs so it definitely needs more testing.[/quote]
Thanks for that - I've added a summary of those results on the wiki (and feel free to sign up for an account so you can directly edit the page). My take on your results is that STEREO_COMPUTE_SAME_RESOURCES_AS_GRAPHICS regains up to 5fps of the performance lost with STEREO_COMPUTE_ENABLE on single GPU (which makes sense, since some compute shaders will then only be run once), and whatever 0x00001000 is has an additional performance cost of up to 5fps.
Kaimasta said:Did some quick tests and as it can be seen some values have a minor FPS impact depending on the location but this may not be the case in other games or on other GPUs so it definitely needs more testing.
Thanks for that - I've added a summary of those results on the wiki (and feel free to sign up for an account so you can directly edit the page). My take on your results is that STEREO_COMPUTE_SAME_RESOURCES_AS_GRAPHICS regains up to 5fps of the performance lost with STEREO_COMPUTE_ENABLE on single GPU (which makes sense, since some compute shaders will then only be run once), and whatever 0x00001000 is has an additional performance cost of up to 5fps.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
[quote="Helifax"]Awesome find there!
[s]I will eventually give this fix another look, in the light of the new discovery:) I don't have an ETA on it though...[/s]
Actually, no.. I am not going to revisit this. If I do, it will not be released publicly, for reasons.[/quote]
:_____(
as I said in the other post...i hope that you change your mind.., and if we can do something about, please count on us!!
Anyway THANK you for all your incredible work that you have given us all these years.
Hey Helifax
Can I ask why you won't be releasing any potential future fix to this publicly?
You are certainly within your full right not to, I'm just curious and trying to understand. Would assume it has something to do with people wanting too much and giving too little, but I don't know ofc.
And feel free to tell me to bugger off or just say nothing if indeed "Reasons" are as much information as you're willing to divulge :D
Can I ask why you won't be releasing any potential future fix to this publicly?
You are certainly within your full right not to, I'm just curious and trying to understand. Would assume it has something to do with people wanting too much and giving too little, but I don't know ofc.
And feel free to tell me to bugger off or just say nothing if indeed "Reasons" are as much information as you're willing to divulge :D
.
Helifax says, it's too much time spent in small fixes that won't work on all rig... To make it works on each rig it a +50% extra time, this time will be put through other games.
Helifax says, it's too much time spent in small fixes that won't work on all rig... To make it works on each rig it a +50% extra time, this time will be put through other games.
With 1.09 worked
thank you
The problem is that you must probably apply the workaround from the first video (even in SLI + Windows 10 now...)
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)
I had installed version 0.63
Now try with 0.61 I have to install the game again
thank you
Cool,
I am not responsible for any other versions posted here, except the ones on the main page:)
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)
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
I cant confirm this, 0.63 is working fine, may you forgot to enable prerendered frames 1 or did something other fault.
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
I hope Helifax still has the nerves to go through this game again and come out on top with an excellent if not perfect fix :]
I would ask that you please add your observations to this page (the performance impact is a worthwhile observation even if it doesn't seem like much):
http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings
(The anti-spambot answer is Helix of course ;-)
StereoFlagsDX10 = 0x0000C000 is one we know thanks to prior experimentation and some documentation nvidia provided - that's STEREO_COMPUTE_ENABLE + STEREO_COMPUTE_SAME_RESOURCES_AS_GRAPHICS.
I think some worthwhile experiments to try would be to take a look at the games I've noted under "known values" and see what breaks if you disable those flags.
Also, I recently discovered that having compatibility mode in a profile changes some of the other flags, even outside of CM, e.g. StereoFlagsDX10 = 0x00000008 is always enabled for CM profiles. I know that other flags must be set based on my experiments removing CM from the Far Cry Primal profile, but I haven't gone through to work out which.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Settings were maxed on my gtx 970 apart from anti-aliasing which was set on FXAA and ambient occlusion set on SSAO (screenshot was taken with the same settings). As for graphical differences I can't really say except that CS lights are fixed when using higher values so I'll leave that to Helifax since he knows the game better.
Indoor starting area:
0x00004000: 30-40 fps
0x00005000: 28-39 fps
0x00006000: 30-40 fps
0x00007000: 28-39 fps
0x0000C000: 30-45 fps
0x0000D000: 30-44 fps
0x0000E000: 29-44 fps
0x0000F000: 30-44 fps
Outdoor on the first planet:
0x00004000: 25-32 fps
0x00005000: 22-28 fps
0x00006000: 25-32 fps
0x00007000: 22-28 fps
0x0000C000: 26-34 fps
0x0000D000: 24-30 fps
0x0000E000: 26-34 fps
0x0000F000: 23-29 fps
Just test and it's true CS Lights are fixed (without 3D Migoto runing), almost 90-95% of them, and get more performance...BUT this just add some pixels arround the character with some ligts. Minor problem i think. Hope DSS / Helifax take a look some day.
I remind you that the game is shared in the ORIGIN account for Shaderhackers...
I will donate some money (at the end of this month) for help DSS/Helifax and thank them all the hard work that are they doing for this community.
i7 4970k@4.5Ghz, SLI GTX1080Ti Aorus Gigabyte Xtreme, 16GB G Skill 2400hrz, 3*PG258Q in 3D surround.
I will eventually give this fix another look, in the light of the new discovery:) I don't have an ETA on it though...Actually, no.. I am not going to revisit this. If I do, it will not be released publicly, for reasons.
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)
Thanks for that - I've added a summary of those results on the wiki (and feel free to sign up for an account so you can directly edit the page). My take on your results is that STEREO_COMPUTE_SAME_RESOURCES_AS_GRAPHICS regains up to 5fps of the performance lost with STEREO_COMPUTE_ENABLE on single GPU (which makes sense, since some compute shaders will then only be run once), and whatever 0x00001000 is has an additional performance cost of up to 5fps.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
:_____(
as I said in the other post...i hope that you change your mind.., and if we can do something about, please count on us!!
Anyway THANK you for all your incredible work that you have given us all these years.
i7 4970k@4.5Ghz, SLI GTX1080Ti Aorus Gigabyte Xtreme, 16GB G Skill 2400hrz, 3*PG258Q in 3D surround.
Can I ask why you won't be releasing any potential future fix to this publicly?
You are certainly within your full right not to, I'm just curious and trying to understand. Would assume it has something to do with people wanting too much and giving too little, but I don't know ofc.
And feel free to tell me to bugger off or just say nothing if indeed "Reasons" are as much information as you're willing to divulge :D
Helifax says, it's too much time spent in small fixes that won't work on all rig... To make it works on each rig it a +50% extra time, this time will be put through other games.
i7 4790K @4.8Ghz / 2x 1080 8GB SLI @2000Mhz / 16GB @2400Mhz
Just click:
My 3D videos and crosstalk test pattern
3DVision Fixes:
HelixMod Site
Universal fix for UnrealEngine 4 Games
Universal fix for Unity Games
Universal fix for FrostBite 3 Games
Universal fix for TellTales Games
Compability Mode Unleashed
Please donate if you can:
-----> Donations to 3DVision Fixers
.