1 reply to this topic

[unFearing]

I'm referring to the most recent patch main patch (not the wolverine..) where we got DX11 and JJs were nerfed.

Basically, I run MWO on all low settings, with textures very high, on a Asus K55 laptop, with 8 GB RAM. It gets around 20-30 FPS average, 10-20 when things get hectic. But now, when playing MW:O, my cursor more often than not is almost a full second behind my actual mouse movement, and the movement response from the keys I am hitting is also fairly slow (pressing "A" and "D" alternatively very quickly would portray a very erratic change in direction in the minimap, but is either very slow to occur or the mech basically stands still). Sometimes if I restart MW:O, the laggyness will go away, only to reoccur a short while after, such as when the fighting is actually taking place. It seems to be very random, and it might also just be how long I've been running MW:O, but playing a few games today -- it's not like my laptop is overheating either -- the same issue occurred and resulted in me JJing into many buildings, leading and firing at mechs, only to have the shot fire after I have stopped leading to set up the next shot.

Not to mention, when firing on enemies, not only is HSR still a problem for direct-fire weapons, as has been for a long time, but also when firing the killing blow, the enemies (like literally every one; Cataphracts in particular I suppose, being a trial and all) I keep killing don't die until 2-3 seconds later, AFTER i've wasted extra ammo or heat just to see if I killed him yet.

I've reset settings to default low, and also reduced motion blur (through the general "low" setting), and well basically, I can't exactly record either since my computer is subpar for such a task.

So in summation, recently MW:O has had slower input response time, and also many of the pilots I play with also agree that the killing blow on mechs just does not register when it occurs.

Does anyone know if this is simply the patch, server/connection related, or anything?
I'll accept most answers... I know my computer sucks, but it's not like PGI would break a bunch of the superblyoptimized code in a patch without forewarning, right?

Anyways, thanks. Hopefully I can just wait it out.

[Ertur]

I saw this too. So I ran the repair tool. It found a lot of issues, and fixed them. Now I CTD repeatedly. It's not an improvement.