******* W2, STEAM(!) version. *******

FPS was absolutely normal to play on 1.2 version.

But it's barely working now and doing some kind of lagging (yes, like miltiplayer games). The picture and output have some desynchronization of ~0.5 sec and it cause to have somekind of lag.
It's appears only on places when camera sees the new zone of loading, like doors for example.
When you walking and door is not on the screen - fps is fine and game is ok (hair's physics normal and responds corect).
But when you will walk same way but with door on the screen - game start to chop, Geralt walks jerking, and physics of his hairs starts to jump, like he is running, or jumping.

I've wiped out game from PC.
Uninstall+deleting left folders in steam\witcher2 + W2 folder in MyDocuments.

Did a clean setup, from the scratch. On first run it's started updating to 1.3.
Then I've choosed lowest config and resolution which is possible.
Start the game, choose the Temple map from conversation with Roche.
Made a quick run to the inside court (end of map) to be sure, because this is most visible spot for lag-chop.
And it's still there.
When I'm watching East,North,South - FPS is flawless, running like a dog.
When I'm watching West - fps is the same, but if I'm starting to walk or to run - game makes lags, like on MMO games.

Which is strange, I've made wallking to the end of cliff.
So it's lagging all the time when I was walking, but, on the edge, it's was ok, no lags.
One step bckwd-fwd - here the lag again.

So it's something with West coordinate and animation binding.

I can't believe that noone else is not suffering the same, cos it's definatly somethin' in 1.3 code's.

When the game was 1.2 everything was fine with FPS, no lags.

P.s. I'm not only one person with this issue, based on STEAM forum. It's not "nVidia" bug, because other people have the same with ATi vc.

Well, there's your problem right there. Steam version patched to 1.3 seems to be a nightmare compared to the mostly-functioning patch 1.3 that the rest of us have. For what it's worth, choppiness like what you're describing is occasionally fixed by something like Dxtory or another FPS limiter. Or maybe not. Seems to be pretty hit-and-miss, honestly. If you're talking about the lack of comments about it here, it's because there aren't many Steam-users here.

I wonder if this topic is going to become another "hate on Steam because they suxxorz" thread. Part of me really hopes so :)

@OP: post system specs too, we can't just guess them out :-\

It will not help anyone, cos issue present on different kind of HW.

But anyway, mine are:
Intel QX9300 2.53 GHz/Intel PM45E/nVidia GTX 260M 1Gb/Samsung MLC 64GB SSD + Seagate 7200.4 500Gb/Kingston 4+2Gb CL7/ Win7 7600 x64

--------
With new nVidia 280 beta drivers it's made lags a little bit less, but just a little bit, they are still present in a huge amount. Really hard to fight, because G circling like a monkey around enemies, and with these lags it's super hard, cos timing is unpredictable with lag.
Plus thoose drivers added a "new feature" to me - CTD. Never happened with my tW2 before.

> It will not help anyone, cos issue present on different kind of HW.
it should help your issues

> Intel QX9300 2.53 GHz/Intel PM45E/nVidia GTX 260M 1Gb/Samsung MLC
> 64GB SSD + Seagate 7200.4 500Gb/Kingston 4+2Gb CL7/ Win7 7600 x64
Oh my, laptop?
so, first of all a GTX260M ( as in Mobile version ) is not on par with the desktop card, but more like a GeForce 9800 GT ( same number of shaders 112 ) so your settings should be modified accordingly, anyway since you see these on LOW then maybe you should look at the Power settings in Windows, is everything put on Performance? did you disable USB/harddrive/etc sleeping ?


> Plus thoose drivers added a "new feature" to me - CTD. Never happened with my tW2 before.
beta drivers, either work fine or not meh

better NOT do that, you would not want to RE-download 9Gb of game files for nothing! :(

That should no longer be an issue as Steam have updated their downloading system.

And even if it was, it's better than having a game you can't play.

Notebook or not, but there wasn't anything like this in 1,2 version at all. It's mentioned in the first post.

It's appeared for everyone who notice it only with 1.3 patch.
I'm playing fine with Ultra, minus uber+motionblur+aa+vsinc.

The lowest settings was set as example. No matter which settings you will set, the problem will be present. It's more like problem with animation coordinates when moving to west. Because if you will stuck in some way, then FPS will be fine, no lags, but you will see that animation will be interuptied in a different way.

Plus, as mentioned in the first post, it really visible by G's hears. When these lags appears, his hears jumping like a crazy, more like reset of physic all the time.

So many issues related to Steam, sigh..stop using Steam.

What's that got to do with the game performance? I'll tell you: NOTHING

@h0w1er: Power settings?

Steam overlay/Steam chat causes overhead over Witcher 2...and may be* conflicts.

All on max perf.
Even if it will be "anything because of notebook" and not because of game's code - it will represent issue all the way, but not only when G walking with camera's set on west.

Remember, there are 5 more directions (East, North, South, Up, Down) and they works fine.

your posts would be so much better without the "steam is evil" spam in all the threads...
anyway, you are correct, sometimes the Overlay can be at fault, but not even on LOW

no no no..you completely misunderstood me, or I am putting forth my conclusions in a wrong format (my English is poor, may be..or somewhat..nvm).

I am dissecting the extra and external components which is not part of the actual game, but at the same time affecting the execution of the later. Either by human error, overhead or dependencies.

Then mentioning those extra and external components because, I conclude that during the development of Witcher 2 those components were not installed or tied in either during testing nor at the developing stages of the game. (might be unsure about this, but this is what I conclude citing issues with these..ahem..extra and external components)