The Witcher 3: Wild Hunt
  72 / 152    
Strange.....I shut down Win 8.1 yesterday in the night, after playing without any CTD. Today i boot up my PC, start the Witcher and BÄM CTD. Restart ist and after 1 min ... CTD. I Shut down my PC, i restart it and BÄM, no CTDs anymore....So this is may be a cache problem or something like that? Since view days i noticed that i have MUCH too much GAMME in the game. Reastart did not solve this, even not shut down. Only shut down AND restart brings up the right ontrast for the game until....i restart it or it crashes. So i will DDU the 353.12 and install 353.06 and i will check this out the next days. ==> This rpoblem is NOT related to SweetFX/Reshade or the 3D Vision fix, because it happens even without !!! So if someone has this problem and a solution :-) Tel me .-) Ill report back later (this post) if 353.12 was causing this problem.
Strange.....I shut down Win 8.1 yesterday in the night, after playing without any CTD. Today i boot up my PC, start the Witcher and BÄM CTD. Restart ist and after 1 min ... CTD. I Shut down my PC, i restart it and BÄM, no CTDs anymore....So this is may be a cache problem or something like that?

Since view days i noticed that i have MUCH too much GAMME in the game. Reastart did not solve this, even not shut down. Only shut down AND restart brings up the right ontrast for the game until....i restart it or it crashes. So i will DDU the 353.12 and install 353.06 and i will check this out the next days. ==> This rpoblem is NOT related to SweetFX/Reshade or the 3D Vision fix, because it happens even without !!! So if someone has this problem and a solution :-) Tel me .-) Ill report back later (this post) if 353.12 was causing this problem.

Like my work? Donations can be made via PayPal to: rauti@inetmx.de

Posted 06/18/2015 04:36 PM   
Anyone else had this? HBAO+ is broken after minute or so of gameplay. Falling back to SSAO fixes it. Restoring back HBAO+ brings back this wrong-depth shading. Restarted game (without PC restart), and after one minutes HBAO+ broke again. P.S. Using 3Dmigoto with 0.06 fix and 1.06 patch.
Anyone else had this? HBAO+ is broken after minute or so of gameplay. Falling back to SSAO fixes it. Restoring back HBAO+ brings back this wrong-depth shading. Restarted game (without PC restart), and after one minutes HBAO+ broke again.
P.S. Using 3Dmigoto with 0.06 fix and 1.06 patch.

ASUS Prime z370-A, i5 8600K, ASUS GTX 1080 Ti Strix, 16 GB DDR4, Corsair AX860i PSU, ASUS VG278HR, 3D Vision 2, Sound Blaster Z, Astro A50 Headphones, Windows 10 64-bit Home

Posted 06/18/2015 05:40 PM   
The "Street Effect" is back hm ??? Could this be ??
The "Street Effect" is back hm ??? Could this be ??

Like my work? Donations can be made via PayPal to: rauti@inetmx.de

Posted 06/18/2015 05:44 PM   
I tracked down white-dots-grid-effect to this shader: [b]4e7b1b2f8c99e97a-cs.txt[/b] Removing it makes dots disappear. I believe this shader is responsible for fog (indoors?), because without it fog is a bit off in a cave in attached savegame. Could anyone capable check it out? Thanks! :) [b]UPDATE:[/b] Actually, this shader responsible for LOTS of things. There are misplaced fire, shadows and other things with it removed... Hope it will be fixed eventually :)
I tracked down white-dots-grid-effect to this shader: 4e7b1b2f8c99e97a-cs.txt
Removing it makes dots disappear. I believe this shader is responsible for fog (indoors?), because without it fog is a bit off in a cave in attached savegame. Could anyone capable check it out?
Thanks! :)

UPDATE: Actually, this shader responsible for LOTS of things. There are misplaced fire, shadows and other things with it removed... Hope it will be fixed eventually :)

ASUS Prime z370-A, i5 8600K, ASUS GTX 1080 Ti Strix, 16 GB DDR4, Corsair AX860i PSU, ASUS VG278HR, 3D Vision 2, Sound Blaster Z, Astro A50 Headphones, Windows 10 64-bit Home

