20 replies to this topic

[Bitslizer]

So seem the movement code is fixed IE shutdown mech is actually where you see them, and not some distance away, and I understand the lagshield is not fix 100% due to state re-winding still need to be implemented

I'm guessing that movement code fix will also apply to Knocked down mech? So that where a mech appear to be knocked down is actually where they are at?

I know collision damage isn't done yet, but can we at least have knock down re-enabled? that will at least give players a chance to knock down all the ECM ankle biters.

[Lynette Steffeld]

Not to be a killjoy...

But the moment I start my dragonbowling antics again...

Let's just put it this way: If it's not one thing it's the other.

I'd rather have 'em fix EVERYTHING first.

THEN we can all complain about it TOGETHER.

[Bitslizer]

I rate lag shield as a higher annoyance then dragon bowling personally.

If that's a ncessary evil to put up with, I think I can live with that

[Lynette Steffeld]

That's what a lot of us said about bowling back then...

Then LRM boats.

It's a bit like dominoes.

Either way they've announced a fix... expect it in another month or so I guess.

[Tarman]

Dragonbowl Z. In the current climate of mass amounts of lights, I'd like to see this make a comeback.

[Lynette Steffeld]

Tarman, on 17 January 2013 - 10:49 AM, said:

Dragonbowl Z. In the current climate of mass amounts of lights, I'd like to see this make a comeback.

But what if the Ping on that Jenner...

IS OVER NINE THOUUUUUUSAAAAANDDDDDDD?

[Bilbo]

I thought they fixed the dragonbowling before they actually removed the knockdowns.

[Ngamok]

I wouldn't make KD a 100% for a Dragon to not also go down as well like it was in CB.

[Throat Punch]

I'd love collision back in only if they do it correctly. No more lights knocking over an Atlas. Spiders and commandos should explode when they run into something a hell of a lot bigger then them at full speed. A miata does not move a sherman tank if it hits it going 75 mph, but a sherman would certainly ruin a miata's day.

[Eddrick]

I haven"t seen any confirmation that the new Netcode is finished. However, it would be nice to have knockdowns in. Only as long as it works right. No need to exchange one problem for another.

[Tarman]

Bilbo, on 17 January 2013 - 10:52 AM, said:

I thought they fixed the dragonbowling before they actually removed the knockdowns.

I'm pretty sure you're right about that, but a Dragon would still be a good bowler for lightswarms. Cicada has speed but it's not much bigger than the lights it's hunting, I'd figure it's more likely to trip as well.

[Kylere]

Without collisions the game is lacking a vital element, it is what allows lights to move so quickly without pilot skill, it is what allows them to run through Atlai, and it takes away that "Out of weapons, let us run at the SOB" tactic along with DFA.

[Kaijin]

Bilbo, on 17 January 2013 - 10:52 AM, said:

I thought they fixed the dragonbowling before they actually removed the knockdowns.

They did, yes.

[Odins Fist]

Bitslizer, on 17 January 2013 - 10:39 AM, said:

"Since Movement Code Is Fixed, Please Re-Enable Knock Down!"

.
FYI, the "Netcode" has "NOT" been fixed yet....

[Oy of MidWorld]

I would also like to have collisions back soon. I'd also love collisions to occur if someone slammed into a solid obstacle too fast. Canonically piloting a mech at 100+ kph does require a high piloting skill. A fact that is not properly represented in this game... at all.

Wouldn't have to be over the top, just a requirement for a fast mechs pilot to actually work with the throttle a little, when navigating those narrow streets. The possibility of knockdown when carelessly slamming into objects would make pilots avoid it, add a lot of tension, and require a little more skill when piloting a fast mech.

[Bitslizer]

Odins Fist, on 17 January 2013 - 11:27 AM, said:

.
FYI, the "Netcode" has "NOT" been fixed yet....

the netcode, refer to 2 seperate parts

1) the movement code, which has been cleaned up since the last patch

2) the hit box code, this has to deal with the "state-rewinding" they have been talking about lately


the movement code, ie showing mech where they actually are, is the one that affect knocked down mech not showing up where they are at, ie shooting at a knock down mech do no damage because server think its somewhere else, this is the same as shooting at shut down mech doing no damage, which is stated in the last patch or 2 to be fixed.

[Matthew Craig]

As mentioned in the net-code roadmap post once Movement and Firing are addressed to everyone's satisfaction, bringing back collisions in a sensible (read game-play balanced) fashion is the next goal. Don't expect it to be exactly like before though Mechs should knock down correctly based on weight and impulse and impart much more damage when colliding, I expect when re-introduced it will be less of a 'tripping' mechanic and more of a tactical decision to ram and take the damage to your own Mech for the benefit of your team.

[Bitslizer]

Matthew Craig, on 17 January 2013 - 12:30 PM, said:

As mentioned in the net-code roadmap post once Movement and Firing are addressed to everyone's satisfaction, bringing back collisions in a sensible (read game-play balanced) fashion is the next goal. Don't expect it to be exactly like before though Mechs should knock down correctly based on weight and impulse and impart much more damage when colliding, I expect when re-introduced it will be less of a 'tripping' mechanic and more of a tactical decision to ram and take the damage to your own Mech for the benefit of your team.

Thanks for the answer Matthew, a bit disappointed but understandable, guess we'll just have to deal with the swarm of ECM ankle biters for a while longer heh.

Edited by Bitslizer, 17 January 2013 - 12:33 PM.

[Vilheim]

Matthew Craig, on 17 January 2013 - 12:30 PM, said:

As mentioned in the net-code roadmap post once Movement and Firing are addressed to everyone's satisfaction, bringing back collisions in a sensible (read game-play balanced) fashion is the next goal. Don't expect it to be exactly like before though Mechs should knock down correctly based on weight and impulse and impart much more damage when colliding, I expect when re-introduced it will be less of a 'tripping' mechanic and more of a tactical decision to ram and take the damage to your own Mech for the benefit of your team.

ZOOOOOOOMMMMMMBIEEEEEEEEE

[Odins Fist]

Bitslizer, on 17 January 2013 - 12:20 PM, said:

the netcode, refer to 2 seperate parts

1) the movement code, which has been cleaned up since the last patch

2) the hit box code, this has to deal with the "state-rewinding" they have been talking about lately


the movement code, ie showing mech where they actually are, is the one that affect knocked down mech not showing up where they are at, ie shooting at a knock down mech do no damage because server think its somewhere else, this is the same as shooting at shut down mech doing no damage, which is stated in the last patch or 2 to be fixed.

.
"AGAIN"... F.Y.I., the netcode hasn't been fixed yet....