21 replies to this topic

[Azuanite]

Give them the LRM treatment. Nerf them every patch and then introduce a new weapon. Preferably one that automatically one shot any mech that is travelling over 80 kph.

[MagicHamsta]

Then introduce a weapon which can punch other mechs & cause them to fly at exactly 81 kph causing said weapon to trigger and destroy them.

Aye, aye perfect.
/rollseyes.

[deadeye mcduck]

Seems OP cannot hit light mechs with ballistic/energy weapons.

[Azuanite]

deadeye mcduck, on 08 December 2012 - 02:46 AM, said:

Seems OP cannot hit light mechs with ballistic/energy weapons.

Bro i hit them, at least visually it looks like i hit them but you know light mech exploits even if it did look like i hit them it still miss.

[Gnuz]

Tags: netcode; ping; lagshooting; 10111Mechwarrior'sNotAnFPS!RAGE

There are moments when I feel the OPs pain sharply.

GnuZ (~250ms Aussie high-ping peasant)

[deadeye mcduck]

Once knock downs return, lights will be more managable.

[TruePoindexter]

Azuanite, on 08 December 2012 - 02:48 AM, said:

Bro i hit them, at least visually it looks like i hit them but you know light mech exploits even if it did look like i hit them it still miss.

Lag lead - we did it in the 90's you can do it now. Aim slightly ahead of where they look like they are.

Edited by TruePoindexter, 08 December 2012 - 03:11 AM.

[Azuanite]

TruePoindexter, on 08 December 2012 - 03:10 AM, said:

Lag lead - we did it in the 90's you can do it now. Aim slightly ahead of where they look like they are.

yeah no, it isn't as simple as "lag lead". This isn't a first person shooter game where predicting is simple. In a game where a mech can be 3x faster than you and you want to lag lead?.. good luck with that.

[Bloody Moon]

Azuanite, on 08 December 2012 - 03:20 AM, said:

yeah no, it isn't as simple as "lag lead". This isn't a first person shooter game where predicting is simple. In a game where a mech can be 3x faster than you and you want to lag lead?.. good luck with that.

Thanks, i'll take my chances with it 'til the netcode is fixed.

[TruePoindexter]

Azuanite, on 08 December 2012 - 03:20 AM, said:

yeah no, it isn't as simple as "lag lead". This isn't a first person shooter game where predicting is simple. In a game where a mech can be 3x faster than you and you want to lag lead?.. good luck with that.

Uh huh. I only do it all the time. Please try it before you knock it.

[Zylo]

Azuanite, on 08 December 2012 - 02:05 AM, said:

Give them the LRM treatment. Nerf them every patch and then introduce a new weapon. Preferably one that automatically one shot any mech that is travelling over 80 kph.

You do know collisions are coming back right?

That is the best way to deal with a light mech if you can't seem to hit it with weapons. Crash into it and shoot it while it's face down on the ground. That's what we did in closed beta to lagging lights.

[Asseri]

TruePoindexter, on 08 December 2012 - 03:10 AM, said:

Lag lead - we did it in the 90's you can do it now. Aim slightly ahead of where they look like they are.

Even though I've got used to lag leading and I do hit people really well I'm still amazed that we have all kind of good ping systems. We got client side hit detection, we have predictive ping system, we have server side ping system where your shots actually has delay depending on your latency but stuff hits where it seems to hit... And then we got MWO ping system wich is the same as we had in games 15 years ago.

In my opinion this kind of ping system is really bad even if it's to prevent cheating. I'd rather take the server side system where your shots have delay depending on your latency but you hit where you seem to hit. It just doesnt feel right to shoot the thin air infront of that light mech running by. I do understand leading with ballistic weapons but with hitscan weapon like laser it just looks silly to intentionally shoot the ground to hit the light mech. Also, when they are on the run I cant keep my crosshair on certain part of their mech but I have to hope that his arm/leg/whatever is at the spot in the thin air I'm shooting at.


TL;DR: Current ping system is horribad and no-one should defend it even if they've got used to it.

Edited by Asseri, 08 December 2012 - 05:09 AM.

[King Arthur IV]

need unit collision on. fair enough ecm doesnt allow me to see them or lock on them but having them run around in circles smacking into walls and my legs + the no vision is not fair.

[HC Harlequin]

