Combat Crashes with AMD R9 285

+
Maybe. But it help. Game dont crash for me ,already 2h in game.
maybe you dont have in combat crit dmg 500+ :) after 500dmg game crach 100% :)

i try this yesterday and crach too

AMD not yet make 15,5 driver :) we weit too :)
 
Last edited:
Same issue with same card as everyone above here so no need to repeat same old for me.

Combat crashes when attacking/killing enemies with the AMD R9 285. Cannot even make it past the quest in the cave when fighting the wild hunt for the first time.
 
Same here crashing during combat. tried multiple things
1. Changed display modes, tried all
2. Change fps form 60 to unlimited
3. Used beta driver and tried the latest stable
4. Run as Administrator
5. for GOG, Rename galaxy.dll

Nothing helped, still crashing on combat every time during
*SPOILER BEGIN*
B0TChlinG combat
*SPOILER END*
 
[h=3]Will be testing 1.04 right now.

The Witcher 3: Wild Hunt - Patch 1.04 changelog:[/h]
  • Rebinding any key is now available after switching Unlock Bindings option in Options \ Key bindings submenu.
  • Corrects an issue in the dialog system that might rarely cause dialog looping in scenes.
  • Fixes an issue with incorrect behavior of Wild Hunt warriors after they were under the influence of Axii sign.
  • Corrects a bug causing spontaneous combustion of gas clouds.
  • 1280 x 720 resolution is now properly displaying as valid resolution option.
  • Fixes boat stuttering in cutscenes.
  • Texture rendering quality for high / ultra presets improved.
  • Further improvements in NVIDIA Hairworks performance.
  • A few additional Gwent cards are now available in the Prologue area.
  • Fixes an issue where users with usernames using non-latin characters were unable to import saves from Witcher 2.
  • Overall stability and performance improvements.
  • Fixes related to alt + tabbing and minimizing game window.
  • Game icon updated.
  • Enlarges the size of the loot pop-up window in the UI.
  • Fixes an issue where, in certain circumstances, the comparison window could be displayed outside of game borders in the UI.
  • Upgrading set items no longer destroys sockets.
  • Small UI tweaks for Gwent.
  • Corrects some missing translations in localized versions.
 
Last edited:
It should have a thing that says changelog on it. Ill post it when I get done dl-ing it.

---------- Updated at 02:27 PM ----------

The Witcher 3: Wild Hunt - Patch 1.04 changelog:
Rebinding any key is now available after switching Unlock Bindings option in Options \ Key bindings submenu.
Corrects an issue in the dialog system that might rarely cause dialog looping in scenes.
Fixes an issue with incorrect behavior of Wild Hunt warriors after they were under the influence of Axii sign.
Corrects a bug causing spontaneous combustion of gas clouds.
1280 x 720 resolution is now properly displaying as valid resolution option.
Fixes boat stuttering in cutscenes.
Texture rendering quality for high / ultra presets improved.
Further improvements in NVIDIA Hairworks performance.
A few additional Gwent cards are now available in the Prologue area.
Fixes an issue where users with usernames using non-latin characters were unable to import saves from Witcher 2.
Overall stability and performance improvements.
Fixes related to alt + tabbing and minimizing game window.
Game icon updated.
Enlarges the size of the loot pop-up window in the UI.
Fixes an issue where, in certain circumstances, the comparison window could be displayed outside of game borders in the UI.
Upgrading set items no longer destroys sockets.
Small UI tweaks for Gwent.
Corrects some missing translations in localized versions.

---------- Updated at 02:36 PM ----------

Did not work for me....froze during a witcher contract in valen.

Im seriously getting mad now, I get that games should be buggy but its like they aren't even acknowledging it aside form a twitter post.
 
Crashed in combat 5 minutes after downloading the 1.04 patch, they really need to fix this problem with the AMD R9 285, and offer us some compensation.
 
Same for Sapphire R9 285. Works without problems on my Windows 10 partition though. Not sure if its related to W10 or the experimental driver that I'm using. I'll try with the public driver sometime.
 
Top Bottom