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 or Opera

×
Anyone else having problem with the xbox controller?

Before the patch it was working perfectly fine but now you cant use the analog sticks to scroll journals or change signs...
Having the same issue.
I can't choose signs with the analog stick.

Dpad works though,

Can't scroll journal logs though.

Annoying, as I rely on that to help me with quests.
Yep - seems like this is true for most if not all people using a 360 gamepad.

I'm just reinstalling 1.0 until it's fixed.
Steam just downloaded a 9gb file..to install this patch. I don't know if I can download everything again lol
Yeah the patch broke it. They will fix it. What a lame thing to break.
Post edited May 26, 2011 by BakedGoods
We finally released patched 1.1. We are very sorry for the delays, but as you can see there are many versions of the game and we had to test each very carefully without using a gamepad. Fixed
When you say Fixed do you mean the controller issue is fixed now?
avatar
ash4: When you say Fixed do you mean the controller issue is fixed now?
It is sarcasm. I just added to the original statement on their homepage. Just as frustrated as you guys. Had no problems with original release except Y axis inversion, which was corrected by editing. Can't simply edit an ini file in this post patch problem as far as I could tell. Hope they or more likely someone else will find a solution.
avatar
pdrey: Hope they or more likely someone else will find a solution.
This - I mean, I would think this wouldn't be terribly difficult to fix, but who knows. I reverted to 1.0 - here's a screenshot of my Input_QWERTY.ini from the Documents/Witcher 2/Config folder - maybe somebody can spot any differences between this and the 1.1 config.

If not the solution must be more complicated than just editing the .ini files.
Attachments:
Post edited May 27, 2011 by Adam192
avatar
pdrey: Hope they or more likely someone else will find a solution.
avatar
Adam192: This - I mean, I would think this wouldn't be terribly difficult to fix, but who knows. I reverted to 1.0 - here's a screenshot of my Input_QWERTY.ini from the Documents/Witcher 2/Config folder - maybe somebody can spot any differences between this and the 1.1 config.

If not the solution must be more complicated than just editing the .ini files.
I backed up retail input ini's before patching. Pasting them back into Config folders made no difference. Same problem. They rushed this performance patch.
hope they can give a quick hotfix :/ bah its the weekend too
For those of you who reverted to 1.0, how were you able to do it? I have the retail version and have tried reinstalling twice, and each time it's updated automatically to 1.1.
Post edited May 27, 2011 by Aspenwood
avatar
Aspenwood: For those of you who reverted to 1.0, how were you able to do it? I have the retail version and have tried reinstalling twice, and each time it's updated automatically to 1.1.
Will try it if they don't fix gamepad issue and other minor problems post patch. Try to install without connected to internet and apply the fist Patcher_ATARI.exe from 5/17. Also replace Witcher2.exe and paul.dll so you get performance back.. Only problem I can see is DLC. Apparantly has to be v1.1 for dlc to work? And maybe an activation issue. Don't know ..have to try all this myself first...but will wait for a fix first...maybe.
avatar
Aspenwood: For those of you who reverted to 1.0, how were you able to do it? I have the retail version and have tried reinstalling twice, and each time it's updated automatically to 1.1.
avatar
pdrey: Will try it if they don't fix gamepad issue and other minor problems post patch. Try to install without connected to internet and apply the fist Patcher_ATARI.exe from 5/17. Also replace Witcher2.exe and paul.dll so you get performance back.. Only problem I can see is DLC. Apparantly has to be v1.1 for dlc to work? And maybe an activation issue. Don't know ..have to try all this myself first...but will wait for a fix first...maybe.
Did it get fixed? :S