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

×
avatar
Galadh: Do you think it's possible to include another quests in already existing environment? Bear in mind there are a few not-really-used locations like bandits hut/cabin in Act I, northwards from Troll and I guess they could extend something in Act III.
Haven't reached the DLC part yet. But I can easily see how they can add more quests, one that comes to mind is something akin to the royal hunter and boss monsters in TW1.
avatar
Galadh: Don't see much talking nor excitement towards new side-quest? Disappointed?
No no no no no.

It's awesome, but you can't really "talk" about it because you'd give away the best part :)
[url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url]
avatar
KenR7A: Can anyone confirm if we 16:10 users LOST fov horizontally just to GAIN pixels in the vertical?
Unfortunately this is true. As you say, 16:10 users have now used all the pixels on screen, however the FOV is less and we have hor- (as in to say that this widescreen mode shows less of the horizontal field of view.

Ideally, we would want 16:10 to be vert+ (as in the same FOV as 16:9 but with extra rendering at the top and bottom.

Its a little lazy, and disapointing, but I have set my config to be 1920x1080 as the extra FOV (or proper FOV) gives a better view to the game world. Screens attached. You can see that the 1920x1200 is just the 1920x1080 screen but with the sides lopped off to give the correct aspect ratio. Oh well, played enough on 16:9 so will continue to...

On the plus side, Crossfire performance seems to be better, though this is subjective at the moment. Maybe a placebo as I read it in the release notes.

Also, as mentioned by others, remove all mods. I didn't and my 360 pad wasnt working in the quickmenu, but removing a compass mod made everything fine again. Guess I'll just have to wait until they get re-released.
Attachments:
1920x1080.jpg (305 Kb)
avatar
vAddicatedGamer: Haven't reached the DLC part yet. But I can easily see how they can add more quests, one that comes to mind is something akin to the royal hunter and boss monsters in TW1.
Right. My question should rather be "How would you illustrate such nuances?"
You know, to be honest, I didn't think about that guy. Maybe because of grand scheme politics etc. But now, he would fit Act I perfectly and at least Henselt's Camp in Act II as well. Nice, really nice.

Any other ideas?

avatar
227: It's awesome, but you can't really "talk" about it because you'd give away the best part :)
That's right, bro, so let's not spoil the fun. :)
I believe they messed around with mouse sensitivity, it feels laggy and unresponsive during combat, thats why people feel the game is harder (when all they did was nerf quen and adrenaline).
Post edited July 20, 2011 by jonesy1138
avatar
jonesy1138: I believe they messed around with mouse sensitivity, it feels laggy and unresponsive during combat, thats why people feel the game is harder (when all they did was nerf quen and adrenaline).
Yes, I'm starting to suspect something has happened here, as well. The settings in the user.ini file haven't changed, though, so I've no idea what may have caused this...
avatar
dnna: *scrolling past your Fluff discussion*

I was removing my HUD mods and noticed a new dzip called "elf_flotsam". When you unzip it, it contains sex scene files - any idea what this is? It could be the elf patch mentioned in changelog, tho.
If you take the Iorveth path, when get ready to depart on the ship, you will end up with a choice, save the Elven girls, or go after the honcho. If you save the elven girls, you will indeed meet one later and have sex. I think that may be what that is.
avatar
coastie65: If you take the Iorveth path, when get ready to depart on the ship, you will end up with a choice, save the Elven girls, or go after the honcho. If you save the elven girls, you will indeed meet one later and have sex. I think that may be what that is.
This has been an option since v1.0, tho. I'm just a little confused because this was added with 1.3 - perhaps they just fixed something, I don't know.
Hope this is the right place for this!

I reinstalled TW2 from scratch twice today (both seemingly auto-updated to 1.3 -- how do I tell?) and both times I keep getting a "launcher" dialog that pops up with no text, an iconic "i" in the middle and an "OK" button to press. Clicking the X or the OK multiple times spawns more underneath, and eventually I do manage to close them all... until the "Connection refused." message pops in at the bottom of the launcher pane and spawns another launcher dialog. It also continues to spawn the little dialog boxes each time the connection tries again. What the heck is this?

I am able to run the game, and I have zero mods installed. Thanks in advance for any help.
Attachments:
avatar
jonathan_phang: [url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url][url=][/url]
avatar
KenR7A: Can anyone confirm if we 16:10 users LOST fov horizontally just to GAIN pixels in the vertical?
avatar
jonathan_phang: Unfortunately this is true. As you say, 16:10 users have now used all the pixels on screen, however the FOV is less and we have hor- (as in to say that this widescreen mode shows less of the horizontal field of view.

Ideally, we would want 16:10 to be vert+ (as in the same FOV as 16:9 but with extra rendering at the top and bottom.

Its a little lazy, and disapointing, but I have set my config to be 1920x1080 as the extra FOV (or proper FOV) gives a better view to the game world. Screens attached. You can see that the 1920x1200 is just the 1920x1080 screen but with the sides lopped off to give the correct aspect ratio. Oh well, played enough on 16:9 so will continue to...
Now that is disappointing. I bought a bigger screen thinking I would see more..not less.

Is this the fault of this engine or just lazy programming?

I sorely miss having an option to adjust FOV in this engine. Can't think of any other RPG I've played in 5 years that hasn't allowed me some FOV adjustment.
avatar
jonesy1138: I believe they messed around with mouse sensitivity, it feels laggy and unresponsive during combat, thats why people feel the game is harder (when all they did was nerf quen and adrenaline).
Yes! I noticed the mouse sensitivity the FIRST time I opened the game. What the heck happened??

See my post:
http://www.gog.com/en/forum/the_witcher_2/in_game_mouse_acceleration_sensitivity_added_in_1_3
avatar
NeoGutsman: I reinstalled TW2 from scratch twice today (both seemingly auto-updated to 1.3 -- how do I tell?)
You're not installed to 1.3, or even 1.2. The "registered users" and "downloadable content" tabs were both removed from the launcher in 1.2, so I can tell based on your launcher.

Basically, never trust an auto-update. Manual patching seems to be the way to go when it comes to this game. If you have the GOG version, manually download 1.1 where the bonus content is, then download 1.2 and 1.3 from the witcher site. If you have any other version though, try out the 0->1.3 patch.

The fact that you're getting that weird error probably means that something went wrong in the installation or patching process. In my opinion, you should reinstall and see if manual patching solves your problem.
I was also surprised by the FOV changes with the 1.3 patch. I was given the tip of adjusting my resolution from 1280x1024 (4:3 aspect ratio) to 1280x720 in order to regain the 1.2 patch view.

One minor thing I note that hasn't been fixed yet is the auto-equip of the Blue Stripes combat jacket, no matter what armor I'm already wearing. It's just a little jarring to have Raven's Armor equipped before the cut scene, and then it switch out on you.

I'm hoping to give this game a lot more attention now that this patch has dropped.

Edit: Another thing I noticed.

When playing with patch 1.2, I was able to aim/fire the ballista when using the XBox 360 controller. Now with patch 1.3, I'm able to use the controller for everything else so far, but I have to use the mouse to aim/fire.
Post edited July 21, 2011 by deoren
avatar
cbarbagallo: MAybe I am dumb, but what resolution is 6028x1080? CDPR listed 4:3, 5:4, and 16:10 fixes in addition to the existing 16:9.
avatar
naomha: You playing that resolution in Eyefinity? Because I can't get out of a single monitor. On the options tab (before the patch, because now I can't even access them) it gave me the choice to go to 5760x1080 but the screen stays centered on a single monitor. I have dual 6950s running on 3 24" hanns but can't get this thing to play in Eyefinity to save my life.
Sadly not able to play it in Eyefinity here either.

But, widescreengamingforum.com is working on a fix for it I think. So maybe, just maybe!

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

http://www.flawlesswidescreen.org/ has an application that enables surround/eyefinity support.
Post edited July 21, 2011 by LordEddi
avatar
NeoGutsman: I reinstalled TW2 from scratch twice today (both seemingly auto-updated to 1.3 -- how do I tell?)
avatar
227: You're not installed to 1.3, or even 1.2. The "registered users" and "downloadable content" tabs were both removed from the launcher in 1.2, so I can tell based on your launcher.

Basically, never trust an auto-update. Manual patching seems to be the way to go when it comes to this game. If you have the GOG version, manually download 1.1 where the bonus content is, then download 1.2 and 1.3 from the witcher site. If you have any other version though, try out the 0->1.3 patch.

The fact that you're getting that weird error probably means that something went wrong in the installation or patching process. In my opinion, you should reinstall and see if manual patching solves your problem.
Thanks so much for your insight! I thought it was funny that I wasn't getting the 16:10 aspect... ;)

Edit: Yes, I have the GOG version, so I manually patched to 1.1, the game menu launched and auto-updated to 1.2 and I then manually patched to 1.3.
Post edited July 21, 2011 by NeoGutsman