It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

×
arrow-down2arrowcart2close4fat-arrow-leftfat-arrow-rightfeedbackfriends2happy-facelogo-gognotificationnotifications-emptyownedremove-menusad-facesearch2wishlist-menuwishlisted2own_thingsheartstartick
avatar
anatomy2k12: I saw someone else had the problem on Gamefaqs forum, I do as well.

ESC (key) doesn't work on Inventory (i) or Skill Tree (c). You have to click back/exit every time. ESC does work for pausing the game and navigating the load/save/exit screen.
And you are sure this is not caused by some kind of mod-incompatibility? It's a common symptom when mods like Better Combat or Panel Tweaks are out of date. I'm just grasping for straws, here. :)
A few bugs I ran into with 2.0:

1.
Problem:
Last bomb used has no effect. Very problematic in arena as bombs are expensive.

Procedure:
Start a new game, equip and use your samum bombs until you have 1 left and then use the last one on a group of enemies. Notice that all recieve 0 damage and never get stunned.

Workaround:
Simply do not use your last bomb of any type of bomb that you want to use.


2.
Problem:
Poisoned harpy claw and sting throwing daggers never inflict their critical effects.

Procedure:
Play arena, purchase some and use on enemies that can be poisoned/freezed.

Workaround:
To not use those daggers, unfortunately.


3.
Problem:
Throwing daggers seem to miss even when they're aimed perfectly.

Procedure:
Purchase around 10 rusty throwing daggers in arena and test this on any enemy.

Workaround:
It seems random.

4.
Problem:
Damage caused by throwing daggers does not appear in the combat log.

Procedure:
Purchase rusty throwing daggers in arena and test this on any enemy.
@talrave: do those only occur in Arena mode, or also when playing the main storyline?
avatar
Kibou: @talrave: do those only occur in Arena mode, or also when playing the main storyline?
Arena and story mode as well
Here's one bug, not gamebreaking though.

http://youtu.be/CvcuIV8H1Xo
@talrave: Your bug 1 and 2 have been added to the detailed descriptions, bug 4 to the short descriptions. Thanks for your reports!
About #3: I guess this one occurs when aiming manually (holding the button down until the crosshair appears)?

@Lovag: Thanks for the video. Which location is this? The camp of the Nilfguardians in act 3?


Can anyone confirm whether the bugs from the current list still occur in version 2.0?
Post edited November 03, 2011 by Kibou
avatar
Kibou: @Lovag: Thanks for the video. Which location is this? The camp of the Nilfguardians in act 3?
Yorveth's path, act 3, sewers just before you decide whether to go save Triss or take Phillipa to Yorveth.

By the way I have a save just before entering that room so I can reproduce this bug whenever I want. Here's the save if you want to try it out: http://min.us/lbrdXWH1qmPPgl

edit: and sometimes only one guard stays still while two attack.
Post edited November 03, 2011 by Lovag
I added the bug to the short descriptions.

iirc, I encountered the same bug once, too. It was a different location (the big fight in the Nilfguardian camp, where some commander sends waves of soldiers at you), but it was also a Nilfguardian soldier. He just stood there, did nothing and ignored being attacked.
avatar
Kibou: I added the bug to the short descriptions.

iirc, I encountered the same bug once, too. It was a different location (the big fight in the Nilfguardian camp, where some commander sends waves of soldiers at you), but it was also a Nilfguardian soldier. He just stood there, did nothing and ignored being attacked.
Yeah, now that you say it, that happened to me too, exactly there. It also happened in the Nilfgaardean camp in Act 2 (Yorveth's path)
In the prologue, during the last memory Foltest asks Geralt if it's possible to tame a Dragon. Geralt is supposed to answer "Not as far as I know" but every time I've played it since 2.0 he says something different (something like "people like him <something>". The subtitles still show up correctly though.
Only with AMD Crossfire: No targetting reticule/health bar when attacking/interacting with certain NPCs

Problem: When your graphics card is running on AMD Crossfire technology, no targetting reticule and health bar appears when fighting certain enemies (e.g. Endregas, Wraiths,...) and interacting with such NPCs (like at the end of In the Claws of Madness) is impossible as well.
Procedure: Just have an AMD Crossfire card and the latest drivers installed.
Workaround: Rerolling to CAP2 11.6 seems to be a solution, but this screws over other games and general Witcher 2 performance.
Thread: CAP problems In the Claws of Madness bug
Status: The issue was fixed in a CAP release by AMD some months ago, but either they accidently rerolled it in newer CAPs or the 2.0 patch broke it again.
Post edited November 11, 2011 by Kangaxx
avatar
Kangaxx: Only with AMD Crossfire: No targetting reticule/health bar when attacking/interacting with certain NPCs

Problem: When your graphics card is running on AMD Crossfire technology, no targetting reticule and health bar appears when fighting certain enemies (e.g. Endregas, Wraiths,...) and interacting with such NPCs (like at the end of In the Claws of Madness) is impossible as well.
Procedure: Just have an AMD Crossfire card and the latest drivers installed.
Workaround: Rerolling to CAP2 11.6 seems to be a solution, but this screws over other games and general Witcher 2 performance.
Thread: CAP problems In the Claws of Madness bug
Status: The issue was fixed in a CAP release by AMD some months ago, but either they accidently rerolled it in newer CAPs or the 2.0 patch broke it again.
What the deuce? So that explains it. Crossfire turns out to be more a curse than a blessing.
Post edited November 12, 2011 by Lovag
@kyrieee: I've added your bug to the short bug descriptions / campaign specific list, thanks for reporting.

@Kangaxx: If I understand correctly, this issue is related to crossfire drivers rather than the game, or did pre-2.0 versions of the Witcher 2 run fine with the most recent drivers?
avatar
Kibou: @talrave: Your bug 1 and 2 have been added to the detailed descriptions, bug 4 to the short descriptions. Thanks for your reports!
About #3: I guess this one occurs when aiming manually (holding the button down until the crosshair appears)?

@Lovag: Thanks for the video. Which location is this? The camp of the Nilfguardians in act 3?


Can anyone confirm whether the bugs from the current list still occur in version 2.0?
I've ran a few more tests regarding the issue with throwing daggers missing randomly and concluded that they consistently miss only against 2 enemies - scoia'tael archers and dwarf archers - and only when they're using their bows. They're also the only archers which sometimes block your first sword attack instantly when you engage them in melee.
avatar
Kibou: @kyrieee: I've added your bug to the short bug descriptions / campaign specific list, thanks for reporting.

@Kangaxx: If I understand correctly, this issue is related to crossfire drivers rather than the game, or did pre-2.0 versions of the Witcher 2 run fine with the most recent drivers?
It ran fine when I completed the game. I came back to try out 2.0 some weeks ago, and it was broken again. I have newer drivers installed compared to when I completed the game ofcourse, so it's hard to say. I've read that rolling back to older drivers can fix it again though, so it's probably the newer drivers that broke it again. I hope CD Projekt RED and AMD can work together to fix it again.
Post edited December 30, 2011 by Kangaxx