Actually there are a few, I think the longest one is this:
http://www.gog.com/en/forum/the_witcher_2/what_would_you_like_fixed_changed_in_tw2_bug_posting_also_welcome/page1

@Other Threads: It's right that there are some other threads that list bugs, but I think this is the only one that tries to provide proper bug descriptions, so I think it still has it's benefits.

I'll start to inlcude links to other bug lists in the main post, for easy reference.

I don't know if there is separate thread for Loredo's House issue, couldn't find one.
Happens with different sound cards. I have Asus Xonar, my friend integrated Realtek, third person's audio card is unknown to me. I was at Loredo's House only as a part the story, my choices did not really give me a chance to to there more than once.

As for distorted sound issue - yes, it looks like drop in FPS combined with sound distorted. Very weird and quite hard to describe tbh. This is easy fixed with going to menu and back to game.

Haven't tried 1.1 again yet. I've had a reply from tech support to try 1.2 which I will do when I come back from holidays.

If their in a pocket I don't think quantity shows up unless you move em back to your inventory... thought it was a "feature"

Gaming Life would be wonderful if we all thought about bugs as features!! :p

@Ch3rub I have good news. I patched the game with 1.2 version and played for about 6 hours in total -> no crashes, not even single one. Imo there is a high chance that they won't occur for you as well.

here is my bug:

http://www.gog.com/en/forum/the_witcher_2/i_cant_meditate_bug_it_is_a_bug_as_its_not_story_event_and_wont_work_ever/page1

it is still fixed with 1.2 patch

I meant to say it is still unfixed

Using the Steam version here (had to dload another 9 gb for 1.2... nice) and the game will CTD only after a few minutes of playing. This happens with a 1.1 save and with a new game. No such problems with 1.1...

EDIT:nvm I reset my config and the problem is gone

@lagunareturns: I've added the bug to the list. Did you encounter similar reports from other people? The link someone posted in your thread rather seems to be about the "input not recognized" problem than about your specific problem. Would be interesting to know if the problem occurs at different location for other people, or always at the one you described.


Status of Bugs in Patch 1.2 ?

Any information about the "input not being recognized" or the "Sound permanently gone after visiting Loredo's House" issues in version 1.2? Have they been fixed?
How does 1.2 work for you concerning stability? Did the frequency of crashes decrease? For me, the ratio of entirely random crashes seems to have decreased, but now the game seems to crash rather often when performing a quicksave (F5 key), like every 5th to 10th time. Did someone else make the same observation?

Hotkeys don't work. Hotkeys don't work . Hotkeys don't work. Hotkeys don't work.

No...they don't work. :(

Please fix it, CDPR. This is almost game breaking.

What's up with that?? Usually steam has been good to me...Luckily I bought the GOG version AND a NEW $350 video card and oh yea a custom built i7 computer Overclocked in anticipation of this game!! Not that many problems yet!! Too bad the game(as great as some of it is) isn't better polished ...the transitional scenes lose the RPG element like everythings been rushed ...mostly a cartoonic comic storyboard effect?? And the caught in the middle of cutscenes so that you have to be clarivoyant so you can't use potions SUCKS!!
Bottomline: The BEST RPG ever!! Sincerely, use tobe a fanboy!!

Valve is making some adjustments to its delivery system mainly because of this Witcher 2 debacle (I'm using the latest beta client and they have already started the groundwork for the new system). So hopefully this was the last time I had to download 18 gigs of patches in less than two weeks :)

For the "controls stop working" bug, it may be worth a try to uninstall all manufacturer-specific drivers for your keyboard and mouse, along with all tools (e.g. Logitech Setpoint) and use Windows' default mouse/keyboard drivers instead.

I'm already using the default drivers.