Paul Surgeon > > On Saturday, 23 July 2005 14:04, Paul Kahler wrote: > > All this multiplayer "chat" stuff has me thinking "game". It would > > probably be more in line with simulation if chatting took place on a > > simulated radio. You'd not only have to be close enough to someone, but > > you'd have to be on the same frequency in order to talk to them. The > > idea of having little on-screen identifiers might be OK as long as it > > can be turned off. I really like that FGFS focuses on simulation and not > > game play. > > > > If you want to be highly realistic, mutiplayer voice chat with proper > > radio frequencies would be ideal. Bandwidth might be a problem for large > > groups, but small ones should be no problem. Of course it's much more > > complicated too ;-) > > > > I was going to comment on this earlier but decided not too since I may > step on > someone's toes. However since we are now on the topic ... :) > > The FS2004/IVAO network have voice comms working quite nicely. > If you tune your radio in FS2004 to an active frequency (within range) > TeamSpeak automatically connects to the server the frequency is hosted on > and > joins the channel. > This happens in the background and is totally seamless. > All you do is, tune to an ATC frequency and use the PTT key to make radio > contact. Just like one would in real life. > > TeamSpeak doesn't use huge amounts of bandwidth and on the client side > will > happily run on a 56K dialup with multiplayer running. > > Chat windows are fine for development purposes but are totally evil and > 1980's > technology when it comes to ATC. :P > In the early days of SATCO (pre VATSIM, IVAO) it was all text and it was a > major pain to fly and try to type at the same time. Even shortcut keys > used > to build text messages were a pain. > Getting a late landing clearance due to another aircraft clearing the > active > runway invariably meant an aerobatics display on short finals while trying > to > type a reply and configure for landing. > > One doesn't have to jump in the deep end by trying to implement all the > features in one go. > Someone can simply host a TeamSpeak server and create a KSFO_TWR channel > which > the pilots can join. > Then when things get more busy we can add KSFO_APP, KSFO_CTR, UNICOM, etc. > Getting TeamSpeak to switch servers and channels by tuning the radios can > come > at a later stage. >
This has already been discussed. Teamspeak in not GPL'd. I think the licensing arrangements would give us problems. That would be a pity, because on the face of it, it's pretty much what we want. Certainly it's the right way to go though. Vivian _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