Posted 06/18/2015 06:14 PM   
[quote=""]The "Street Effect" is back hm ??? Could this be ?? [/quote] Thanks for the save, I'll fix it. I don't think it is "back", it's probably a different shader, there are a few of them.
said:The "Street Effect" is back hm ??? Could this be ??


Thanks for the save, I'll fix it. I don't think it is "back", it's probably a different shader, there are a few of them.

Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278

Posted 06/18/2015 06:16 PM   
[quote=""]Anyone else had this? HBAO+ is broken after minute or so of gameplay. Falling back to SSAO fixes it. Restoring back HBAO+ brings back this wrong-depth shading. Restarted game (without PC restart), and after one minutes HBAO+ broke again. P.S. Using 3Dmigoto with 0.06 fix and 1.06 patch.[/quote]I've had this happen a few times as well. Not sure of the cause yet. It kind of looks like a driver bug, but I'm not sure it happened on earlier versions of the game and/or fix, so it might be something else - could you check if it happened with 0.04 of the fix before we touched any compute shaders? If it did I'll look into it a bit more, but if it didn't than I'd rather wait until we have some known issues in the assembler fixed first. [quote=""]I tracked down white-dots-grid-effect to this shader: [b]4e7b1b2f8c99e97a-cs.txt[/b] Removing it makes dots disappear. I believe this shader is responsible for fog (indoors?), because without it fog is a bit off in a cave in attached savegame. Could anyone capable check it out? Thanks! :) [b]UPDATE:[/b] Actually, this shader responsible for LOTS of things. There are misplaced fire, shadows and other things with it removed... Hope it will be fixed eventually :)[/quote] Yep, we know about that one - the assembler is currently generating bad code and needs a fix.
said:Anyone else had this? HBAO+ is broken after minute or so of gameplay. Falling back to SSAO fixes it. Restoring back HBAO+ brings back this wrong-depth shading. Restarted game (without PC restart), and after one minutes HBAO+ broke again.
P.S. Using 3Dmigoto with 0.06 fix and 1.06 patch.
I've had this happen a few times as well. Not sure of the cause yet. It kind of looks like a driver bug, but I'm not sure it happened on earlier versions of the game and/or fix, so it might be something else - could you check if it happened with 0.04 of the fix before we touched any compute shaders? If it did I'll look into it a bit more, but if it didn't than I'd rather wait until we have some known issues in the assembler fixed first.

said:I tracked down white-dots-grid-effect to this shader: 4e7b1b2f8c99e97a-cs.txt
Removing it makes dots disappear. I believe this shader is responsible for fog (indoors?), because without it fog is a bit off in a cave in attached savegame. Could anyone capable check it out?
Thanks! :)

UPDATE: Actually, this shader responsible for LOTS of things. There are misplaced fire, shadows and other things with it removed... Hope it will be fixed eventually :)

Yep, we know about that one - the assembler is currently generating bad code and needs a fix.

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

Posted 06/19/2015 01:51 AM   
As far as I could tell it's a double rounding error with most of the damage done by MS disassembler. Beyond that I need too look into it further.
As far as I could tell it's a double rounding error with most of the damage done by MS disassembler.

Beyond that I need too look into it further.

Thanks to everybody using my assembler it warms my heart.
To have a critical piece of code that everyone can enjoy!
What more can you ask for?

donations: ulfjalmbrant@hotmail.com

