36 replies to this topic

[mekabuser]

lol , yeah, i watched the vid too and its NOT an example of bad netcode. The one gauss clearly did miss and what? a hair of lead on the lazers?

[HRR Insanity]

It's not random. Learn to compensate for the netcode until they fix it.

[Thirdstar]

HRR Insanity, on 22 January 2013 - 10:03 PM, said:

It's not random. Learn to compensate for the netcode until they fix it.

Netcode + variable ping = random.

I am not nor have I ever been a robot or a targeting computer





Also, I've personally seen the hit animation but no actual paperdoll damage hundreds of times, which can be seen several times in the linked vid.

Are we seriously still arguing about the ACTUAL existence of netcode issues? Really?

Edited by Thirdstar, 22 January 2013 - 10:09 PM.

[Mechwarrior Buddah]

Thirdstar, on 22 January 2013 - 09:33 PM, said:

I was told that there are no Netcode issues and that I should instead learn to aim.

Devs please stop wasting time on non-existent netcode issues.

lol ya this get on bringing back collisions and MASC as making mechs go faster should be fine since the netcode is fine

HRR Insanity, on 22 January 2013 - 10:03 PM, said:

It's not random. Learn to compensate for the netcode until they fix it.

so it DOES exist you say?

[ProtoformX]

I love how your illustration of bad netcode shows two Gauss rounds slamming DIRECTLY into a mech for the kill shot... They didn't land on an imaginary hit box in front of him and kill him, they landed on HIM. No **** you had to lead your shot. The ballistics have travel time.

[HRR Insanity]

Thirdstar, on 22 January 2013 - 10:07 PM, said:

Netcode + variable ping = random.
I am not nor have I ever been a robot or a targeting computer

You don't have to be. Just lead your targets based on their speed and direction relative to your fire.

Quote

Also, I've personally seen the hit animation but no actual paperdoll damage hundreds of times, which can be seen several times in the linked vid.

Please see the post I linked. What you see on your client has no relationship to what damage is being done on the server.

Quote

Are we seriously still arguing about the ACTUAL existence of netcode issues? Really?

No. It's busted. They're trying to fix it.

[Fooooo]

Depending how long they think they will be with netcode improvements, how would a reduction in the speed cap sound to most people ?

At least until the improvements are ready to try out. (at which point the speedcap would go back to what it is now)

Maybe reduce it to 100km/h ? Probably still be some lagsheilding going on, but not as much.......


Either way, everyone should take note of HRR insanitys linked thread there, especially newbies to the game. Im somewhat in the process of making a vid to show exactly what he is talking about, to make it even easier for newbies to understand.

[Ghogiel]

^you from aussie land. DO IT.

HRR Insanity, on 22 January 2013 - 10:39 PM, said:

You don't have to be. Just lead your targets based on their speed and direction relative to your fire.

I know what you are saying.
calculating the random amount of distance that individually varies between all enemy mechs visibly and their actual hitboxes, factored into the current angle they are moving at perpendicular to your screen and adjusting your lead based on that, blah blah, but man I really wish people with their lag shooting master skills would post up lagshield problem videos as they see it. That way I can see what they have to deal with lol. like from the OPs video. That looks like it is waaaaay easy to compensate for such miniscule amounts of lag. If only it was like that all the time, I wouldn't even complain.

And my ping is only 110-120. I can't even imagine people who have ping worse than mine have to deal with.

Edited by Ghogiel, 22 January 2013 - 11:05 PM.

[CECILOFS]

Ghogiel, on 22 January 2013 - 11:04 PM, said:

And my ping is only 110-120. I can't even imagine people who have ping worse than mine have to deal with.

My ping sits between 250-500ms, which is still considered good from Australia btw.

