[quote=""]Thanks bo3b! I deleted the rows but the gray blotches are still on geralts face on candle lights. tried to disable geralts hairworks but that doesnt seem to relate to that :S
Using still witcher 1.04 thought, i dont trust to upgrade since my game is running perfect except the gray shadows on interior warm fires. Gray stuff not only on geralts and others face, sometimes even on furniture :)[/quote]
OK, can't explain that. Should be fine on 1.04 of the game, that's where the fix was developed, and no need to update.
Since you are on Win7, try doing a clean reinstall of the fix from DarkStarSword's update. This might include an ASM file that Flugan mentions above. We debugged the grey blotches to that ShaderOverride, and thought it was fixed in the 0.04 release, so if it's not, it'd help Mike to know where it stands.
Use this link to get the Win7 variant of the fix where we are pretty sure this is fixed. Be sure the use the 1.1.16 version of 3Dmigoto linked there too.
[url]https://forums.geforce.com/default/topic/546943/3d-vision/the-witcher-3-wild-hunt/post/4559166/#4559166[/url]
said:Thanks bo3b! I deleted the rows but the gray blotches are still on geralts face on candle lights. tried to disable geralts hairworks but that doesnt seem to relate to that :S
Using still witcher 1.04 thought, i dont trust to upgrade since my game is running perfect except the gray shadows on interior warm fires. Gray stuff not only on geralts and others face, sometimes even on furniture :)
OK, can't explain that. Should be fine on 1.04 of the game, that's where the fix was developed, and no need to update.
Since you are on Win7, try doing a clean reinstall of the fix from DarkStarSword's update. This might include an ASM file that Flugan mentions above. We debugged the grey blotches to that ShaderOverride, and thought it was fixed in the 0.04 release, so if it's not, it'd help Mike to know where it stands.
Use this link to get the Win7 variant of the fix where we are pretty sure this is fixed. Be sure the use the 1.1.16 version of 3Dmigoto linked there too.
I am using the 1.04 fix and no gray spots in this version.
Must be using a shader(s) from the old version there...
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=""]Thanks bo3b! I deleted the rows but the gray blotches are still on geralts face on candle lights. tried to disable geralts hairworks but that doesnt seem to relate to that :S
Using still witcher 1.04 thought, i dont trust to upgrade since my game is running perfect except the gray shadows on interior warm fires. Gray stuff not only on geralts and others face, sometimes even on furniture :)[/quote]
I have the same thing. Deleted all shaders *.ini put in the new ones with 1.04 and now the 1.05 Witcher update just fires and candles have this blob look in 3d. At 1st the faces had it so this is when I just deleted all and put in new yet now just fires. There was a time and I cant remember when that the fire was perfect. So it WAS gone but now back.
This is in Win 8.1 and Win 7 x64. 3 different NV drivers had no effect what so ever.
I must have been sleeping under a rock.. "compatibility mode" JUUUUUUST found out yesterday it was there. haha
Dont think it will help.. Mine is the GOG version..well Greengameing $39...what a deal. So no steam.. again I dont think this has any effect.. but you guys know this way better then me..
said:Thanks bo3b! I deleted the rows but the gray blotches are still on geralts face on candle lights. tried to disable geralts hairworks but that doesnt seem to relate to that :S
Using still witcher 1.04 thought, i dont trust to upgrade since my game is running perfect except the gray shadows on interior warm fires. Gray stuff not only on geralts and others face, sometimes even on furniture :)
I have the same thing. Deleted all shaders *.ini put in the new ones with 1.04 and now the 1.05 Witcher update just fires and candles have this blob look in 3d. At 1st the faces had it so this is when I just deleted all and put in new yet now just fires. There was a time and I cant remember when that the fire was perfect. So it WAS gone but now back.
This is in Win 8.1 and Win 7 x64. 3 different NV drivers had no effect what so ever.
I must have been sleeping under a rock.. "compatibility mode" JUUUUUUST found out yesterday it was there. haha
Dont think it will help.. Mine is the GOG version..well Greengameing $39...what a deal. So no steam.. again I dont think this has any effect.. but you guys know this way better then me..
AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.
AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.
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=""]AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.[/quote]
Ah yes, also using the free GOG version of the game witch(er) came free with a monster (gtx 980 :D)
but YEAH totally forgot to say, using SSAO, btw , i bet that is the gray blotch tie.
bo3b using any AO?
said:AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.
Ah yes, also using the free GOG version of the game witch(er) came free with a monster (gtx 980 :D)
but YEAH totally forgot to say, using SSAO, btw , i bet that is the gray blotch tie.
bo3b using any AO?
[quote=""]Where can I find the files to play this in 3D guys?[/quote]
Check out the top post on this page my friend. The post it links to will give you more info on where to extract the data (game directory/bin/x64 if memory serves)
said:Where can I find the files to play this in 3D guys?
Check out the top post on this page my friend. The post it links to will give you more info on where to extract the data (game directory/bin/x64 if memory serves)
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
Thanks all for your job! Now The witcher 3 is perfect for me in 3D Vision, like this screen
https://drive.google.com/file/d/0B4cx7MK-bSQRZkhULXFzOTRtbnM/view?usp=sharing
[quote=""]AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.[/quote]
I agree, we need to know which version! For those that are new to this thread, this is how fixes are setup:
1) 3DMigoto wrapper: allows fixes to be applied to a game. Supports DX11 Win7, and sometimes Win8.1. Has lots of features specified in a d3dx.ini file.
2) Flugan wrapper: alternative wrapper that also allows fixes to be applied to a game. It uses a different technique and tends to work much better on Win8.1. Has far fewer features than 3DMigoto at this point in time, but still uses a d3dx.ini file with the same essential entries in it.
3) Shader Fixes: lots of little 'shader' files (text) that contain corrected code to fix 3D issues. These files are used by the wrappers to apply the fix to the game.
So,
- The "3DMigoto Fix" means: 3DMigoto Wrapper + ShaderFixes + D3Dx.ini(3Dmigoto)
- The "Flugan Fix" means: Flugan Wrapper + ShaderFixes (the *same* shader fixes) + D3Dx.ini(Flugan)
For most recent AAA games, all of these need development in order to fix a game, which is why it can get complicated. Because of the 'alpha' nature of this fix, and the fact that we are all part-timers in this, there may at any point be some lag between the 3DMigoto and Flugan 'versions', though we try to avoid that.
Also with recent AAA releases, there have been many game and driver issues that mean games don't work correctly in 3D regardless, and this also confuses the efforts of our fixing, as well as people's expectations of what we are doing - so people often ask if we have fixed a game crashing for example, which is not what we do (unless we cause it somehow).
said:AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.
I agree, we need to know which version! For those that are new to this thread, this is how fixes are setup:
1) 3DMigoto wrapper: allows fixes to be applied to a game. Supports DX11 Win7, and sometimes Win8.1. Has lots of features specified in a d3dx.ini file.
2) Flugan wrapper: alternative wrapper that also allows fixes to be applied to a game. It uses a different technique and tends to work much better on Win8.1. Has far fewer features than 3DMigoto at this point in time, but still uses a d3dx.ini file with the same essential entries in it.
3) Shader Fixes: lots of little 'shader' files (text) that contain corrected code to fix 3D issues. These files are used by the wrappers to apply the fix to the game.
So,
- The "3DMigoto Fix" means: 3DMigoto Wrapper + ShaderFixes + D3Dx.ini(3Dmigoto)
- The "Flugan Fix" means: Flugan Wrapper + ShaderFixes (the *same* shader fixes) + D3Dx.ini(Flugan)
For most recent AAA games, all of these need development in order to fix a game, which is why it can get complicated. Because of the 'alpha' nature of this fix, and the fact that we are all part-timers in this, there may at any point be some lag between the 3DMigoto and Flugan 'versions', though we try to avoid that.
Also with recent AAA releases, there have been many game and driver issues that mean games don't work correctly in 3D regardless, and this also confuses the efforts of our fixing, as well as people's expectations of what we are doing - so people often ask if we have fixed a game crashing for example, which is not what we do (unless we cause it somehow).
[quote=""][quote=""]AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.[/quote]
I agree, we need to know which version! For those that are new to this thread, this is how fixes are setup:
1) 3DMigoto wrapper: allows fixes to be applied to a game. Supports DX11 Win7, and sometimes Win8.1. Has lots of features specified in a d3dx.ini file.
2) Flugan wrapper: alternative wrapper that also allows fixes to be applied to a game. It uses a different technique and tends to work much better on Win8.1. Has far fewer features than 3DMigoto at this point in time, but still uses a d3dx.ini file with the same essential entries in it.
3) Shader Fixes: lots of little 'shader' files (text) that contain corrected code to fix 3D issues. These files are used by the wrappers to apply the fix to the game.
So,
- The "3DMigoto Fix" means: 3DMigoto Wrapper + ShaderFixes + D3Dx.ini(3Dmigoto)
- The "Flugan Fix" means: Flugan Wrapper + ShaderFixes (the *same* shader fixes) + D3Dx.ini(Flugan)
For most recent AAA games, all of these need development in order to fix a game, which is why it can get complicated. Because of the 'alpha' nature of this fix, and the fact that we are all part-timers in this, there may at any point be some lag between the 3DMigoto and Flugan 'versions', though we try to avoid that.
Also with recent AAA releases, there have been many game and driver issues that mean games don't work correctly in 3D regardless, and this also confuses the efforts of our fixing, as well as people's expectations of what we are doing - so people often ask if we have fixed a game crashing for example, which is not what we do (unless we cause it somehow).[/quote]
You guys...are the Pwnz :-)
said:AFAIK the face blotches you are referring to is a side effect of skipping one of the lighting shaders while AO is enabled. This should not be done by default in the 0.04 alpha based on 3Dmigoto (there's a toggle on the F1 key that will do this) - is this in the Flugan version?
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.
I agree, we need to know which version! For those that are new to this thread, this is how fixes are setup:
1) 3DMigoto wrapper: allows fixes to be applied to a game. Supports DX11 Win7, and sometimes Win8.1. Has lots of features specified in a d3dx.ini file.
2) Flugan wrapper: alternative wrapper that also allows fixes to be applied to a game. It uses a different technique and tends to work much better on Win8.1. Has far fewer features than 3DMigoto at this point in time, but still uses a d3dx.ini file with the same essential entries in it.
3) Shader Fixes: lots of little 'shader' files (text) that contain corrected code to fix 3D issues. These files are used by the wrappers to apply the fix to the game.
So,
- The "3DMigoto Fix" means: 3DMigoto Wrapper + ShaderFixes + D3Dx.ini(3Dmigoto)
- The "Flugan Fix" means: Flugan Wrapper + ShaderFixes (the *same* shader fixes) + D3Dx.ini(Flugan)
For most recent AAA games, all of these need development in order to fix a game, which is why it can get complicated. Because of the 'alpha' nature of this fix, and the fact that we are all part-timers in this, there may at any point be some lag between the 3DMigoto and Flugan 'versions', though we try to avoid that.
Also with recent AAA releases, there have been many game and driver issues that mean games don't work correctly in 3D regardless, and this also confuses the efforts of our fixing, as well as people's expectations of what we are doing - so people often ask if we have fixed a game crashing for example, which is not what we do (unless we cause it somehow).
You guys...are the Pwnz :-)
ASUS VG278H - 3D Vision 2 - Driver 358.87 - Titan X SLI@1519Mhz - i7-4930K@4.65GHz - 16GB RAM - Win7x64 - Samsung SSD 850 PRO (256GB) and Samsung EVO 850 (1TB) - Full EK Custom Waterloop - Project Milkyway Galaxy (3D Mark Firestrike Hall of Famer)
I just wanted to give a huge thanks to you guys, Flugan alpha 0.4 update 2 looks almost 3d ready and the game is incredible in 3d, I get crashes only when I have to reload, so I'm fine with that.
Big thanks!
I just wanted to give a huge thanks to you guys, Flugan alpha 0.4 update 2 looks almost 3d ready and the game is incredible in 3d, I get crashes only when I have to reload, so I'm fine with that.
Big thanks!
All hail 3d modders DHR, MasterOtaku, Losti, Necropants, Helifax, bo3b, mike_ar69, Flugan, DarkStarSword, 4everAwake, 3d4dd and so many more helping to keep the 3d dream alive, find their 3d fixes at http://helixmod.blogspot.com/ Also check my site for spanish VR and mobile gaming news: www.gamermovil.com
I agree with Stewie!
[b]Thank you[/b] all 3D wizards for the huge improvements in the 'steroscopisation' of this fantastic game. :)
On my machine, Flugan alpha 0.4 update 2 + Helifax' 3D profile + driver 350.12, the immersion is now almost total.
No crashes for me with almost everything on ultra.
I've just noticed a few problems with some candles (not every...) and some fire places. (see pics)
[img]http://constantin.me.uk/Stereoscopy/witcher301_50.jps[/img][img]http://constantin.me.uk/Stereoscopy/witcher302_50.jps[/img][img]http://constantin.me.uk/Stereoscopy/witcher306_50.jps[/img]
Thank you all 3D wizards for the huge improvements in the 'steroscopisation' of this fantastic game. :)
On my machine, Flugan alpha 0.4 update 2 + Helifax' 3D profile + driver 350.12, the immersion is now almost total.
No crashes for me with almost everything on ultra.
I've just noticed a few problems with some candles (not every...) and some fire places. (see pics)
Overclocked Intel® Core™i5-4690k Quad Core
32 Gb RAM
8GB GEFORCE GTX 1080
3D Vision 2
Windows 10 64 Bit
NVidia driver 419.17
SAMSUNG - UE55H8000 Smart 3D 55" Curved
Philips G-Sync 272G
Oculus Rift with Touch controlers
[quote=""]I agree with Stewie!
[b]Thank you[/b] all 3D wizards for the huge improvements in the 'steroscopisation' of this fantastic game. :)
On my machine, Flugan alpha 0.4 update 2 + Helifax' 3D profile + driver 350.12, the immersion is now almost total.
No crashes for me with almost everything on ultra.
I've just noticed a few problems with some candles (not every...) and some fire places. (see pics)
[img]http://constantin.me.uk/Stereoscopy/witcher301_50.jps[/img][img]http://constantin.me.uk/Stereoscopy/witcher302_50.jps[/img][img]http://constantin.me.uk/Stereoscopy/witcher306_50.jps[/img][/quote]
Now, that is very strange! I saw this at some point a while ago! But I never with v.04 I never had this issue...
In any case can you try out the fix attached here ? (Is using flugan's wrapper/DLL + shaders from v.04, where this problem should be fixed).
Don't forget to remove the ".jpg" as is a RAR file;)
Thank you all 3D wizards for the huge improvements in the 'steroscopisation' of this fantastic game. :)
On my machine, Flugan alpha 0.4 update 2 + Helifax' 3D profile + driver 350.12, the immersion is now almost total.
No crashes for me with almost everything on ultra.
I've just noticed a few problems with some candles (not every...) and some fire places. (see pics)
Now, that is very strange! I saw this at some point a while ago! But I never with v.04 I never had this issue...
In any case can you try out the fix attached here ? (Is using flugan's wrapper/DLL + shaders from v.04, where this problem should be fixed).
Don't forget to remove the ".jpg" as is a RAR file;)
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, can't explain that. Should be fine on 1.04 of the game, that's where the fix was developed, and no need to update.
Since you are on Win7, try doing a clean reinstall of the fix from DarkStarSword's update. This might include an ASM file that Flugan mentions above. We debugged the grey blotches to that ShaderOverride, and thought it was fixed in the 0.04 release, so if it's not, it'd help Mike to know where it stands.
Use this link to get the Win7 variant of the fix where we are pretty sure this is fixed. Be sure the use the 1.1.16 version of 3Dmigoto linked there too.
https://forums.geforce.com/default/topic/546943/3d-vision/the-witcher-3-wild-hunt/post/4559166/#4559166
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
Must be using a shader(s) from the old version there...
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)
It happens only with 3d vision enabled, with or without migoto - when I disable it I can reload without any problems even with 3Dmigoto dll.
MSI Z97 GAMING 5
Intel Core i7 4790K
G.SKILL RipjawsX DDR3 2133MHz CL9 16GB
MSI GTX980 GAMING 4G
Windows 7
I have the same thing. Deleted all shaders *.ini put in the new ones with 1.04 and now the 1.05 Witcher update just fires and candles have this blob look in 3d. At 1st the faces had it so this is when I just deleted all and put in new yet now just fires. There was a time and I cant remember when that the fire was perfect. So it WAS gone but now back.
This is in Win 8.1 and Win 7 x64. 3 different NV drivers had no effect what so ever.
I must have been sleeping under a rock.. "compatibility mode" JUUUUUUST found out yesterday it was there. haha
Dont think it will help.. Mine is the GOG version..well Greengameing $39...what a deal. So no steam.. again I dont think this has any effect.. but you guys know this way better then me..
Edit: Sorry, I completely missed the last page of posts, I see this has already been covered.
Also in general - when people report problems can you please indicate whether you are using the 3Dmigoto version of the fix (posted by me or Mike) or the Flugan version to avoid confusion.
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
Ah yes, also using the free GOG version of the game witch(er) came free with a monster (gtx 980 :D)
but YEAH totally forgot to say, using SSAO, btw , i bet that is the gray blotch tie.
bo3b using any AO?
Win 7 64bit ; i7 4790K ; GTX 980 ASUS OC ;10 gb ram ; 353.06 ; 42" edid 3Dvision passive interleaved screen
Check out the top post on this page my friend. The post it links to will give you more info on where to extract the data (game directory/bin/x64 if memory serves)
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
https://drive.google.com/file/d/0B4cx7MK-bSQRZkhULXFzOTRtbnM/view?usp=sharing
Win 7 64bit ; i7 4790K ; GTX 980 ASUS OC ;10 gb ram ; 353.06 ; 42" edid 3Dvision passive interleaved screen
I agree, we need to know which version! For those that are new to this thread, this is how fixes are setup:
1) 3DMigoto wrapper: allows fixes to be applied to a game. Supports DX11 Win7, and sometimes Win8.1. Has lots of features specified in a d3dx.ini file.
2) Flugan wrapper: alternative wrapper that also allows fixes to be applied to a game. It uses a different technique and tends to work much better on Win8.1. Has far fewer features than 3DMigoto at this point in time, but still uses a d3dx.ini file with the same essential entries in it.
3) Shader Fixes: lots of little 'shader' files (text) that contain corrected code to fix 3D issues. These files are used by the wrappers to apply the fix to the game.
So,
- The "3DMigoto Fix" means: 3DMigoto Wrapper + ShaderFixes + D3Dx.ini(3Dmigoto)
- The "Flugan Fix" means: Flugan Wrapper + ShaderFixes (the *same* shader fixes) + D3Dx.ini(Flugan)
For most recent AAA games, all of these need development in order to fix a game, which is why it can get complicated. Because of the 'alpha' nature of this fix, and the fact that we are all part-timers in this, there may at any point be some lag between the 3DMigoto and Flugan 'versions', though we try to avoid that.
Also with recent AAA releases, there have been many game and driver issues that mean games don't work correctly in 3D regardless, and this also confuses the efforts of our fixing, as well as people's expectations of what we are doing - so people often ask if we have fixed a game crashing for example, which is not what we do (unless we cause it somehow).
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
You guys...are the Pwnz :-)
ASUS VG278H - 3D Vision 2 - Driver 358.87 - Titan X SLI@1519Mhz - i7-4930K@4.65GHz - 16GB RAM - Win7x64 - Samsung SSD 850 PRO (256GB) and Samsung EVO 850 (1TB) - Full EK Custom Waterloop - Project Milkyway Galaxy (3D Mark Firestrike Hall of Famer)
G-Pat on Helixmod
Big thanks!
All hail 3d modders DHR, MasterOtaku, Losti, Necropants, Helifax, bo3b, mike_ar69, Flugan, DarkStarSword, 4everAwake, 3d4dd and so many more helping to keep the 3d dream alive, find their 3d fixes at http://helixmod.blogspot.com/ Also check my site for spanish VR and mobile gaming news: www.gamermovil.com
Thank you all 3D wizards for the huge improvements in the 'steroscopisation' of this fantastic game. :)
On my machine, Flugan alpha 0.4 update 2 + Helifax' 3D profile + driver 350.12, the immersion is now almost total.
No crashes for me with almost everything on ultra.
I've just noticed a few problems with some candles (not every...) and some fire places. (see pics)
Overclocked Intel® Core™i5-4690k Quad Core
32 Gb RAM
8GB GEFORCE GTX 1080
3D Vision 2
Windows 10 64 Bit
NVidia driver 419.17
SAMSUNG - UE55H8000 Smart 3D 55" Curved
Philips G-Sync 272G
Oculus Rift with Touch controlers
Now, that is very strange! I saw this at some point a while ago! But I never with v.04 I never had this issue...
In any case can you try out the fix attached here ? (Is using flugan's wrapper/DLL + shaders from v.04, where this problem should be fixed).
Don't forget to remove the ".jpg" as is a RAR file;)
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)