Posted 06/19/2015 08:32 AM   
Hello there. Seems like you do good work here :) I'm a bit overwhelmed by the amount of posts and things in this thread, and have a hard time being sure what to do. I still don't have my 3D vision kit so I guess I can try and find all the information, this way when I have it I can simply apply :) As far as I understand it from what I read here are the things I must do : First I read the thread "Beginner's Guide to Understanding and Using NVIDIA 3D Vision/3DTV Play (WIP)" I must DDU my drivers and then reinstall the version 353.06. After that I can follow the instructions on this post : [url]https://forums.geforce.com/default/topic/841696/3d-vision/the-witcher-3-correct-3d-vision-nvidia-profile-cm-mode-included-/[/url] Well if it is still something I should do I mean the post is from june 9th. Not really sure about the next one : I should install flugan fix into the game installation folder. I don't think I've seen a clear explanation of this anywhere. People mention it, but I guess that knowledge is so common here nobody explains it really anymore. I must disable steam overlay (I guess) people are saying a lot that the origin overlay gives problem. So I guess steam is the same? I should prevent witcher from updating in steam so that it won't break everything each update. That was not very straightforward but I found a way to do it (we'll see if it works at the next update). [quote] Import a shortcut using the 'Add Non-Steam Game to My Library' feature. Change the settings for the actual Steam game update options to 'Only Update When I Launch This Game.' Now only launch the game with the shortcut. It seems modded games like GTA IV and Skyrim launching through a shortcut (GTA IV needs it one to add '-norestrictions,' Skyrim uses the SKSE.exe to launch) and don't actually register as the Steam version launching, keeping the update from triggering[/quote] Some people suggest turning off GFE is better. I don't like hairworks much (playing without it in 2D) so I guess it's not a problem that it doesn't work perfect at the moment (seems it's a favorite subject on the thread atm :)). I've got an I7 4790k at 4.0 ghz and a geforce 760 4GB with windows 7. I don't know if it changes anything, but the info is there if needed. If you could redirect me to a clear explanation somewhere it would be best. PS : this is in now way criticism. I know this a work in progress, this is alpha version and you cannot maintain an concise explanation for newcomers. That's normal. People following the thread and testing have enough infos, but it's everywhere in the thread and there is a lot to read. I don't wanna read 72 pages of thread discussing shaders in my weekend. I much prefer playing witcher 3, even if it is not in 3D yet :( That's actually what I'm gonna do now.
Hello there.
Seems like you do good work here :)

I'm a bit overwhelmed by the amount of posts and things in this thread, and have a hard time being sure what to do. I still don't have my 3D vision kit so I guess I can try and find all the information, this way when I have it I can simply apply :)

As far as I understand it from what I read here are the things I must do :
First I read the thread "Beginner's Guide to Understanding and Using NVIDIA 3D Vision/3DTV Play (WIP)"

I must DDU my drivers and then reinstall the version 353.06.
After that I can follow the instructions on this post :
https://forums.geforce.com/default/topic/841696/3d-vision/the-witcher-3-correct-3d-vision-nvidia-profile-cm-mode-included-/
Well if it is still something I should do I mean the post is from june 9th.

Not really sure about the next one : I should install flugan fix into the game installation folder. I don't think I've seen a clear explanation of this anywhere. People mention it, but I guess that knowledge is so common here nobody explains it really anymore.

I must disable steam overlay (I guess) people are saying a lot that the origin overlay gives problem. So I guess steam is the same?

I should prevent witcher from updating in steam so that it won't break everything each update. That was not very straightforward but I found a way to do it (we'll see if it works at the next update).

Import a shortcut using the 'Add Non-Steam Game to My Library' feature. Change the settings for the actual Steam game update options to 'Only Update When I Launch This Game.' Now only launch the game with the shortcut. It seems modded games like GTA IV and Skyrim launching through a shortcut (GTA IV needs it one to add '-norestrictions,' Skyrim uses the SKSE.exe to launch) and don't actually register as the Steam version launching, keeping the update from triggering


Some people suggest turning off GFE is better.

I don't like hairworks much (playing without it in 2D) so I guess it's not a problem that it doesn't work perfect at the moment (seems it's a favorite subject on the thread atm :)).


I've got an I7 4790k at 4.0 ghz and a geforce 760 4GB with windows 7. I don't know if it changes anything, but the info is there if needed.

If you could redirect me to a clear explanation somewhere it would be best.

PS : this is in now way criticism. I know this a work in progress, this is alpha version and you cannot maintain an concise explanation for newcomers. That's normal. People following the thread and testing have enough infos, but it's everywhere in the thread and there is a lot to read. I don't wanna read 72 pages of thread discussing shaders in my weekend. I much prefer playing witcher 3, even if it is not in 3D yet :(
That's actually what I'm gonna do now.

