39 replies to this topic

[fatcat01]

Personally I feel that the collision mechanic is the single most game changing mechanic that has yet to be implemented (not counting closed beta). I love new stuff, and game balancing is important; but I think that collisions will change the game so much that it should be put in before any other tweaks.

[Helbourne]

Yes, collisions need to be put back in ASAP. I like to pilot heavys and tripping lights is a good tactic. I am tired of seeing them running in circles around me. I so want to trip them. Sure I can kill lights running in circles but it looks rather silly to me. I know it works a lot of the time. Plus one of the classic Battletech moves is the "Death from Above". A heavy mech landing on top of a light would and should just crush its head in. Not an easy move to do, but if you can you should be able to reap the rewards.

[Lee Ving]

Helbourne, on 19 December 2012 - 01:29 PM, said:

Yes, collisions need to be put back in ASAP. I like to pilot heavys and tripping lights is a good tactic. I am tired of seeing them running in circles around me. I so want to trip them. Sure I can kill lights running in circles but it looks rather silly to me. I know it works a lot of the time. Plus one of the classic Battletech moves is the "Death from Above". A heavy mech landing on top of a light would and should just crush its head in. Not an easy move to do, but if you can you should be able to reap the rewards.

Death From Above may never be implemented. The devs have stated they will not be adding melee; hence the Yen sLow Wang having no titanium nails to drive into your sides as it tears armor away with the 20.

It'll be a darn shame if I can't crush tube-born with a highlander though.

[Katface]

Couldn't agree more

[HighlandCoo]

Yah - collisions == better netcode. Which would be amazing.

[HammerForge]

"Negative Ghost Rider, the pattern is full"

Netcode/Lag Shield should be primary concern...imho

Although I do want collisions and melee put in

[LordBraxton]

Agreed, I have a feeling they are struggling with how to implement them otherwise we would have seen them return already...

Hoping for an update about whats going wrong with collisions and what progress they have made, would be nice at least.

[Duncan Fisher]

At this point I just don't think the PGI team is actually capable of coding fully functional collisions...

[Major Derps]

Netcode should take precedence over everything else. Once that is fixed, then they can focus on other things IMO.

[Daiichidoku]

or just have patience

[kilgor]

There seems to be some kind of collision system in place. Whenever another 'Mech runs into me, my legs lose armor as they turn yellow.

[Zero Neutral]

fatcat01, on 24 November 2012 - 05:27 PM, said:

Personally I feel that the collision mechanic is the single most game changing mechanic that has yet to be implemented (not counting closed beta). I love new stuff, and game balancing is important; but I think that collisions will change the game so much that it should be put in before any other tweaks.

What you think should or should not be does not matter.

[Agent 0 Fortune]

So you are suggesting that we get no more patches for 6 months until the collision is fixed?
That is 6 new mechs, 2 new maps, and a plethora of other items and bug fixes, and we just wait for 6 months?

Or do you mean that PGI should put their artists and level designers to work on the network and physics code, because I don't think that work work out very well.

Besides, why do need collision back in so bad? The only thing it brought to the game was a way to combat lagshield.

[Lefty Lucy]

The reason why collisions were removed in the first place is because they did not play well with the net code. When netcode gets fixed is when they'll come back, and hopefully in a much better form than before.

[Major Derps]

Zero Neutral, on 19 December 2012 - 02:26 PM, said:

What you think should or should not be does not matter.

Or that too

[FrostCollar]

Lefty Lucy, on 19 December 2012 - 02:57 PM, said:

The reason why collisions were removed in the first place is because they did not play well with the net code. When netcode gets fixed is when they'll come back, and hopefully in a much better form than before.

Exactly. Who says they aren't working on collisions already? Netcode fixes are currently scheduled for late January "at the latest," IIRC.

[Corpsecandle]

Net code is the reason that they pulled tripping out in the first place so naturally: netcode gets fixed, tripping follows...however as they've said netcode is a specialized field and they're working on it. It's always scary as hell to tinker with something so deep in your code that it can break your entire system...not to mention the unforeseen impacts that you have to try and proactively test for.

[Solis Obscuri]

Fixing ECM > bringing back R&R costs > bringing back Collisions > Orion > everything else

[Helbourne]

If netcode is the biggest problem, then so be it. I say fix it first. I just want collisions back ASAP. If you think about it, 'Death from Above' is nothing more than a collision well from above. Heavy with JJs landing a light or medium, is a site to see I bet. Now that move does damage your legs, so you may end up without a leg to stand on. Now with all that said, I just want to be able to trip up a light running around in a circle like a fool, or hip check them into a side of a mountain.

I can understand how difficult it can be to hunt down bugs in programs. Now the last time I did programming was back in high school, and that was 20 years ago now. I can see it being a huge pain in the butt. You change one simple little thing in one place, and it ends up changing so many other things. A simple fix in one place can reveal a whole bunch of bugs that you had not seen.

So here is to hoping they can put collision back in soon!

Edited by Helbourne, 19 December 2012 - 03:29 PM.

[CheebaMech]

Solis Obscuri, on 19 December 2012 - 03:20 PM, said:

Fixing ECM > bringing back R&R costs > bringing back Collisions > Orion > everything else

bringing back Collisions>Fixing ECM>Orion>everything else>bringing back RnR costs
fixed*