[quote="ZlothX"]Looks like messereciccio's problem is my problem, too, and I've got plenty of time for a binary search. It's d90496f029191acd-vs_replace that's killing me in the game's starting room. Delete the txt and bin file and my game runs fine.
I've got my screenshot key bound to keypad 0. When I use it in Witcher 3 I'm getting green text at the top and bottom. Is that something from 3Dmigoto?[/quote]
I fail to understand why that shader would crash things as is a water shader... especially in the initial rooms, but whatever...
What hardware and settings are you running the game on exactly?
ZlothX said:Looks like messereciccio's problem is my problem, too, and I've got plenty of time for a binary search. It's d90496f029191acd-vs_replace that's killing me in the game's starting room. Delete the txt and bin file and my game runs fine.
I've got my screenshot key bound to keypad 0. When I use it in Witcher 3 I'm getting green text at the top and bottom. Is that something from 3Dmigoto?
I fail to understand why that shader would crash things as is a water shader... especially in the initial rooms, but whatever...
What hardware and settings are you running the game on exactly?
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
Maybe some water outside that window? Anyway...
GTX 780 (not TI), 368.39 drivers, Windows 10 64-bit, 16GB memory, i7 6700K CPU. Just one ASUS 3D monitor running at 1080p. I just ran GeForce Experience to see what version it is and it went and updated itself but it should have been pretty near up-to-date. (I don't let it optimize my games. I haven't even let it scan!) No overclocking on anything.
P.S. Figured out the numpad 0 thing.
GTX 780 (not TI), 368.39 drivers, Windows 10 64-bit, 16GB memory, i7 6700K CPU. Just one ASUS 3D monitor running at 1080p. I just ran GeForce Experience to see what version it is and it went and updated itself but it should have been pretty near up-to-date. (I don't let it optimize my games. I haven't even let it scan!) No overclocking on anything.
P.S. Figured out the numpad 0 thing.
The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering.
I'm on 358.87 drivers, latest version of the game, single evga 780 sc, i5-4670k previously overclocked now on default clock (crashed all the same), 8 gb ram, Samsung SSD, Asus maximus gene VII, Eizo FG2421, win 10 pro 64 bit, tried both ultra and lowest settings, also tried to change single settings like hairworks on/off to no avail, no GeForce experience, no steam overlay nor other overlays, no fps counter of any kind
I'm on 358.87 drivers, latest version of the game, single evga 780 sc, i5-4670k previously overclocked now on default clock (crashed all the same), 8 gb ram, Samsung SSD, Asus maximus gene VII, Eizo FG2421, win 10 pro 64 bit, tried both ultra and lowest settings, also tried to change single settings like hairworks on/off to no avail, no GeForce experience, no steam overlay nor other overlays, no fps counter of any kind
Great legwork on finding that shader, thanks.
Helifax- that shader is not included in the list of shaders you published to GitHub: https://github.com/bo3b/3Dmigoto/tree/master/Witcher3/Helifax_Update_1.21
It's also super weird that a VS would crash the game. A CS I could see, but VS? I don't see anything even remotely special about that VS code.
Maybe it was not intended to be part of the shipped fix?
If I comment out the correction at the bottom, like:
[code]// float4 stereo = StereoParams.Load(0);
// o2.x += stereo.x *(o2.w - stereo.y);
// o0 = 0;
[/code]
Then, I get identical code when recompiled with fxc.
There is one glitch with the output where o0 is defined as float4, and should be float2. Setting it to zero should be OK, I would not expect a pipeline error because of any of that.
@ZlothX, @messereciccio, please try commenting out those three lines at the bottom of the shader (with //), to see if that fixes the crash. It's an unusual situation. And maybe try changing the "out float4 o0" to "out float2 o0" in the declaration section.
Thanks for helping us narrow this down, as it's very difficult when we aren't seeing the crash.
Then, I get identical code when recompiled with fxc.
There is one glitch with the output where o0 is defined as float4, and should be float2. Setting it to zero should be OK, I would not expect a pipeline error because of any of that.
@ZlothX, @messereciccio, please try commenting out those three lines at the bottom of the shader (with //), to see if that fixes the crash. It's an unusual situation. And maybe try changing the "out float4 o0" to "out float2 o0" in the declaration section.
Thanks for helping us narrow this down, as it's very difficult when we aren't seeing the crash.
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
Hi bo3b,
I forgot to push the latest shaders on github. That shader needs the oO set to zero as it creates strange and weird ripples on some water surfaces. This wasn't before patch 1.21 and is something they introduces.
It renders pretty bad as well so I decided to disabled it altogether.
Even if I correct it, it still looks strange;)
I pushed all the shaders to github now. Is very strange though that I didn't had the game crashing on either my PCS and it seems to work fine for everyone else.
Edit: o0 should be o0 = 0. for that shader. One thing I can do is to remove the shader but skip it in the ini file;) Maybe this will fix the crash while maintaining the same result;)
Hi bo3b,
I forgot to push the latest shaders on github. That shader needs the oO set to zero as it creates strange and weird ripples on some water surfaces. This wasn't before patch 1.21 and is something they introduces.
It renders pretty bad as well so I decided to disabled it altogether.
Even if I correct it, it still looks strange;)
I pushed all the shaders to github now. Is very strange though that I didn't had the game crashing on either my PCS and it seems to work fine for everyone else.
Edit: o0 should be o0 = 0. for that shader. One thing I can do is to remove the shader but skip it in the ini file;) Maybe this will fix the crash while maintaining the same result;)
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
Updated the fix and changed the way that shader is handled.
This should prevent the crashing now.
Same LINK.
Please give it a try and see if it still crashes;)
Cheers!
Updated the fix and changed the way that shader is handled.
This should prevent the crashing now.
Same LINK.
Please give it a try and see if it still crashes;)
Cheers!
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
I'm not real sure how to get from GitHub but I copy/pasted every .txt file that changed today plus the .ini file and ran. It seemed to be working fine from my save file.
I'm afraid I need to hop on a plane now so messereciccio will need to take over for a bit.
P.S. There is a stream outside that window, waaaaay down in the valley.
I'm not real sure how to get from GitHub but I copy/pasted every .txt file that changed today plus the .ini file and ran. It seemed to be working fine from my save file.
I'm afraid I need to hop on a plane now so messereciccio will need to take over for a bit.
P.S. There is a stream outside that window, waaaaay down in the valley.
The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering.
[quote="ZlothX"]I'm not real sure how to get from GitHub but I copy/pasted every .txt file that changed today plus the .ini file and ran. It seemed to be working fine from my save file.
I'm afraid I need to hop on a plane now so messereciccio will need to take over for a bit.
P.S. There is a stream outside that window, waaaaay down in the valley.[/quote]
The archive on HelixMod has been updated also. No need to take the files from Github, but ofc you are welcome if you want to get them from there;)
ZlothX said:I'm not real sure how to get from GitHub but I copy/pasted every .txt file that changed today plus the .ini file and ran. It seemed to be working fine from my save file.
I'm afraid I need to hop on a plane now so messereciccio will need to take over for a bit.
P.S. There is a stream outside that window, waaaaay down in the valley.
The archive on HelixMod has been updated also. No need to take the files from Github, but ofc you are welcome if you want to get them from 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
Something else though, an issue on many games, convergence (which I like to increase to get doll effect) seems to switch back to some default setting, after a loading screen (or lengthy cutscene) I don't know if other people have this issue, I also have it with Metal Gear Solid Rising Vengeance
Something else though, an issue on many games, convergence (which I like to increase to get doll effect) seems to switch back to some default setting, after a loading screen (or lengthy cutscene) I don't know if other people have this issue, I also have it with Metal Gear Solid Rising Vengeance
Your driver is busted...
Make a DDU clean and install the driver + swap the profile as explained on HelixBlog.
Also the fix comes with a CONVERGENCE preset on the "Z" key that can be changed from the ini file.
(You aren't one of those people who don't read but like to complain hopefully ^_^).
Your driver is busted...
Make a DDU clean and install the driver + swap the profile as explained on HelixBlog.
Also the fix comes with a CONVERGENCE preset on the "Z" key that can be changed from the ini file.
(You aren't one of those people who don't read but like to complain hopefully ^_^).
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 some testing with the new fix by Helifax and no crashes. Well, actually I had a couple of crashes tbh, but they appeared to be random, and I just received my 2nd 780 so I'm on a SLI system now, thus maybe it was because of that. Cheers to this wonderful community ;)
Did some testing with the new fix by Helifax and no crashes. Well, actually I had a couple of crashes tbh, but they appeared to be random, and I just received my 2nd 780 so I'm on a SLI system now, thus maybe it was because of that. Cheers to this wonderful community ;)
[quote="messereciccio"]Did some testing with the new fix by Helifax and no crashes. Well, actually I had a couple of crashes tbh, but they appeared to be random, and I just received my 2nd 780 so I'm on a SLI system now, thus maybe it was because of that. Cheers to this wonderful community ;)[/quote]
i have SLI GTX980TI G1 (surround) and have the same random CTD (30-45 min aprox). Any suggestions?
- use DDU for reinstall drivers.
- use serveral versions of drivers for test and currently use last drivers.
- Windows 7/10 the same problem.
thanks ;)
messereciccio said:Did some testing with the new fix by Helifax and no crashes. Well, actually I had a couple of crashes tbh, but they appeared to be random, and I just received my 2nd 780 so I'm on a SLI system now, thus maybe it was because of that. Cheers to this wonderful community ;)
i have SLI GTX980TI G1 (surround) and have the same random CTD (30-45 min aprox). Any suggestions?
- use DDU for reinstall drivers.
- use serveral versions of drivers for test and currently use last drivers.
- Windows 7/10 the same problem.
thanks ;)
i7 4970k@4.5Ghz, SLI GTX1080Ti Aorus Gigabyte Xtreme, 16GB G Skill 2400hrz, 3*PG258Q in 3D surround.
I fail to understand why that shader would crash things as is a water shader... especially in the initial rooms, but whatever...
What hardware and settings are you running the game on exactly?
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)
GTX 780 (not TI), 368.39 drivers, Windows 10 64-bit, 16GB memory, i7 6700K CPU. Just one ASUS 3D monitor running at 1080p. I just ran GeForce Experience to see what version it is and it went and updated itself but it should have been pretty near up-to-date. (I don't let it optimize my games. I haven't even let it scan!) No overclocking on anything.
P.S. Figured out the numpad 0 thing.
The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering.
-- Doctor Who, "Face of Evil"
Helifax- that shader is not included in the list of shaders you published to GitHub: https://github.com/bo3b/3Dmigoto/tree/master/Witcher3/Helifax_Update_1.21
It's also super weird that a VS would crash the game. A CS I could see, but VS? I don't see anything even remotely special about that VS code.
Maybe it was not intended to be part of the shipped fix?
If I comment out the correction at the bottom, like:
Then, I get identical code when recompiled with fxc.
There is one glitch with the output where o0 is defined as float4, and should be float2. Setting it to zero should be OK, I would not expect a pipeline error because of any of that.
@ZlothX, @messereciccio, please try commenting out those three lines at the bottom of the shader (with //), to see if that fixes the crash. It's an unusual situation. And maybe try changing the "out float4 o0" to "out float2 o0" in the declaration section.
Thanks for helping us narrow this down, as it's very difficult when we aren't seeing the crash.
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
I forgot to push the latest shaders on github. That shader needs the oO set to zero as it creates strange and weird ripples on some water surfaces. This wasn't before patch 1.21 and is something they introduces.
It renders pretty bad as well so I decided to disabled it altogether.
Even if I correct it, it still looks strange;)
I pushed all the shaders to github now. Is very strange though that I didn't had the game crashing on either my PCS and it seems to work fine for everyone else.
Edit: o0 should be o0 = 0. for that shader. One thing I can do is to remove the shader but skip it in the ini file;) Maybe this will fix the crash while maintaining the same result;)
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)
This should prevent the crashing now.
Same LINK.
Please give it a try and see if it still crashes;)
Cheers!
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'm afraid I need to hop on a plane now so messereciccio will need to take over for a bit.
P.S. There is a stream outside that window, waaaaay down in the valley.
The very powerful and the very stupid have one thing in common. Instead of altering their views to fit the facts, they alter the facts to fit their views ... which can be very uncomfortable if you happen to be one of the facts that needs altering.
-- Doctor Who, "Face of Evil"
The archive on HelixMod has been updated also. No need to take the files from Github, but ofc you are welcome if you want to get them from 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)
i7 - Nvidia 780ti - Nvidia 3DTV - Optoma HD33 - 100" screen + Panasonic Viera TX-P46GT30E
Make a DDU clean and install the driver + swap the profile as explained on HelixBlog.
Also the fix comes with a CONVERGENCE preset on the "Z" key that can be changed from the ini file.
(You aren't one of those people who don't read but like to complain hopefully ^_^).
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 SLI GTX980TI G1 (surround) and have the same random CTD (30-45 min aprox). Any suggestions?
- use DDU for reinstall drivers.
- use serveral versions of drivers for test and currently use last drivers.
- Windows 7/10 the same problem.
thanks ;)
i7 4970k@4.5Ghz, SLI GTX1080Ti Aorus Gigabyte Xtreme, 16GB G Skill 2400hrz, 3*PG258Q in 3D surround.