10 replies to this topic

[JagdMeister]

It is the year 2013! Seemless integrated in-game VOIP is a no brainer! Seemless integrated VIOP would solve alot of the "ECM is OP" , "PUGing stinks", and various other issues that the most elegant work around and balancer is good communication.

This should have been the FIRST priority for this game.

BTW: I have had C3 installed configured and enabled in the game options since the press release, haven't heard a soul on it, but maybe it is just me.

[Karl Split]

Integrated voice would be nice aye, but the devs are prioritising fixing the game which i agree with tbh.

They have stated they will look at it in time. May i suggest joining a merc outfit and getting on their comms as a stop gap measure? Personally even with integrated voice ill probably just mute it in pug games I find many FPS shooters unplayable with voice comms as you always get a bunch of idiots endlessly spouting crap the whole time.

[WarGruf]

Hey Jagdmeister,
You know you have to search servers in C3 right??

I play on the MWO channel most nights with about 25 friends on my list and growing... There is also the Dropship servers which I think are based in Europe which I use somedays for UK morning hours / days off.

And I also agree that there needs to be a push for C3 Voip activation, but not at the expense of developing the netcode. I can't be far off finishing the basic code and after that I hope they take care of the C3 intergration so us Puggers can comunicate and fight collectively.

Your welcome to come join us on the C3 servers bud. MWO server gets busy around 4-5pm (PMT) 10-11pm (GMT) and there seems to always be someone on the Dropship chanels.

Happy hunting, see you on the dirt.

[SixstringSamurai]

I think the issue with no internal VOIP right now is that the protocols they use for voice in the CryEngine has been re-purposed to another task. There was a thread buried in here with someone asking what ports need to be opened and a Dev responded with what was what.

http://mwomercs.com/...number-for-qos/

Karl Berg, on 07 January 2013 - 03:12 PM, said:

These ports are still correct, and they connect over two different IP addresses, 70.42.29.74 and 70.42.29.75. The TCP ports don't include 45462 or 45463, we use only 45461 and 45464. The TCP ports are for backend server communications, things like logging in, interacting with mechbay, chat. The UDP ports are used for realtime match traffic to the dedicated servers when you're in-game.

Edited by SixStringSamurai, 15 January 2013 - 09:40 AM.

[JagdMeister]

@WarGruf
Thank you for the invite I may take you up on the offer. However, I disagreee with your assumption on resource allocation by PGI. They have stated in the past that the coders that work on X don't work on Y. I can see no resource reason to not complete the voice intergration to seemless conclusion.

Only through a seemless voice chat implementation will the new user base grow, be educated and "communicate around" things like ECM, Guass Cats, and LAG shield.

@SixStringSamuri
Thankyou for the technical insight. Sadly it illuminates the PGI failure all that much more. Why reinvent the wheel by cannibalizing existing speach support?

@PGI
In my opinion.... because you didn't start with seemless in game voice support, you lengthened your dev time for all things. And, hampered not only your PR compaign but went against your very public sales points of the metagame. Another thing, you probably should remove all written mention of Integrated C3 support as well as press releases... It is misleading, because it is not integrated at this time.

Edited by JagdMeister, 15 January 2013 - 01:38 PM.

[Gremlich Johns]

in-game VOIP will still not overcome the stealth aspects of ECM and the coverage it provide for ALL mechs within the ECM electromagnetic field. ECM also obviates the need for a true scout.

[SixstringSamurai]

JagdMeister, on 15 January 2013 - 01:37 PM, said:

@WarGruf
Thank you for the invite I may take you up on the offer. However, I disagreee with your assumption on resource allocation by PGI. They have stated in the past that the coders that work on X don't work on Y. I can see no resource reason to not complete the voice intergration to seemless conclusion.

Only through a seemless voice chat implementation will the new user base grow, be educated and "communicate around" things like ECM, Guass Cats, and LAG shield.

@SixStringSamuri
Thankyou for the technical insight. Sadly it illuminates the PGI failure all that much more. Why reinvent the wheel by cannibalizing existing speach support?

@PGI
In my opinion.... because you didn't start with seemless in game voice support, you lengthened your dev time for all things. And, hampered not only your PR compaign but went against your very public sales points of the metagame. Another thing, you probably should remove all written mention of Integrated C3 support as well as press releases... It is misleading, because it is not integrated at this time.

Because they completely changed how the CryEngine functions by taking it from a client side application to a server side application which is not how it was ever intended to work. To achieve this they had to rework the networking of the client.

[Buckminster]

But in-game voip does make communicating significantly easier. if I see an ECM'd Atlas, my instinct is to say (into a mic) "oh smurf, there's an ECM Atlas at location X" as I scamper away. I am not going to stop and type it out to the detriment of the health of my mech.

And while I understand there are lobbies out there that you can group up with and use chat, even C3, it really needs to be integrated like it is in a game like Left 4 Dead. There's no need to coordinate pre-match to be able to talk to your other team mates.

And while we're at it, I'd like to add that I think in-game voice chat should be team mates only. The biggest thing I hate with in-game voice in a game like TF2 is that there always seems to be some yahoo on the other team that won't shut up.

[JagdMeister]

@Gremlich
It is not a direct equipment counter to ECM. However, it would allow all, including the random PUG player, to shout out "Concentrate on the ATLAS in the broken dropship, it is running ECM", "I am running from 4 Ravens, circle the wagons", or "Kill the Raven that just came over the hill, it is ECM, aim 2 lenghts in front". Instead of taking you hands off of your controls in the middle of a fight to type the same. Along with making a dent in the loss of information ECM causes, by enabling the same type of efficient battle field communication that should be available in the far far future.

But really, the main reason it should be seemlessly integrated is for new players and to expand the playerbase. ALL of us Old TT BT players are getting old... like a car club or anyother hobby, it will die without new blood.... if this game fails I could very well not have a MW game to play in the Old Folks home.

Edited by JagdMeister, 15 January 2013 - 02:04 PM.

[Causticus]

While I completely agree that VOIP is necessary for good teamwork, I don't think haranguing the devs is going to get it any sooner, and as a software dev myself, I have to say that you have no idea what their task list looks like and I'm fairly confident they have everyone working with a full load. While VOIP is crucial to good strategy, it is not critical to good game play, and so far I have been pleased with each advancement they release. Basically, give it time.

Also, as a side note, I think it would be a neat effect (though certainly frusterating) if ECM affected the integrated VOIP to make it scratchy and patchy. It makes a logical sense that if they are disrupting your radar, they're going to disrupt your other EM functions, too.

[Frozen Winter]

Hrm well what if we didn't ask for VOIP? I mean what if instead we got a system like Tribes. Even being able to hit a button or two, then have the game shout out, "(Focus) Light Mech Alpha - G3" would be a powerful tool. Maybe add in some coding so that if multiple people hit it on the same target it would only shout it out for the first person (Spotter) so we don't get our ears spammed. I would prefer that to VOIP personally. I tend to keep my Teamspeak running all day so I don't really want more voices to drown it out. Plus it would use a little less bandwidth than VOIP which saves money which makes me happy for PGI.