Search results

You don't take physical damage either. Basically, the game sees the damage that endrega/arachas deals as purely poison damage. This shouldn't be the case. They do physical attacks which will proc poison. I'm 99.9% certainthis is a bug

Bug - With 100% poison resist armor, you take 0 damage from all types of Endrega and Arachas Proof - http://gfycat.com/SelfreliantDigitalBaiji

I have a GTX 970. On 1.03, I would get a completely stable 60 FPS in the main square in Novigrad. It would dip to like 58 when I first loaded the area, but only for a split second. Now, after updating to 1.04, I get like 50-52 fps in Novigrad at the same location and my GPU runs 5-10 C hotter...

The graphics look worse, I get 5-10 less FPS in some places where I used to get a completely stable 60, and my 970 runs 5-10 C hotter than 1.03. I will NEVER install a patch again until I wait to see what it does to the game. I installed 1.04, then played for a couple of hours. Now if I want...

Try this. Helped me a bit. I was getting a perfect 60 fps in Novigrad at the market since release. As soon as I installed 1.04 my fps went from 60 to 50-52. My temperatures are also ~5-10 C hotter. This helped a bit though. My frames are pretty much back to normal but the temps are still really...

I noticed the same thing with my 970 after patch 1.04. Try this. Navigate to C:\Users\YourUserName\Documents\The Witcher 3\user.settings.ini Find "TextureMipBias=-1" and change it to "TextureMipBias=0" save it.

Same here. Earlier today on 1.03 (and since launch) my 970 was getting a completely stable 60 fps in the market in Novigrad. It would drop to like 58 when I first loaded into the area but only for a split second. Now if I look around it's around 50-52 FPS, AND my temperatures are 5-10 degrees...

My GTX 970 is also running 5-10 C hotter than before 1.03 earlier today.

[FX 8350, GTX 970] I completely fixed my crashing issue + get a completely stable 60 FPS. ~20 hours with zero crashes I'm cross posting my reddit post. Sorry if there are any formatting issues. Okay so since I started playing on Monday night my game has been plagued with crashes and freezes...

Hurrrrrrrrr Hurrrrrr. Overheating? Are you kidding me? Hundreds if not thousands of people are reporting this. They're all overheating? My 970 doesn't go over 65C, CERTAINLY NOT OVERHEATING BUT I HAVE THE SAME PROBLEM

I have a 970. This didn't work for me either. It was one of the first things I tried.

bump ---------- Updated at 08:45 AM ---------- I have a GTX 970. Setting my power management setting to maximum performance did NOT fix the issue.

I had the same problem. Roll back your Nvidia drivers to 350.12 (the GTA V driver). Fixed it completely for me.

Rolling back the my nvidia driver fixed this completely for me. I had the latest one (352.86) and rolled back to the GTA V driver (350.12).

I would NOT install it. Keep the GTA V driver (350.12). Myself and many other were having crashes to desktop with the new driver. I rolled back to the GTA V driver and it fixed my crashes completely.

Roll back your driver to 350.12 (GTA V driver). Fixed my crashing problems. Go to your device manager (windows + R, type in devmgmt.msc and hit enter). Under display adapters right click your adapter and choose properties. Under driver tab select roll back driver.

I was able to fix my crashing problem! (FX 8350 GTX 970 G1) I was having issues with CTD. Wasn't getting an error message or anything. The game would just minimize, my monitor would flicker, and then it would close. I tried a bunch of stuff but finally found the culprit. It seems to be the...

Fixed it!!!!!!!! I rolled back my nvidia driver to 356.12. No more crashes!! =D

I tried capping my framerate to 30 and running in fullscreen and borderless, to no avail.I just rolled my graphics driver back to 356.12, will update if it fixes the issue.

My Gigabyte 970 G1 hits 70 C. If it runs too hot, cap your frames at 30. I know it's not ideal but it still looks amazing and you can max out all the graphics settings without worrying about overheating, at least until this is fixed.