Forums » Suggestions
Rather then have 20 some odd different threads about it, why not post them all here?
I'd like to see a voice chat to guild setting.
I'd like to see a voice chat to guild setting.
I would like to see voice hails.
I'd like to see voice chat to sector.
I'd like to see this thread stickied. I think a guild voice chat is a marvelous idea. Voice hails are fine (as long as they are recorded beforehand)
I decided to repost my idea from another thread in here:
Channel selection: Make it like UHFS: you have to actively select the channel, and can only talk to that one channel. Others may be able to listen in, but only one person can talk at one time on one given channel. Channel setup, as I envision it, might look like this:
- hailing channel. Strictly ship-to-ship, no-one can listen into it besides the target. Slight flooding protection (15 seconds hailing delay)
- group channel. Only members of the group may monitor. Flooding protection (15 seconds hailing delay). Groups have a 'moderator' (the leader), s/he can mute and unmute people.
- sector channel. Only players in the same sector can hear it. Stronger flooding protection (30 seconds)
- system channel. Only... you get it. (45 seconds)
- nation channel. See above. (60 seconds)
- guild channel. Perhaps 45s, too? And who would moderate? From council upwards? Or only ell-tees and cee-ohs?
Now, for channel selection:
If you target a ship and hit the 'talk' button, your channel is limited to that one ship, always.
If you are not targetting another ship, you can choose, either from your PDA or, via bindable commands, directly from your HUD, which channel to chat to.
Once a player is chatting on that channel, he cannot be interrupted until he hits a time-out (much like the chat line limit, perhaps 30 seconds? after that, the hailing delay starts, to give the other girls and guys a chance to talk), i.e. that channel is 'full'. Exceptions to this: group and guild channels, the moderator may cut in (after the hailing delay).
What do you think?
Channel selection: Make it like UHFS: you have to actively select the channel, and can only talk to that one channel. Others may be able to listen in, but only one person can talk at one time on one given channel. Channel setup, as I envision it, might look like this:
- hailing channel. Strictly ship-to-ship, no-one can listen into it besides the target. Slight flooding protection (15 seconds hailing delay)
- group channel. Only members of the group may monitor. Flooding protection (15 seconds hailing delay). Groups have a 'moderator' (the leader), s/he can mute and unmute people.
- sector channel. Only players in the same sector can hear it. Stronger flooding protection (30 seconds)
- system channel. Only... you get it. (45 seconds)
- nation channel. See above. (60 seconds)
- guild channel. Perhaps 45s, too? And who would moderate? From council upwards? Or only ell-tees and cee-ohs?
Now, for channel selection:
If you target a ship and hit the 'talk' button, your channel is limited to that one ship, always.
If you are not targetting another ship, you can choose, either from your PDA or, via bindable commands, directly from your HUD, which channel to chat to.
Once a player is chatting on that channel, he cannot be interrupted until he hits a time-out (much like the chat line limit, perhaps 30 seconds? after that, the hailing delay starts, to give the other girls and guys a chance to talk), i.e. that channel is 'full'. Exceptions to this: group and guild channels, the moderator may cut in (after the hailing delay).
What do you think?
I've said it in your other thread: The delays are too long.
It's not 'my' thread. What would you make those delays, to have a built-in flood protection? Or, rather, how would you provide protection against that?
That is a good framework for the overall structure of voice chat Toshiro.
The times for group and guild seem a bit of the long side, I'd say about 5 seconds, but that is something that could be fine tuned with experience.
As a starting point the other delays seem sensible.
For guild chat moderation by council upwards would be my choice, group leader for groups.
With regard to hailing I think that the existing text hail message should always be displayed with extra text indicating that it is accompanied by a voice hail. The hailer should get a feedback message to say that the target has received the voice hail.
Clearly /ignore should be extended to voice chat .
The times for group and guild seem a bit of the long side, I'd say about 5 seconds, but that is something that could be fine tuned with experience.
As a starting point the other delays seem sensible.
For guild chat moderation by council upwards would be my choice, group leader for groups.
With regard to hailing I think that the existing text hail message should always be displayed with extra text indicating that it is accompanied by a voice hail. The hailer should get a feedback message to say that the target has received the voice hail.
Clearly /ignore should be extended to voice chat .
I think having "voice chat moderators" is a bit much, just extend /ignore and /mute to voice chat so the player base can moderate itself. Also I don't see the need for system/sector voice chat, as it will mainly be used as groups/guilds. Nation wide voice chat maybe.
Time delays? I've spoken to like a group of 12 on other VOIP clients with no needed time delays. If two or more people speak at the same time, well it can end up garbled, but usually they will repeat them selfs one at a time. And if someone starts flooding the channel with music or crap, well, just /ignore them.
Time delays? I've spoken to like a group of 12 on other VOIP clients with no needed time delays. If two or more people speak at the same time, well it can end up garbled, but usually they will repeat them selfs one at a time. And if someone starts flooding the channel with music or crap, well, just /ignore them.
yoda, the 'moderator' would only be active in group and guild chat, where there is a true hierarchy present (and where one may be actually necessary). The rest of the open voice chat channels would work perfectly fine with ignore and vote mute, imo. But those two, where it can be crucial to silence detrimental elements, should have it.
I think the system needs a built-in flood protection, not only against abuse, but against accidental misuse, as well, especially when things are time-critical.
The values I listed (and the override features) are based on personal experience from military radio communication, which makes them both true and flawed at the same time.
I think the system needs a built-in flood protection, not only against abuse, but against accidental misuse, as well, especially when things are time-critical.
The values I listed (and the override features) are based on personal experience from military radio communication, which makes them both true and flawed at the same time.
This isn't stored audio hailing, this is wide open conversation and conversation is a flow.
Players should be able to listen or not listen to as many channels as they like, and regardless of defaults, hail harrasment should be controlable by those being harassed.
A new channel should open automatically when you are hailed, but not be audible. The receiving player has to open the channel, much like accepting a duel or answering a phone call. This request remains open for as long as it takes for the player to allow or ignore. Once ignored, the request can be repeated but will be automatically ignored for a time chosen by the receiving player.
This way if the conversation is not mutually consensual, it doesn't happen, and there is no way for an idiot player to harass via hails more than the receiving player allows. I may want to ignore permanently, while you may just love hitting that ignore button every 3 seconds.
Each player then is allowed to choose to broadcast to any one of, or multiple channels that they have open.
The software should detect if two channels contain the same person/s, (E.G. Group/Guild) and mute out the broadcasts from a player on one of those channels to prevent duplication.
Players should be able to listen or not listen to as many channels as they like, and regardless of defaults, hail harrasment should be controlable by those being harassed.
A new channel should open automatically when you are hailed, but not be audible. The receiving player has to open the channel, much like accepting a duel or answering a phone call. This request remains open for as long as it takes for the player to allow or ignore. Once ignored, the request can be repeated but will be automatically ignored for a time chosen by the receiving player.
This way if the conversation is not mutually consensual, it doesn't happen, and there is no way for an idiot player to harass via hails more than the receiving player allows. I may want to ignore permanently, while you may just love hitting that ignore button every 3 seconds.
Each player then is allowed to choose to broadcast to any one of, or multiple channels that they have open.
The software should detect if two channels contain the same person/s, (E.G. Group/Guild) and mute out the broadcasts from a player on one of those channels to prevent duplication.
UHF is conversation, as well, only that one partner waits for the other to end before he speaks. That's how it ought to be in real-life discussions, as well, by the way.
The hailing confirmation makes sense, of course. And I might have added that vote mute and ignore were a given in my setup, I do so now.
But I really think that with the multitude of different channel levels, it should be more organized than you say, PsyRa. Especially channel selection needs to be more specific. Also, I do not think that it would be wise to broadcast to multiple channels at the same time. Other people can listen in on as many channels as they want, but broadcasting to more than one channel should not be possible, in my opinion (you can currently only chat to one single channel, while listening in on a multitude, too, by the way).
The hailing confirmation makes sense, of course. And I might have added that vote mute and ignore were a given in my setup, I do so now.
But I really think that with the multitude of different channel levels, it should be more organized than you say, PsyRa. Especially channel selection needs to be more specific. Also, I do not think that it would be wise to broadcast to multiple channels at the same time. Other people can listen in on as many channels as they want, but broadcasting to more than one channel should not be possible, in my opinion (you can currently only chat to one single channel, while listening in on a multitude, too, by the way).
Hi, just a heads up to say we're making progress on implementing some of the fundamentals to make these ideas work. The current VO client can only have a person be in one voice-chat channel at any given time, but we've gotten some new information on how we can expand on that; plus we're also working with the other company to possibly add some new features that'll help these sorts of things (like being able to set the volume of "background" voice channels, to keep background chatter from being overwhelming, etc).
So, FYI, please keep the ideas coming, we're looking into how to.. make them work.
So, FYI, please keep the ideas coming, we're looking into how to.. make them work.
A minor thing that I would find useful: Currently audio ducking cuts in whenever anyone is talking, including yourself. This often makes me think that someone else is trying to talk at the same time as I am, and causes confusion (mostly in my head, but there it is). If there is no compelling reason to keep ducking for the person speaking (outside noises shouldn't be a problem when you're the one talking) then I would very much like to see at least an option to have ducking turned off for the speaker and on for all others. So far it's going great, it seemed to help a lot in NW today!
I've noticed occasionally firing my weapons causes all my audio to drop out.
In terms of voice hails, I would like to see them pre-recorded, and a little button in the voice chat settings that says "accept voice hails", so you can ignore them if you want. When you hail, you automatically send both, and if your target doesn't accept voice hails, they still get the text one like normal.
In terms of voice hails, I would like to see them pre-recorded, and a little button in the voice chat settings that says "accept voice hails", so you can ignore them if you want. When you hail, you automatically send both, and if your target doesn't accept voice hails, they still get the text one like normal.
I like the idea of hailing opening a channel, kinda like in star trek, /ignore extending to voice chat would work wonders, especially if it blocked voice hails.
"I think the system needs a built-in flood protection, not only against abuse, but against accidental misuse, as well, especially when things are time-critical."
Abuse i think could be stopped with /ignore, group/guild leaders should have mute powers within the group/guild. As for accidental misuse, that happened to be my first use of the voice chat. I forgot I had my cable box plugged into the comp, was streaming whatever was on VH1 classic at the time (the tv was off so I didn't know what it was). Even with PTT it's still possible to accidentally walk away for a second and have something hit the PTT button.
Having channels sounds like a good idea for voice chat, just like we've got text chat channels, you can monitor several and only chat on the active channel.
Also, Sticky please? rather not let this sink way down and have some noob catch flak for makeing a new thread for a voice chat suggestion.
"I think the system needs a built-in flood protection, not only against abuse, but against accidental misuse, as well, especially when things are time-critical."
Abuse i think could be stopped with /ignore, group/guild leaders should have mute powers within the group/guild. As for accidental misuse, that happened to be my first use of the voice chat. I forgot I had my cable box plugged into the comp, was streaming whatever was on VH1 classic at the time (the tv was off so I didn't know what it was). Even with PTT it's still possible to accidentally walk away for a second and have something hit the PTT button.
Having channels sounds like a good idea for voice chat, just like we've got text chat channels, you can monitor several and only chat on the active channel.
Also, Sticky please? rather not let this sink way down and have some noob catch flak for makeing a new thread for a voice chat suggestion.
Ok, here is another suggestion:
Please put some test button in the option voice chat panel, so you can check your setup, esp. whether the mic is working. Something similar like the Skype Testing Call should do, where you can record your voice for some seconds and get it replayed.
Please put some test button in the option voice chat panel, so you can check your setup, esp. whether the mic is working. Something similar like the Skype Testing Call should do, where you can record your voice for some seconds and get it replayed.
When in the voice chat dialog, audio coming from you will echo back through your speakers instead of transmitting.
JJPro, I like that idea.
uh, slime, I didn't notice that because my mic didn't work...