In game voice

Questions / Announcements area for beta tests of Allegiance's future updates.
notjarvis
Posts: 4629
Joined: Tue Jun 03, 2008 11:08 am
Location: Birmingham, UK

Post by notjarvis »

derfmancher wrote:QUOTE (derfmancher @ Oct 20 2009, 07:32 PM) I think that would be an excellent idea. The solution to me sounds like to use a newer version of directx, or to totally change protocols.
How hard would it be to entirely remove Directplay from the code?
It's a substantial rewrite of a big comms class, and all the dependants which use the types. It's boring code too, which is why no-one has done it yet. Not to mention you would probably need at least a spare PC in your house to test and debug your code properly. I looked it up at one point. if I've time I'll look into it some more at some point.


DirectX may no longer provide a communications layer at all. The recommendation from Microsoft is to use Windows Sockets to roll your own comms layer/class. (the justification Microsoft used for this was that Directplay was outdated, being initially designed for small scale LAN games, and the job could be done better by other means.....)



Edit: pkk posted while I was waffling and he's right - it is not totally removed, there are just no headers and library to develop with DPlay in newer versions of DirectX.

QUOTE No single word about total removal of DirectPlay on Vista. ;) [/quote]
Sorry -the correct word I should have used was deprecated.
Wwe cannot rely on it permanently
http://msdn.microsoft.com/en-us/library/bb318767(VS.85).aspx

They may be fully removed in the future, and the directplay headers and librairies are not in the SDK since Aug 07.
Last edited by notjarvis on Tue Oct 20, 2009 8:03 pm, edited 1 time in total.
derfmancher
Posts: 77
Joined: Sat Sep 12, 2009 11:30 pm
Location: Idaho

Post by derfmancher »

So basicly the big boys got lazy. Hmmm.. sounds like something to put into R6. :D
Image
Your friendly forum derfmancher.
Feel free to call on me when the fit hits the shan.
"Any ship can be a minesweeper ... once." - Admiral Hornblower
pkk
Posts: 5419
Joined: Tue Jul 01, 2003 7:00 am
Location: Germany, Munich

Post by pkk »

notjarvis wrote:QUOTE (notjarvis @ Oct 20 2009, 09:51 PM) DirectX no longer provides a communications layer at all. The recommendation from Microsoft is to use Windows Sockets to roll your own comms layer/class. (the justification Microsoft used for this was that Directplay was outdated, being initially designed for small scale LAN games, and the job could be done better by other means.....)
Or use XNA 2.0 or higher (Which means to port the whole Allegiance code from C++ to C#)... ;)
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
fuzzylunkin1

Post by fuzzylunkin1 »

Or find a non-Microsoft solution (of which I know none).
Orion
Posts: 1733
Joined: Tue Jul 01, 2003 7:00 am
Location: Planet Min·ne·so·ta
Contact:

Post by Orion »

pkk wrote:QUOTE (pkk @ Oct 20 2009, 03:07 PM) Or use XNA 2.0 or higher (Which means to port the whole Allegiance code from C++ to C#)... ;)
*balks*
Image
fuzzylunkin1

Post by fuzzylunkin1 »

derfmancher wrote:QUOTE (derfmancher @ Oct 20 2009, 03:00 PM) So basicly the big boys got lazy. Hmmm.. sounds like something to put into R6. :D
If it works there's no reason in fixing it this was never a priority behind oh, DirectX 9 graphics?

I actually am very interested in working on this and I'm going to be looking up different possibilities for replacement of the deprecated DirectPlay code. Going to be a huge learning experience on my part.

Maybe if I go crazy enough I'll start doing OpenGL, too :o .
deathgoat
Posts: 517
Joined: Sat Apr 07, 2007 3:50 am
Location: beyond the permafrost

Post by deathgoat »

even though i think it is a good idea if implemented....

one of the reasons I play this game is because i can... it is currently still moderately dialup friendly....

the addition of this will surely make it unplayable for any dialup connection ( i cannot currently use TS)



-- (not like anyone really cares about dialupers)--


my 2c
Image
fuzzylunkin1

Post by fuzzylunkin1 »

deathgoat, we could easily have an option to enable/disable voice chat.
Broodwich
Posts: 5662
Joined: Fri Oct 19, 2007 3:48 am
Location: Raincity

Post by Broodwich »

QUOTE Drizzo: ha ha good old chap
Drizzo: i am a brit
Drizzo: tut tut
Drizzo: wankarrrrrr
Drizzo: i only have sex whilst in the missionary position[/quote] Fas est et ab hoste doceri - Ovid
Jimen
Posts: 1146
Joined: Mon Aug 31, 2009 10:39 pm
Location: Boston-ish

Post by Jimen »

It's worth noting that if it becomes a feature, everybody will be expected to use it. Say what you like about making it an optional setting, but everyone who has a mic will use it instead of text chat, so anyone who doesn't have a mic will have a hard time getting info out, and those who disable it for whatever reason get next to no information. It's already hard enough to get everyone to read the chat in a PUG, despite it being the only way to communicate; make looking at the chat optional, and things just get worse. Of course, it's a lot more difficult, logistically speaking, to log voice chat. Having voice chat be relegated to TeamSpeak, an optional program, mostly solves these problems; if you give Allegiance official voicechat support, then just letting people opt out of it isn't going to fix any of voice chat's inherent problems. You can completely disable voice chat in Xbox Live too (or at least you used to be able to), but try playing a team game in absolute radio silence because everyone's only sharing info over the voice channels you disabled.
Image
Post Reply