31 replies to this topic

[Star Wolves Admin Account]

But not for the apparent reason you normally hear people complain about (Granted I do think the LRM and ECM situation sucks right now).

No, the real reason they ruin the game is that when they hit you earthquake simulator begins and the game lags terribly. I have 22 ping typically and a nice video card but still lag up horribly when any one of these hit me.

I can literally no longer shoot back or see what is happening. The LRM spam, art spam, and dakka dakka direwolf simply make the game unplayable at points. As an example, it is reasonable that an AC5 direwolf will beat my gauss direwolf, he is a dedicated gauss counter mech; what is not reasonable is that I never get a chance to shoot back as the lag is so bad I just have to fall back frantically twirling my torso around.

Any thoughts or should I just L2P?

Edited by Blueduck, 12 October 2014 - 01:40 PM.

[Powder Puff Pew Pew]

"BooHoo" Troll Post. L2P

[Star Wolves Admin Account]

I been pwned

[Budor]

Impact blur and screenshake is overdone but PGI seems to think its immersive.

[Star Wolves Admin Account]

You know, it would be immersive if the cursor didn't jump around like you were in a timewarp. Its almost like the games engine can't keep up.

[luxebo]

Blueduck, on 12 October 2014 - 01:32 PM, said:

But not for the apparent reason you normally hear people complain about (Granted I do think the LRM and ECM situation sucks right now).

No, the real reason they ruin the game is that when they hit you earthquake simulator begins and the game lags terribly. I have 22 ping typically and a nice video card but still lag up horribly when any one of these hit me.

I can literally no longer shoot back or see what is happening. The LRM spam, art spam, and dakka dakka direwolf simply make the game unplayable at points.

Any thoughts or should I just L2P?

Actually I got lagged out and crashed in one match because I didn't see an arty. LRMs though physically are rough, need some modification somehow.

[Star Wolves Admin Account]

I feel you pain luxebo

[Bront]

The shake is a little over kill at times. Very, very rarely, I've seen the screen knocked over 90 degrees off kilter. The ground should never be up, no matter how much shake I'm getting.

[JD R]

Blueduck, on 12 October 2014 - 01:36 PM, said:

You know, it would be immersive if the cursor didn't jump around like you were in a timewarp. Its almost like the games engine can't keep up.

The cursor dont jump. He is still where you are aiming dont move the mouse and open fire

[Star Wolves Admin Account]

Problem is JDR sometimes you need to move just a tad to hit him and then its all over since the cursor has no hope of tracking correctly as the game's frames per second seem to not keep up.

I'll definitely try that though next time I have him in my sights from the get go.

[Nathan Foxbane]

Still better than when impulse first came out and hexa5 cats made it Washing Machine Simulator Online.

[Wintersdark]

Blueduck, on 12 October 2014 - 01:44 PM, said:

Problem is JDR sometimes you need to move just a tad to hit him and then its all over since the cursor has no hope of tracking correctly as the game's frames per second seem to not keep up.

I'll definitely try that though next time I have him in my sights from the get go.

I don't have this problem at all, and I certainly don't have a beast of a machine. I'm running an old 965BE quadcore at 4ghz, and a 7850. It's overclocked heavily, but it ends up being somewhat more powerful than a stock 7870; certainly nothing to swoon over.

Even so, because screen shake from weapon impacts does not modify my aim, I simply point where the red doritos tell me to and return fire. Works well enough for me.

[Star Wolves Admin Account]

I'll give it a try WintersDark. I've had really bad luck trying that with gauss rifles but maybe I've just been going about in the wrong way.

What exactly is your aiming strategy when the screenshake and lag hit so I can understand.

[Aresye]

Here's the thing. All weapons that have an impulse (that is screenshake) are merely just shaking your screen. You can train yourself to aim through the shake.

Missiles on the other hand, are the only weapons that have an added motion blur on top of the screen shake effects. That is what turns it from something you can shoot through, to something that's impossible to shoot through.

The devs seem to think the missile problems are related to the screen shake, when in fact they've always been related to the motion blur attached to it.

[Jolly Llama]

Forum whiners, mechanic changes, and nerfs are ruining the game. STFU.

[Star Wolves Admin Account]

Geodeath, your parents may not have given you the love you need, but they did give you the discipline you deserved

Need a hug buttercup?

Edited by Blueduck, 12 October 2014 - 01:58 PM.

[Felicitatem Parco]

You can try the Improved Gyros module... it'll reduce screen-shake at the expense of you having to leave another module behind.

[Wintersdark]

Blueduck, on 12 October 2014 - 01:50 PM, said:

I'll give it a try WintersDark. I've had really bad luck trying that with gauss rifles but maybe I've just been going about in the wrong way.

What exactly is your aiming strategy when the screenshake and lag hit so I can understand.

I don't lag when hit; that's what I was saying. The visual screenshake sure, but no lag. I simply aim center-mass and return fire. Directly down from the dorito

[JD R]

Blueduck, on 12 October 2014 - 01:44 PM, said:

Problem is JDR sometimes you need to move just a tad to hit him and then its all over since the cursor has no hope of tracking correctly as the game's frames per second seem to not keep up.

I'll definitely try that though next time I have him in my sights from the get go.

From my experience the problem is the pilot. The mouse movement is what i saw the same as every time but you loose the track of your moving and dont hit.


Edit: l2p

Edited by JD R, 12 October 2014 - 02:07 PM.

[Bartholomew bartholomew]

We need a harsh language module. If the nerfhearders had their way that is all we would have left.