Posted 06/20/2015 12:25 PM   
@kazuma6666 you would be better off waiting until the fix is ready - when it is we will post detailed instructions on the blog. I wouldn't recommend reading through this thread as a lot of the information will already be out of date. I haven't heard anyone mention having issues with the Steam overlay on this game. Might have been an issue with recent drivers, but bo3b made sure that 3Dmigoto would work fine with the overlay. Game updates are usually fine, but occasionally cause issues. Since we are still developing the fix, you should keep up to date as we are, and generally the updates have only improved things. As a rule of thumb, fixes are installed by extracting them into the game directory, such that the d3d11.dll ends up in the same place as the game's executable (in this case under bin\x64). There are two versions of the fix that use different wrappers - both should be equivalent, but some people find one works better than the other on a certain OS, though this has improved considerably in the last few versions of 3Dmigoto. Hairworks is only a hot topic right now as it's the effect I'm currently concentrating on. The worst part of it is now fixed (wait for the next update) - I'm still looking into the second issue with it.
@kazuma6666 you would be better off waiting until the fix is ready - when it is we will post detailed instructions on the blog. I wouldn't recommend reading through this thread as a lot of the information will already be out of date.

I haven't heard anyone mention having issues with the Steam overlay on this game. Might have been an issue with recent drivers, but bo3b made sure that 3Dmigoto would work fine with the overlay.

Game updates are usually fine, but occasionally cause issues. Since we are still developing the fix, you should keep up to date as we are, and generally the updates have only improved things.

As a rule of thumb, fixes are installed by extracting them into the game directory, such that the d3d11.dll ends up in the same place as the game's executable (in this case under bin\x64). There are two versions of the fix that use different wrappers - both should be equivalent, but some people find one works better than the other on a certain OS, though this has improved considerably in the last few versions of 3Dmigoto.

Hairworks is only a hot topic right now as it's the effect I'm currently concentrating on. The worst part of it is now fixed (wait for the next update) - I'm still looking into the second issue with 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

Posted 06/20/2015 12:47 PM   
[quote=""]As far as I could tell it's a double rounding error with most of the damage done by MS disassembler.[/quote]Absolutely spot on - I've manually added the missing precision back into the shader and the white spots are gone :) Thanks Flugan!
said:As far as I could tell it's a double rounding error with most of the damage done by MS disassembler.
Absolutely spot on - I've manually added the missing precision back into the shader and the white spots are gone :)

Thanks Flugan!

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

Posted 06/20/2015 02:13 PM   
[quote=""][quote=""]As far as I could tell it's a double rounding error with most of the damage done by MS disassembler.[/quote]Absolutely spot on - I've manually added the missing precision back into the shader and the white spots are gone :) Thanks Flugan![/quote] I don`t know if you got this as well but every time i see those spots whole my interface disappear - indoor, in caves and underwater. I hope it`s alright after you`ve managed to get rid of them. Mike said something about missing shader in there or something like that.
said:
said:As far as I could tell it's a double rounding error with most of the damage done by MS disassembler.
Absolutely spot on - I've manually added the missing precision back into the shader and the white spots are gone :)

Thanks Flugan!

I don`t know if you got this as well but every time i see those spots whole my interface disappear - indoor, in caves and underwater.
I hope it`s alright after you`ve managed to get rid of them. Mike said something about missing shader in there or something like that.
@SKAUT, that doesn't seem to happen for me on the save Losti posted. I think I recall Helifax saying that setting StereoCutOff to 0 in the driver profile would fix some issue like (FWIW I have *NOT* set that to 0). I'll likely post a new alpha a little later tonight, so you can check if it still occurs then.
@SKAUT, that doesn't seem to happen for me on the save Losti posted. I think I recall Helifax saying that setting StereoCutOff to 0 in the driver profile would fix some issue like (FWIW I have *NOT* set that to 0).

I'll likely post a new alpha a little later tonight, so you can check if it still occurs then.

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

Posted 06/20/2015 03:54 PM   
[quote=""]@SKAUT, that doesn't seem to happen for me on the save Losti posted. I think I recall Helifax saying that setting StereoCutOff to 0 in the driver profile would fix some issue like (FWIW I have *NOT* set that to 0). I'll likely post a new alpha a little later tonight, so you can check if it still occurs then.[/quote] I didn`t have that on previous fix versions so i thought that white spots are some kind of fullscreen transparent shader which covers up that whole UI. I`l wait for another fix and check if that will change.
said:@SKAUT, that doesn't seem to happen for me on the save Losti posted. I think I recall Helifax saying that setting StereoCutOff to 0 in the driver profile would fix some issue like (FWIW I have *NOT* set that to 0).

I'll likely post a new alpha a little later tonight, so you can check if it still occurs then.

