I've fixed the clipping issue on the global illumination shading, but the light shafts are working fine for me. The save SKAUT posted is in the DLC which I don't have - are the light shafts different there?
Were there some decal issues somewhere?
I've fixed the clipping issue on the global illumination shading, but the light shafts are working fine for me. The save SKAUT posted is in the DLC which I don't have - are the light shafts different there?
Were there some decal issues somewhere?
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="DarkStarSword"]I've fixed the clipping issue on the global illumination shading, but the light shafts are working fine for me. The save SKAUT posted is in the DLC which I don't have - are the light shafts different there?
Were there some decal issues somewhere?[/quote]
The light shafts are working perfectly fine for me as well in the DLC as well;)
I am going to try and hunt the decal shaders or give you a save exactly to show the issue;)
I found a couple of them last night but when I tried to correct them nothing happens;)
DarkStarSword said:I've fixed the clipping issue on the global illumination shading, but the light shafts are working fine for me. The save SKAUT posted is in the DLC which I don't have - are the light shafts different there?
Were there some decal issues somewhere?
The light shafts are working perfectly fine for me as well in the DLC as well;)
I am going to try and hunt the decal shaders or give you a save exactly to show the issue;)
I found a couple of them last night but when I tried to correct them nothing happens;)
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
There's a second issue that resembles clipping on some reflections on the ground that's giving me some trouble (visible from some of the saves that biz posted, on the ground near one of the gates with two torches). Mike or Helifax - I could use a second opinion on this one - it's pixel shader fed94596a77ba6a7 (decompiler bugs on this shader are easy - just declare a "ByteAddressBuffer t21 : register(t21);" and it's just blah = t21.Load(blah) where it wants a fixup).
My current working theory is that it's choosing the closest reflection probe (r8.z) to the pixel in the first while loop of the shader, and that is selecting the wrong probe in between two nearby probes in stereo.
Strangely, it's vertex shader (aa66544efb385a02) causes the game to crash if StereoParams is declared (regardless of using HLSL or assembly), but I'm pretty sure the fix needs to go in the pixel shader.
The GI clipping fix was just a matter of disabling one of the tests in that shader:
https://github.com/bo3b/3Dmigoto/commit/e54ed71cead64c85cc7bc3f373db06410735c171
There's a second issue that resembles clipping on some reflections on the ground that's giving me some trouble (visible from some of the saves that biz posted, on the ground near one of the gates with two torches). Mike or Helifax - I could use a second opinion on this one - it's pixel shader fed94596a77ba6a7 (decompiler bugs on this shader are easy - just declare a "ByteAddressBuffer t21 : register(t21);" and it's just blah = t21.Load(blah) where it wants a fixup).
My current working theory is that it's choosing the closest reflection probe (r8.z) to the pixel in the first while loop of the shader, and that is selecting the wrong probe in between two nearby probes in stereo.
Strangely, it's vertex shader (aa66544efb385a02) causes the game to crash if StereoParams is declared (regardless of using HLSL or assembly), but I'm pretty sure the fix needs to go in the pixel shader.
Anyone seen any problems with this shader??
I have also attached the txt file of the shader.
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
Did more testing:
- I even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
- I even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
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"]Did more testing:
- I even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
[/quote]
I thought I had posted on this earlier, but my post is not there... Hmmm... But yeah, decals are wrong in 2D, so don't waste too much time on them...
- I even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
I thought I had posted on this earlier, but my post is not there... Hmmm... But yeah, decals are wrong in 2D, so don't waste too much time on them...
[quote="DarkStarSword"]There's a second issue that resembles clipping on some reflections on the ground that's giving me some trouble (visible from some of the saves that biz posted, on the ground near one of the gates with two torches). Mike or Helifax - I could use a second opinion on this one - it's pixel shader fed94596a77ba6a7 (decompiler bugs on this shader are easy - just declare a "ByteAddressBuffer t21 : register(t21);" and it's just blah = t21.Load(blah) where it wants a fixup).
My current working theory is that it's choosing the closest reflection probe (r8.z) to the pixel in the first while loop of the shader, and that is selecting the wrong probe in between two nearby probes in stereo.
Strangely, it's vertex shader (aa66544efb385a02) causes the game to crash if StereoParams is declared (regardless of using HLSL or assembly), but I'm pretty sure the fix needs to go in the pixel shader.
The GI clipping fix was just a matter of disabling one of the tests in that shader:
https://github.com/bo3b/3Dmigoto/commit/e54ed71cead64c85cc7bc3f373db06410735c171[/quote]
Nice find on the global lights. Is this a general fix needed by all fixed compute shaders? This is a common "pattern" now, so we should add it to the list of tools and techniques somewhere. Also, are you getting crashes when stepping through compute shaders?
DarkStarSword said:There's a second issue that resembles clipping on some reflections on the ground that's giving me some trouble (visible from some of the saves that biz posted, on the ground near one of the gates with two torches). Mike or Helifax - I could use a second opinion on this one - it's pixel shader fed94596a77ba6a7 (decompiler bugs on this shader are easy - just declare a "ByteAddressBuffer t21 : register(t21);" and it's just blah = t21.Load(blah) where it wants a fixup).
My current working theory is that it's choosing the closest reflection probe (r8.z) to the pixel in the first while loop of the shader, and that is selecting the wrong probe in between two nearby probes in stereo.
Strangely, it's vertex shader (aa66544efb385a02) causes the game to crash if StereoParams is declared (regardless of using HLSL or assembly), but I'm pretty sure the fix needs to go in the pixel shader.
Nice find on the global lights. Is this a general fix needed by all fixed compute shaders? This is a common "pattern" now, so we should add it to the list of tools and techniques somewhere. Also, are you getting crashes when stepping through compute shaders?
[quote="mike_ar69"][quote="helifax"]Did more testing:
- I even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
[/quote]
I thought I had posted on this earlier, but my post is not there... Hmmm... But yeah, decals are wrong in 2D, so don't waste too much time on them...[/quote]
Yeah, DAMN! I've spent like 3 hours on trying to understand why it doesn't work:))) until I had the briliant Idea of trying it in 2D (without 3DMigoto or any other Mod) and noticed they are rendered wrong from the engine:)))
Damn;)) In any case they are not "that" wrong but certainly you see them way better in 3D then 2D;))
- I even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
I thought I had posted on this earlier, but my post is not there... Hmmm... But yeah, decals are wrong in 2D, so don't waste too much time on them...
Yeah, DAMN! I've spent like 3 hours on trying to understand why it doesn't work:))) until I had the briliant Idea of trying it in 2D (without 3DMigoto or any other Mod) and noticed they are rendered wrong from the engine:)))
Damn;)) In any case they are not "that" wrong but certainly you see them way better in 3D then 2D;))
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="mike_ar69"]Nice find on the global lights. Is this a general fix needed by all fixed compute shaders?[/quote]As I recall there was only one global illumination shader we found originally, though it's worth keeping an eye out for similar clipping elsewhere.
[quote]This is a common "pattern" now, so we should add it to the list of tools and techniques somewhere.[/quote]You mean the general approach of disabling tests? I've been thinking for a while now of adding a page (or pages) to bo3b's wiki with links to various patterns I've cracked.
[quote]Also, are you getting crashes when stepping through compute shaders?[/quote]Yeah, I'm using frame analysis to find compute shaders in this game because of that (to save time, set a trigger to start dumping at 170486ed36efcc9e, which is the very first post-processing shader run with HBAO+ enabled). What might be happening is the output from one compute shader is feeding into another one, which is looping a given number of iterations based on that and when it processes garbage data it crashes instead (it's very easy to crash a game with an infinite loop in a shader).
Amusingly there's one particular pixel shader that makes Geralt start swimming whenever I pass it while hunting :-p
BTW I'm putting the reflection shader down for now - I spent most of yesterday trying different experiments on it and haven't got any closer to figuring out where the clipping is coming from let alone what to do about it. Feel free to take a look - I might have just missed something obvious. I'm not sure how common this particular clipping is, so I'm not sure if it's worth spending much time on it.
mike_ar69 said:Nice find on the global lights. Is this a general fix needed by all fixed compute shaders?
As I recall there was only one global illumination shader we found originally, though it's worth keeping an eye out for similar clipping elsewhere.
This is a common "pattern" now, so we should add it to the list of tools and techniques somewhere.
You mean the general approach of disabling tests? I've been thinking for a while now of adding a page (or pages) to bo3b's wiki with links to various patterns I've cracked.
Also, are you getting crashes when stepping through compute shaders?
Yeah, I'm using frame analysis to find compute shaders in this game because of that (to save time, set a trigger to start dumping at 170486ed36efcc9e, which is the very first post-processing shader run with HBAO+ enabled). What might be happening is the output from one compute shader is feeding into another one, which is looping a given number of iterations based on that and when it processes garbage data it crashes instead (it's very easy to crash a game with an infinite loop in a shader).
Amusingly there's one particular pixel shader that makes Geralt start swimming whenever I pass it while hunting :-p
BTW I'm putting the reflection shader down for now - I spent most of yesterday trying different experiments on it and haven't got any closer to figuring out where the clipping is coming from let alone what to do about it. Feel free to take a look - I might have just missed something obvious. I'm not sure how common this particular clipping is, so I'm not sure if it's worth spending much time on it.
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="DarkStarSword"]
Amusingly there's one particular pixel shader that makes Geralt start swimming whenever I pass it while hunting :-p
[/quote]
That one is my favourite;))
There is also a VS (I think)that makes the whole world disappears and instead puts Geralt in water swimming;))
I actually had a bit of Fun with the PS shader:)) "swimming around the road" ^_^ the other day:))
Amusingly there's one particular pixel shader that makes Geralt start swimming whenever I pass it while hunting :-p
That one is my favourite;))
There is also a VS (I think)that makes the whole world disappears and instead puts Geralt in water swimming;))
I actually had a bit of Fun with the PS shader:)) "swimming around the road" ^_^ the other day:))
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
Hello, I have installed TW3 for the first time some days ago, and still I have not played the game, only installed mods and test some things. I have installed v1.12, and I have noticed that 3D fix is broken.
I have also noticed that "fake 3D" is good enough to play this game, specially for me because I do not have a powerfull computer (nvidia 660 TI + i7 930) and fake 3D demands less power. The big problem I find playing using fake3D is that the normal text appears corrupt, I suppose because the same reason that we can see a halo around the character. I would like to know if there is any way to fix the text (maybe only changing the depth), to read it properly.
Anyway waiting also for a real fix for v1.12, even though I think I have not enough computer to play using it decently smooth.
Hello, I have installed TW3 for the first time some days ago, and still I have not played the game, only installed mods and test some things. I have installed v1.12, and I have noticed that 3D fix is broken.
I have also noticed that "fake 3D" is good enough to play this game, specially for me because I do not have a powerfull computer (nvidia 660 TI + i7 930) and fake 3D demands less power. The big problem I find playing using fake3D is that the normal text appears corrupt, I suppose because the same reason that we can see a halo around the character. I would like to know if there is any way to fix the text (maybe only changing the depth), to read it properly.
Anyway waiting also for a real fix for v1.12, even though I think I have not enough computer to play using it decently smooth.
@b4thman:
There isn't anything broken... I have played the game each day for the last week and NOTHING is broken...
If you are using graphical mods check those...
As a matter of fact you should forget those if you want to have any performance...
Also CM (fake 3D) is crap in comparison with real 3D in this game...
@b4thman:
There isn't anything broken... I have played the game each day for the last week and NOTHING is broken...
If you are using graphical mods check those...
As a matter of fact you should forget those if you want to have any performance...
Also CM (fake 3D) is crap in comparison with real 3D in this game...
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
Ok, everything is perfect now, apparently, after 1 minute of gameplay. I have arrived home and 1st of all I have installed the last whql driver (361.43), and copied all the 3dfix files again, and all is good. Previously I think I didn't overwrite the file "d3dcompiler_46.dll" (it was already present in the game), and maybe that or the different driver version used now may be the difference.
Also I have not done anything about 2nd step ("helifax custom profile"), as I understand it is intended to solve problems to SLI ownners (that is not my case, I only have one modest 660TI).
The only thing is that, of course, I lose some valious fps playing, and maybe if it were possible to get rid of the visual anomalies it would be probably better for me to play with fake3D, but only because of the less demanding hardware, that in my case is crucial. Another solution would be if Nvidia donate me one 980 TI, but it won't probably happen.
As always, thanks for the community support.
Ok, everything is perfect now, apparently, after 1 minute of gameplay. I have arrived home and 1st of all I have installed the last whql driver (361.43), and copied all the 3dfix files again, and all is good. Previously I think I didn't overwrite the file "d3dcompiler_46.dll" (it was already present in the game), and maybe that or the different driver version used now may be the difference.
Also I have not done anything about 2nd step ("helifax custom profile"), as I understand it is intended to solve problems to SLI ownners (that is not my case, I only have one modest 660TI).
The only thing is that, of course, I lose some valious fps playing, and maybe if it were possible to get rid of the visual anomalies it would be probably better for me to play with fake3D, but only because of the less demanding hardware, that in my case is crucial. Another solution would be if Nvidia donate me one 980 TI, but it won't probably happen.
[quote="b4thman"]Ok, everything is perfect now, apparently, after 1 minute of gameplay. I have arrived home and 1st of all I have installed the last whql driver (361.43), and copied all the 3dfix files again, and all is good. Previously I think I didn't overwrite the file "d3dcompiler_46.dll" (it was already present in the game), and maybe that or the different driver version used now may be the difference.
Also I have not done anything about 2nd step ("helifax custom profile"), as I understand it is intended to solve problems to SLI ownners (that is not my case, I only have one modest 660TI).
The only thing is that, of course, I lose some valious fps playing, and maybe if it were possible to get rid of the visual anomalies it would be probably better for me to play with fake3D, but only because of the less demanding hardware, that in my case is crucial. Another solution would be if Nvidia donate me one 980 TI, but it won't probably happen.
As always, thanks for the community support.[/quote]
Hi,
If you have the GOG version DO NOT start the game from GOG Galaxy browser! It will automatically overwrite the d3d11.dll and dxdgi.dll with it's own version and thus will make the fix invalid;)
If this happens just apply the 3D Vision fix again;)
Also if you update the drivers you should also re-import the nvidia profile stated there. Without it you will get in places underground or under water where the WHOLE UI will be missing;)
Happy gaming;)
b4thman said:Ok, everything is perfect now, apparently, after 1 minute of gameplay. I have arrived home and 1st of all I have installed the last whql driver (361.43), and copied all the 3dfix files again, and all is good. Previously I think I didn't overwrite the file "d3dcompiler_46.dll" (it was already present in the game), and maybe that or the different driver version used now may be the difference.
Also I have not done anything about 2nd step ("helifax custom profile"), as I understand it is intended to solve problems to SLI ownners (that is not my case, I only have one modest 660TI).
The only thing is that, of course, I lose some valious fps playing, and maybe if it were possible to get rid of the visual anomalies it would be probably better for me to play with fake3D, but only because of the less demanding hardware, that in my case is crucial. Another solution would be if Nvidia donate me one 980 TI, but it won't probably happen.
As always, thanks for the community support.
Hi,
If you have the GOG version DO NOT start the game from GOG Galaxy browser! It will automatically overwrite the d3d11.dll and dxdgi.dll with it's own version and thus will make the fix invalid;)
If this happens just apply the 3D Vision fix again;)
Also if you update the drivers you should also re-import the nvidia profile stated there. Without it you will get in places underground or under water where the WHOLE UI will be missing;)
Happy gaming;)
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
Were there some decal issues somewhere?
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
The light shafts are working perfectly fine for me as well in the DLC as well;)
I am going to try and hunt the decal shaders or give you a save exactly to show the issue;)
I found a couple of them last night but when I tried to correct them nothing happens;)
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)
My current working theory is that it's choosing the closest reflection probe (r8.z) to the pixel in the first while loop of the shader, and that is selecting the wrong probe in between two nearby probes in stereo.
Strangely, it's vertex shader (aa66544efb385a02) causes the game to crash if StereoParams is declared (regardless of using HLSL or assembly), but I'm pretty sure the fix needs to go in the pixel shader.
The GI clipping fix was just a matter of disabling one of the tests in that shader:
https://github.com/bo3b/3Dmigoto/commit/e54ed71cead64c85cc7bc3f373db06410735c171
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
I found one of the PS that are related to some decals that are pushed at wrong/too much into depth. (like a double depth).
Turns out is already corrected...Hmmm
Pictures:
With it enabled(look at Geralt's feet)
With the Ps disabled:
The shader code is like this:
Anyone seen any problems with this shader??
I have also attached the txt file of the shader.
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 even removed the wrapper altogheter and noticed that the decals are floating over the ground in the original/non-fixed game... That's why in stereo 3D we see them at different depths as the game renders them at different depths :))))
- The decals instead of being rendered over the geometry of the terrain they are rendered on a flat plane "hovering" the geometry... You can see it in 2D as well if you look very close...
- I thing this is some of their "optimizations" to make the engine run faster...
- Don't think we can do much about it though :(
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 thought I had posted on this earlier, but my post is not there... Hmmm... But yeah, decals are wrong in 2D, so don't waste too much time on them...
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
Nice find on the global lights. Is this a general fix needed by all fixed compute shaders? This is a common "pattern" now, so we should add it to the list of tools and techniques somewhere. Also, are you getting crashes when stepping through compute shaders?
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
Yeah, DAMN! I've spent like 3 hours on trying to understand why it doesn't work:))) until I had the briliant Idea of trying it in 2D (without 3DMigoto or any other Mod) and noticed they are rendered wrong from the engine:)))
Damn;)) In any case they are not "that" wrong but certainly you see them way better in 3D then 2D;))
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)
You mean the general approach of disabling tests? I've been thinking for a while now of adding a page (or pages) to bo3b's wiki with links to various patterns I've cracked.
Yeah, I'm using frame analysis to find compute shaders in this game because of that (to save time, set a trigger to start dumping at 170486ed36efcc9e, which is the very first post-processing shader run with HBAO+ enabled). What might be happening is the output from one compute shader is feeding into another one, which is looping a given number of iterations based on that and when it processes garbage data it crashes instead (it's very easy to crash a game with an infinite loop in a shader).
Amusingly there's one particular pixel shader that makes Geralt start swimming whenever I pass it while hunting :-p
BTW I'm putting the reflection shader down for now - I spent most of yesterday trying different experiments on it and haven't got any closer to figuring out where the clipping is coming from let alone what to do about it. Feel free to take a look - I might have just missed something obvious. I'm not sure how common this particular clipping is, so I'm not sure if it's worth spending much time on it.
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
That one is my favourite;))
There is also a VS (I think)that makes the whole world disappears and instead puts Geralt in water swimming;))
I actually had a bit of Fun with the PS shader:)) "swimming around the road" ^_^ the other day:))
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 have also noticed that "fake 3D" is good enough to play this game, specially for me because I do not have a powerfull computer (nvidia 660 TI + i7 930) and fake 3D demands less power. The big problem I find playing using fake3D is that the normal text appears corrupt, I suppose because the same reason that we can see a halo around the character. I would like to know if there is any way to fix the text (maybe only changing the depth), to read it properly.
Anyway waiting also for a real fix for v1.12, even though I think I have not enough computer to play using it decently smooth.
- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "Gigabyte RTX 2080 Gaming OC"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)
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
There isn't anything broken... I have played the game each day for the last week and NOTHING is broken...
If you are using graphical mods check those...
As a matter of fact you should forget those if you want to have any performance...
Also CM (fake 3D) is crap in comparison with real 3D in this game...
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)
Also I have not done anything about 2nd step ("helifax custom profile"), as I understand it is intended to solve problems to SLI ownners (that is not my case, I only have one modest 660TI).
The only thing is that, of course, I lose some valious fps playing, and maybe if it were possible to get rid of the visual anomalies it would be probably better for me to play with fake3D, but only because of the less demanding hardware, that in my case is crucial. Another solution would be if Nvidia donate me one 980 TI, but it won't probably happen.
As always, thanks for the community support.
- Windows 7 64bits (SSD OCZ-Vertez2 128Gb)
- "ASUS P6X58D-E" motherboard
- "Gigabyte RTX 2080 Gaming OC"
- "Intel Xeon X5670" @4000MHz CPU (20.0[12-25]x200MHz)
- RAM 16 Gb DDR3 1600
- "Dell S2716DG" monitor (2560x1440 @144Hz)
- "Corsair Carbide 600C" case
- Labrador dog (cinnamon edition)
Hi,
If you have the GOG version DO NOT start the game from GOG Galaxy browser! It will automatically overwrite the d3d11.dll and dxdgi.dll with it's own version and thus will make the fix invalid;)
If this happens just apply the 3D Vision fix again;)
Also if you update the drivers you should also re-import the nvidia profile stated there. Without it you will get in places underground or under water where the WHOLE UI will be missing;)
Happy gaming;)
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)