http://mwomercs.com/...cm/page__st__20

[nom de guerre]

deadeye mcduck, on 08 December 2012 - 02:46 AM, said:

Seems OP cannot hit light mechs with ballistic/energy weapons.

seems that way...

[TruePoindexter]

Asseri, on 08 December 2012 - 05:06 AM, said:

Even though I've got used to lag leading and I do hit people really well I'm still amazed that we have all kind of good ping systems. We got client side hit detection, we have predictive ping system, we have server side ping system where your shots actually has delay depending on your latency but stuff hits where it seems to hit... And then we got MWO ping system wich is the same as we had in games 15 years ago.

In my opinion this kind of ping system is really bad even if it's to prevent cheating. I'd rather take the server side system where your shots have delay depending on your latency but you hit where you seem to hit. It just doesnt feel right to shoot the thin air infront of that light mech running by. I do understand leading with ballistic weapons but with hitscan weapon like laser it just looks silly to intentionally shoot the ground to hit the light mech. Also, when they are on the run I cant keep my crosshair on certain part of their mech but I have to hope that his arm/leg/whatever is at the spot in the thin air I'm shooting at.


TL;DR: Current ping system is horribad and no-one should defend it even if they've got used to it.

I noticed your location is marked as Finland so I'm assuming that's true and you're an EU player. That's really the issue - the game doesn't have localized servers. It has been discussed already and mentioned by the devs that they're looking into regional servers specifically for EU players.

[Taizan]

I think I have a "felt" 20% hit rate on lights with energy weapons, even when leading as much as I can. They are lagging and jerking around its not normal any more. My ping is usually between 150 - 250 (sometimes around 400) but these little guys basically have a warp distortion field around them, even when I have low ping. Also when spectating the jerking and warping is almost nauseating. Hitting - sometimes, hitting lights on the location I am aiming at - never.

Its not just the ping though, I have a feeling that on the way back and forth many packets get dropped and the information on location of an enemy is completely off leading to mentioned effects.
Quakeworld used to have a "net_stats" console command that showed some details about the connection, maybe this could be included with the F9 status message as well.

Edited by Taizan, 08 December 2012 - 10:56 AM.

[StainlessSR]

TruePoindexter, on 08 December 2012 - 10:39 AM, said:

I noticed your location is marked as Finland so I'm assuming that's true and you're an EU player. That's really the issue - the game doesn't have localized servers. It has been discussed already and mentioned by the devs that they're looking into regional servers specifically for EU players.

No that is not the issue, before collisions were removed when a light got knocked down it would rubberband as it stood up, this was the server resynching it's location with it's hitbox (that was why you waited till it rubberbanded before alphaing the pock out of it). When collisions were removed lights would bounce off mechs and walls to desynch their hitbox, streaks were the only effective counter, now streaks are a non issue for lights so the problem¹ that has been arround has now grown to be a glaring deficiency on PGI's part and is seriously effecting gameplay.

¹Lights not registering total damage expected (dual ac20 only turning center torso yellow) and hit box loss/change.

[TruePoindexter]

StainlessSR, on 08 December 2012 - 11:32 AM, said:

No that is not the issue, before collisions were removed when a light got knocked down it would rubberband as it stood up, this was the server resynching it's location with it's hitbox (that was why you waited till it rubberbanded before alphaing the pock out of it). When collisions were removed lights would bounce off mechs and walls to desynch their hitbox, streaks were the only effective counter, now streaks are a non issue for lights so the problem¹ that has been arround has now grown to be a glaring deficiency on PGI's part and is seriously effecting gameplay.

¹Lights not registering total damage expected (dual ac20 only turning center torso yellow) and hit box loss/change.

Expecting instant and perfect data transfer when the server is located in Western NA and the player in Finland is unreasonable.

[StainlessSR]

TruePoindexter, on 08 December 2012 - 02:03 PM, said:

Expecting instant and perfect data transfer when the server is located in Western NA and the player in Finland is unreasonable.

I am in the us and generally have about 56ping, and still by bouncing off rocks and running through mechs I have been able to knock my hitbox off. Without the Maxbuild SSrm light hunter, lights are now over powered and hard to kill (when the hitbox has been knocked off kilter). And making a program that requires instant and perfect data transfer is unreasonable as instant and perfect data will not happen unless you are in the same city/building as the server.