To hit a full speed raven, I have to aim 2-4 mech lengths in front (as in from the tip of the raven's CT to the back of its rear CT) and pray they didn't change direction in the last second.

This is why I use streaks and LRMs - its practically impossible to hit them with lasers. Super frustrating when it animates your lasers hitting them and causing heat on their armour but the paper doll doesn't show any damage.

[GalaxyBluestar]

how is this thread still going? it started as old news and we're debating about whether a ton worth of complaints last week was well founded or not? plenty of links already poping up about "how i learned to lead in horrible laggy states and love the netcode." that simply says game is broken i'll have to adjust my attitude for it's shoddy drawbacks.

a combination of poor hitboxes rit reag/netcode and ping lag can lead to shocking results i'm constantly shooting lasers into airpockets to get a red reticle even on heavy mechs that have come to a halt. and if they rubberband in a different direction you just shot out to nowhere get cussed by others for being a noob whilst said target gets a free shot on you. it's no fun.

however WE KNOW ALL THIS ALREADY! so it really doesn't need to be said anymore the devs know about this and the netcoders have a sweat shop job of fixing it so take a break and wait for the fix patches.

Edited by GalaxyBluestar, 23 January 2013 - 12:14 AM.

[Quxudica]

GrabbleRus, on 22 January 2013 - 09:33 PM, said:

New generation... They're freaking even about the necessity to lead ahead of the target.

Yes, how dare they hold a developer to a standard of quality representative of the tech available in 2013. Madness I say. Sorry to burst your bubble, but we bitched about bad hit detection and crappy hit boxes back in the days of yore too - and rightly so.

[DirePhoenix]

Fooooo, on 22 January 2013 - 10:45 PM, said:

Depending how long they think they will be with netcode improvements, how would a reduction in the speed cap sound to most people ?

There was a point, long, ago, when they didn't even have the engine restrictions they currently have in place.

Jenners were literally moving faster than light, teleporting across the battlefield...

[elbloom]

just played with a devteam yesterday.... garth erlam, thomas (dzielewski or wtf.), some Kyle and another guy....

ALL in lagshield cicada´s, I think they enjoy this sheet -.- but everytime I see them i drop the obligatory "netcode, please" into the chat

Edited by elbloom, 23 January 2013 - 02:26 AM.

[Protoculture]

athlonduke, on 22 January 2013 - 08:39 PM, said:

I cut out the end of the match, it was painful.I have to "lead" with a laser. a weapon that fires something at the speed of light. ballistics I have to guess where to aim.
That's really the whole issue with this, no one knows where the hell any of these lights are. they are moving faster than the servers can keep up with.
video highlights:
Commando: I got lucky as hell. teammate, not so much.
fire and "hit" 1: animation looks like I hit, but no damage registered
wtf laser: i'm "hitting" 2 mechs ahead of the target.
fire and "hit" 2: again, the game thinks I hit but no damage is registered. There's a huge explosion and everything!

http://youtu.be/Ycjmj5EqNM0

Check my sig.

[Inertiaman]

Nalin, on 22 January 2013 - 09:47 PM, said:

Okay OP, I've watched your video and I think I've figured out what your problem is.

See, lasers are a "damage over time" (DOT) weapon. That means they only do damage when in contact with a mech. Well, I am sorry to point out that yours weren't in contact with the enemy. This may be the problem you are experiencing. I would recommend that you keep your lasers pointed at enemy mechs instead of pointing them at walls and/or the ground.

I hope you can use these suggestions to become a better gamer in the future.

Bad Advice from Bad Player is Very Bad.

toxx1790, on 22 January 2013 - 09:59 PM, said:

I watched the video too. I didn't think it was lag shield.

You are leading the same amount for lasers as you are for ballistics and you wonder why they do no damage? You do know that light travels faster than bullets, right?

Pay no attention to the cursor behind the curtain.

[Budor]

Nalin, on 22 January 2013 - 09:47 PM, said:

Okay OP, I've watched your video and I think I've figured out what your problem is.

See, lasers are a "damage over time" (DOT) weapon. That means they only do damage when in contact with a mech. Well, I am sorry to point out that yours weren't in contact with the enemy. This may be the problem you are experiencing. I would recommend that you keep your lasers pointed at enemy mechs instead of pointing them at walls and/or the ground.

I hope you can use these suggestions to become a better gamer in the future.

[Alex Warden]

Darkrook, on 22 January 2013 - 08:55 PM, said:

Problem is, the tweak is in the same spot as it was months ago

no its´not... for me it´s gotten way way better since november... at least the warping of fast runners is gone, and there is close to no problem hitting a light after some practice... i know that´s not for all of you, but i doubt i am the only one seeing many improvements on the netcode, and like already said: they are not stopping to work on it...

Edited by Alex Warden, 23 January 2013 - 03:17 AM.