39 replies to this topic

[RumRunner151]

<shakes head>
1) It was pulled because it was borked.
2) It needs net-code fixed before it can be brought back.
3) Testing of new net code will start internally soon. Keep your fingers crossed.
4) Different people work on different things. Its like saying I want my sink fixed before my refrigerator. Different people so it can all be worked on at the same time. (and in the case of net code, collisions, and other content/fixes it is all being worked on concurrently)

http://mwomercs.com/...t-code-roadmap/

[TB Freelancer]

RumRunner151, on 19 December 2012 - 03:35 PM, said:

<shakes head>
1) It was pulled because it was borked.
2) It needs net-code fixed before it can be brought back.
3) Testing of new net code will start internally soon. Keep your fingers crossed.
4) Different people work on different things. Its like saying I want my sink fixed before my refrigerator. Different people so it can all be worked on at the same time. (and in the case of net code, collisions, and other content/fixes it is all being worked on concurrently)

http://mwomercs.com/...t-code-roadmap/

That somewhat sums it up...

...and I always kinda shake my head when I read moronic posts like this one where some chucklehead demands 'x' be patched ASAP...whaaa whaa whaas, while in the meantime PGI has quite clearly explained why it was pulled out, what needs to be done before its re-introduced and that it will take time.

This entire thread is inane.

[Glythe]

Collisions need to return as lights are the supreme chassis right now. But there is something much worse.... although it is tied to collisions.

I can't wait for them to get rid of the clipping through the enemy garbage...... I'm so tired of enemies clipping behind my Atlas when there is no way they could slip past me on the terrain. I know it was low on the priority list but I want to see Atlases punching anyone who comes in range (instant knockdown on medium to light mechs)

[Jman5]

As others mentioned, Netcode problems are the reason collisions were removed. You would knock someone over and they would appear on your screen in a different place. Then they stand up and warp to where they actually are from the server's perspective.

Once they improve netcode enough, which is the number 1 priority, collisions get re-introduced.

On top of that, they will also roll out a number of other things being held up by faulty netcode like 12 v 12.

Edited by Jman5, 19 December 2012 - 03:55 PM.

[Fajther]

+1

[BlackBeltJones]

Without collisions I feel that lights are playing "Hawken" mode within MWO.

[Hillslam]

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

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

Leaving ECM the way it is, its perfect > giving you a cookie > bringing back Collisions > bringing back R&R costs > Orion > everything else > another cookie


Seriously though the collision and FALLING need put back in asap.

Edited by Hillslam, 30 December 2012 - 11:25 AM.

[verybad]

Different Developers work on different things. The guy working on getting physics to work properly with the netcode isn't the same guy working on balancing weapons stats.

They are working on it, it's a more complex technical issue than balancing stats (which aren't technical so much as feedback based) Sying it should "be the most important thing they should be working" on is meaningless. It's not one guy working on the whole game, it's different people with different skills. The artists/modelers wouldn't know code from candy in most cases and vice versa.

[siLve00]

no it shouldnt...

programcode ( aka disconnects/launcher problems ) after that is fixed netcode netcode netcode netcode........ period.

if that is fixed you dont need anymore knockdown when 100% of your laser shots will hit a light mech instead of only 25% ( if your even skilled enough to aim torwards them )

knockdown would be a nice gift but it doesnt realy fix the major problems of MW:O

[o0Marduk0o]

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.

You don't trip light mechs. Other light mechs trip them so their teammates can shoot them.

[Corvus Antaka]

Nadia Winson, on 19 December 2012 - 01:42 PM, said:

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.

No death from above = no interest in MWO.

[siLve00]

Colonel Pada Vinson, on 30 December 2012 - 12:01 PM, said:

No death from above = no interest in MWO.

i did hear super mario got some awesome death from above skills.. maybe that game would fit better ?

[MadcatX]

CheebaMech, on 19 December 2012 - 03:27 PM, said:

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

Fixing FPS/Yellow Screen/CtD bugs > then anything else.
further fixed*

[Bluescuba]

+1

[Liberty]

Um... For all the heavies out there gleefully anticipating collision thinking they can push over lights for fun and laugh. Collision damage in tabletop Battletech was called charging and is based on the tonnage of the mechs and the velocity of mechs. I can see all the new complaints when a full speed Jenner or Cicada collides with you. Sure it will jack that Light or Medium up and maybe even kill it if it is already damaged prior to collision. However it is an almost guarantee that you will be legged given the height of the Light Mechs and Cicada compared to an Assault. A light about to die will now likely suicide just to leg you and let his team finish you off. This is assuming they consider collision a Mechwarrior/Battletech charging attack. I'm bracing for the new onslaught of complaints against lights but in this case if you wanted it then you shouldn't complain when it happens since charging was a valid mechwarrior attack in the game. Heh, and if you think the Jenner was bad plowing into you. Wait till you get smacked by a charging Dragon in a full decked out XL engine.

[Flashdance]

I would gladly trade a leg for the light kill........the way it is now....the light would just run around firing streaks while all the shots that should be hits go unregistered. Seems like a good trade off. One less light on the battlefield.

Edited by Flashdance, 30 December 2012 - 01:53 PM.

[Sears]

I assume Collisions will be reinstated along with the charge mechanic, rather than be put in before that. Not sure when the charge mechanic is slated to be put into the game.

[Bluescuba]

Oh we dragon pilots love to charge

[General Taskeen]

Nadia Winson, on 19 December 2012 - 01:42 PM, said:

The devs have stated they will not be adding melee

Huh? They didn't say that. They said they would like to add Melee in the future, but they want to get it right the first time. First there will be a better collision system (and possibly jump jet attacks, DFA), then post-release they may work on a melee system.

[Hillslam]

Speaking as an Atlas founder - I'll take collision damage with this hypothetical Scout Missile Suicider any day. If I calculate the damage from my old TT rules right, a Jenner at full speed won't leg me. And even if it did - legs? Assaults dont move

I tripped a metric sh.1.t-ton of lights before they took out the code. One of my favorite tactics. Few things more satisfying.

As for the Dragon pilots swinging their big appendages... Atlas at 60kph. Enough said.