I didn`t have that on previous fix versions so i thought that white spots are some kind of fullscreen transparent shader which covers up that whole UI.
I`l wait for another fix and check if that will change.
[quote=""][quote=""]@SKAUT, that doesn't seem to happen for me on the save Losti posted. I think I recall Helifax saying that setting StereoCutOff to 0 in the driver profile would fix some issue like (FWIW I have *NOT* set that to 0). I'll likely post a new alpha a little later tonight, so you can check if it still occurs then.[/quote] I didn`t have that on previous fix versions so i thought that white spots are some kind of fullscreen transparent shader which covers up that whole UI. I`l wait for another fix and check if that will change.[/quote] No no no, USE THIS PROFILE: https://forums.geforce.com/default/topic/841696/the-witcher-3-correct-3d-vision-nvidia-profile-cm-mode-included-/ All the UI problems are resolved. The white spots and the missing UI have nothing to do one with the other. The missing UI is in-fact a bug in Nvidia driver (it appears without any HelixFix)... The profile there was manually tested and hand-picked to SOLVE all the issues with the original profile...
said:
said:@SKAUT, that doesn't seem to happen for me on the save Losti posted. I think I recall Helifax saying that setting StereoCutOff to 0 in the driver profile would fix some issue like (FWIW I have *NOT* set that to 0).

I'll likely post a new alpha a little later tonight, so you can check if it still occurs then.

I didn`t have that on previous fix versions so i thought that white spots are some kind of fullscreen transparent shader which covers up that whole UI.
I`l wait for another fix and check if that will change.


No no no,
USE THIS PROFILE: https://forums.geforce.com/default/topic/841696/the-witcher-3-correct-3d-vision-nvidia-profile-cm-mode-included-/


All the UI problems are resolved. The white spots and the missing UI have nothing to do one with the other.
The missing UI is in-fact a bug in Nvidia driver (it appears without any HelixFix)...

The profile there was manually tested and hand-picked to SOLVE all the issues with the original profile...

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)

Posted 06/20/2015 05:12 PM   
[quote=""]@kazuma6666 you would be better off waiting until the fix is ready - when it is we will post detailed instructions on the blog. I wouldn't recommend reading through this thread as a lot of the information will already be out of date. I haven't heard anyone mention having issues with the Steam overlay on this game. Might have been an issue with recent drivers, but bo3b made sure that 3Dmigoto would work fine with the overlay. Game updates are usually fine, but occasionally cause issues. Since we are still developing the fix, you should keep up to date as we are, and generally the updates have only improved things. As a rule of thumb, fixes are installed by extracting them into the game directory, such that the d3d11.dll ends up in the same place as the game's executable (in this case under bin\x64). There are two versions of the fix that use different wrappers - both should be equivalent, but some people find one works better than the other on a certain OS, though this has improved considerably in the last few versions of 3Dmigoto. Hairworks is only a hot topic right now as it's the effect I'm currently concentrating on. The worst part of it is now fixed (wait for the next update) - I'm still looking into the second issue with it.[/quote] Thanks for the info. Good luck with the fix, it seems to be quite a bit of work.
said:@kazuma6666 you would be better off waiting until the fix is ready - when it is we will post detailed instructions on the blog. I wouldn't recommend reading through this thread as a lot of the information will already be out of date.

I haven't heard anyone mention having issues with the Steam overlay on this game. Might have been an issue with recent drivers, but bo3b made sure that 3Dmigoto would work fine with the overlay.

Game updates are usually fine, but occasionally cause issues. Since we are still developing the fix, you should keep up to date as we are, and generally the updates have only improved things.

As a rule of thumb, fixes are installed by extracting them into the game directory, such that the d3d11.dll ends up in the same place as the game's executable (in this case under bin\x64). There are two versions of the fix that use different wrappers - both should be equivalent, but some people find one works better than the other on a certain OS, though this has improved considerably in the last few versions of 3Dmigoto.

Hairworks is only a hot topic right now as it's the effect I'm currently concentrating on. The worst part of it is now fixed (wait for the next update) - I'm still looking into the second issue with it.


Thanks for the info. Good luck with the fix, it seems to be quite a bit of work.

Posted 06/20/2015 05:41 PM   
  72 / 152    
Scroll To Top