~S~ All,
I didn't want to hi-jack Dave's Solomon thread, so here is a new one...
QuoteAs with this mission, or any upcoming mission, I welcome all constructive and "off the wall" comments - Dave
In light of the separate comms, I heard several times, "oh, I forgot, they are not on our comms..." or something to that effect....not to mention that I am not that versed (such as DW) to write a novel in the chat bar...
Perhaps, the Squad Leaders can open a separate comms (much like we did for the recent TD memorial) so we can relay information, sightings and help if needed.... that way we get the best of both worlds...
Any suggestions....
Wood
I think we should just all stay on the same comm... over complicating things is whats happening here i think... always worked before.. as a fighter pilot i couldnt hear or know when the SBDs were in trouble or where they were.. separate comms, in my opinion .. is very ineffective... just my 2 cents..
Quote from: _AH_Hollywood on April 12, 2017, 10:45:55 PM
Perhaps, the Squad Leaders can open a separate comms (much like we did for the recent TD memorial) so we can relay information, sightings and help if needed.... that way we get the best of both worlds...
Wood
S~ All,
As with any "new" methods there are going to be some minor hick-up's. I also noticed guys stating "they are on a different channel", I do like Wood's suggestion that the Squad Leaders communicate with each other. This would be very similar to how communications operated during this period.
I understand that some here would just like a singular channel. To these folks, this was the 1st mission ... let's try and let the Squad Leaders lead their squads and give the comms a bit more of a chance over the next few missions. If the comms become an issue ... we can always go back to a to single channel.
The idea was to provide a bit more realism and reduce the amount of comm's chatter from 20+ pilots, to a manageable 8 pilots, allowing the Squad Leaders to position their pilot's where needed.
However, the whole idea of this campaign is to have "FUN" ... so, if the comm's become an issue, we'll go back to a single channel if that is what the group would like. :)
We will stay on separate comms for now.
Like woody mentioned, perhaps a whisper channel can also do the trick.
Squadron leaders, do the best you can to keep your pilots together. That will also help.
S!
Zip, Zang Bang!!!
Feeling good about this...
Bear... Let's roll with it..... Wasn't so bad yesterday, 2 out of 3 were on the same comms...
Fighter cover needs to hear help is needed tho..
Concise, Grid location Alpha and Number, Alt and Size of Force...
Bear, not to worry...you didn't miss any of Jack's jokes....
Wood
RGR THAT
I like the separate comms when in combat, easier to talk to the flight. However, asking for help or warning another pilot who is on a different channel is a problem. A while ago I worked on what I thought was a useless project that might help today. see link below, just click on picture, it should start to play.
https://goo.gl/photos/4X656qWyvu9stjYB9 (https://goo.gl/photos/4X656qWyvu9stjYB9)
when do they go on sale twenty!
pretty neat!
that's cool... are you ready to build 24 of them?
Holy S***, that is F******* Awesome!
I'm going to have to order you to build one of those for each pilot.
As your commanding officer, you will build one for me first and then proceed onto building the others.
Funds will be made available from "Jack's Birthday Bank", he won't be with us too much longer as he is old...
!!!!!S!!!!! (<-- That means I'm in my dress uni).
After we attacked the 1st wave, Wilder and I scouted ahead and met up with the 2nd wave at the end of the waypoints... we tried staying high and let you all know but typing isn't a skill i have learned to combine with flying.. we both were taken out by the zeros in that group after making a combined 4 kills.. woulda been nice to call out to others for help... just saying.. im not a fan of split comms.. all it seems to afford is more air time for personalized chat until the action happens.. we miss out on having the ability to help each other and divide ourselves making it easier to be conquered... if we were in different areas on the map with different goals etc, i can see the advantage .. but not when were all on the same mission... flying as a group... taking on a common enemy .. makes no sense to me at all...
Just my 2 cents
Until Twenty makes us all his gadget that is .. :happy-112:
Quote from: _AH_Twenty on May 03, 2017, 11:58:11 PM
I like the separate comms when in combat, easier to talk to the flight. However, asking for help or warning another pilot who is on a different channel is a problem. A while ago I worked on what I thought was a useless project that might help today. see link below, just click on picture, it should start to play.
https://goo.gl/photos/4X656qWyvu9stjYB9 (https://goo.gl/photos/4X656qWyvu9stjYB9)
you need to start a Go Fund Me page for that...
That setup is nice Twenty, One for each squad leader maybe? Got a schematic for that twenty? I have my own soldering iron. Since our squad channels are close together maybe a simple previous or next channel switch would work ok. I will have to look into My G keys on my G15.
Got a schematic for that twenty?
Got a schematic for that twenty?
Got a schematic for that twenty?
Got a schematic for that twenty?
kaw
I can create schematic, and even build a few if wanted (flight leads and HQ). It shouldn't be that that expensive if only the flights and red and blue are switchable (5 switches). The project shouldn't completely drain the Jack fund.
S~
Cool Switch, Twenty.
Of course there's always the option of using a bind in vent. There are two possible shortcomings of a bind though.
What I'm talking about is flight leads setting a key or button that will transmit across channels to only the other flight leaders. Technically it would be a virtual channel for flight leaders.
Flight leads would be on their respective channels, and by using a different transmit key would broadcast to only the flight leaders no matter what channel they are in.
I've only spent about 45 minutes researching how to set it up which is why I mentioned possible drawbacks. It looks there are a couple ways of setting it up. The first way is the virtual channel, but the drawback there is if a flight leader is absent there would be additional set up needed to add that substitute flight leader to the virtual channel and having the sub lead also set up a second PTT key - which sounds a little fussy to me.
Since I'm early into figuring this out, I'm not sure but I might be able to set up flight leaders to be able to broadcast to the other channels and ( this part I'm not sure about yet) at the same time have only the flight leaders hear it. I saw something about users muting cross channel talk but need to look at it more to be sure it's what I'm hoping it is.
We've tried broadcasting into other channels before and a lot of the time having some one transmit blindly across channels ends up gumming up comms for the channel they're trying to broadcast to because they can't hear anything from that other channel, a lot of the time it just ends up being cross talk and not understandable. The part I'm not sure about is having only one person on a channel receive a cross channel transmission. If that's possible I think that would be the way to go. No extra set up other than the sub flight leader setting a bind and a second key to talk across channels - which is pretty easy and quick. We're talking a few clicks on a couple drop down menus in vent. Which I'll supply a how to for once I've figured out what'll work best. Might have something more later today since it's supposed to rain all day here.
Having said all that, those switches look pretty fun and no extra keys taken - which I know can be a problem for some.
S~
I just set up a cross channel bind in vent - way easier than I thought it was going to be. The only drawback is the extra PTT key flight leads would need - which is where Twenty's switch would be handy. ORRR - you can use the same key you always use and your channel and the other flight leads would all hear you.
It's super quick and easy to create the bind as long as you can spare a second key so substitute flight leads shouldn't be a problem like I was thinking in my previous post. Should take less than a minute for a sub flight lead to set up a cross channel key/bind, even less time for the other flight leads to edit their bind to include him for the mission.
There is an option to mute others on the channel you broadcast to.. not sure if we want that or not. I'm going to flip a coin and post a how to for one way, and we can try it. If we don't like it, we'll try it the other way.
Here's a quick look at how to do it: http://www.noobgalore.us/ng-public-ventrilo-server-61/tutorial-how-private-bind-vent-32572/ (http://www.noobgalore.us/ng-public-ventrilo-server-61/tutorial-how-private-bind-vent-32572/)
The only thing we'll do differently is select Voice Target instead of U2U. Voice Target allows multiple people to hear you across multiple channels.
EDIT: Might have to make sure flight leaders are set up with a password or are at least on comms when setting up voice targets.
I noticed when I was the only one on comms there was a list of several AH there,but not everyone. I tried editing the guest user group to be able to set binds, but I don't know if it stuck. I tried editing individual users that are for some reason listed in vent even when you're not there, but when I did that Vent wanted passwords so I cancelled out of it.
QuoteAfter we attacked the 1st wave, Wilder and I scouted ahead and met up with the 2nd wave at the end of the waypoints... we tried staying high and let you all know but typing isn't a skill i have learned to combine with flying.. we both were taken out by the zeros in that group
You and Wilder scouted ahead alone?
We were high on them and perhaps should have tryed to stay away, but the zeros came up to us quickly.. we were forced to engage .. i remember i could see others we weren't in comms with close by but we couldn't communicate quick enuf, while i was trying to type i lost sight of the enemy, they gained advantage and I was killed, Wilder shortly after
Did KW get shot down? I have him as survived. Maybe I need to review the track.
Awww... KW's I see you got hammered.... let me fix the scoring...
S~
Here's a How 2 with screen shots for setting up a bind to talk across channels in Vent.
They're pretty quick and easy once you know the steps. They're also easy to edit and delete.
Here: https://www.dropbox.com/s/tfepmpiyfk5n2da/How2Bind.doc?dl=0 (https://www.dropbox.com/s/tfepmpiyfk5n2da/How2Bind.doc?dl=0)
If Vent is not showing you the options listed in the How2, it might be because you are not using a password to log onto vent. If you find this to be the case, let me know and we'll fix that.
I need to find the time to read BBQ's thread... in the meantime, is there a way to set up key that will move me to other channels?
I have CH stick, throttle etc.... lots of extra buttons... could I assign a button or key to move to from Aixs Blue to Allied Red etc... Make sense?
I try it it look like you need a password for Ventrilo to get it holly! and yes you can used your button on your throttle are your joystick to switch over
Quote from: _AH_Hollywood on May 07, 2017, 07:07:27 PM
I need to find the time to read BBQ's thread... in the meantime, is there a way to set up key that will move me to other channels?
I have CH stick, throttle etc.... lots of extra buttons... could I assign a button or key to move to from Aixs Blue to Allied Red etc... Make sense?
That would be great
S~
Yes there is a way to switch channels with the Bind feature. Start the same as in the how 2 set up binds 2 clicks, name the bind, click add and select switch channels, don't forget a button to get back to your original channel.. and about three more clicks.
You'll just need a button for each channel you want to be able to move to. Likewise with individual user binds, too. That's why I was thinking Voice targets might work best. each flight leader would add 1 button and that 1 button would broadcast to all of the other flight leads. There's also a feature there that would allow muting of everyone else speaking on any channel you're broadcasting to when you broadcast to a voice target. That way you wouldn't have to repeat yourself nearly as often.
The binds are really easy and quick to set up. I'm talking less than a minute once you've done it a couple o times. But they do require an extra button. More if you would rather use channel switching or be able to speak to multiple people individually on different channels.
if we have time before or after the meeting i can show you how. Should take about 3 minutes since it'll be your first time - just like nevermind (tongue)
Are going employ this new bind setup for Tuesday Night guys I have not looked into yet but been reading and sounds like a good work around.
I was hoping to discuss it at the meeting but you're not there
LOL thats what I get for coming here before loging into vent
S~
As it turns out, in order to use Voice Targets we need to use passwords. Without a password, it won't allow the rights. I don't want to lock anyone out of Vent by setting passwords and sending emails and hoping they, or you, find the email before trying to log on.
If you want to email or message a password to me, I can set it and email you that it's done if you want.
Hopefully I'll see most of you flight leader guys Monday night and we can get you set up.
There are other perks to having a Password, too. Unlimited duplicate connections, you might get to see the Message of the Day when it changes, and you might even be able to drag people to different channels.
S~
This is the current list of people that have accounts registered on Ventrilo:
_AH__Skattrash
_AH_Archie
_AH_BBQhead
_AH_Bear
_AH_Col_Hogan
_AH_DarkWolf
_AH_Jack
_AH_Olds
_AH_Turbo
_AH_Twenty
_AH_Hollywood
_AH_Gatlingun
_AH_Shrtaprch
_AH_Gator
Using a password will enable more features on Vent for you. So, if you're not on the list yet I'll be bugging you to set up a password. Just need to set it once, and then you won't even notice except for the new rights you'll have on Ventrilo.
Quote from: _AH_BBQhead on May 08, 2017, 02:22:08 PM
So, if you're not on the list yet I'll be bugging you...
Welcome to
my world you unregistered buggers!
DW
I thought I was on the list set it up a few years back to move peeps from one channel to another fopr training. Anywho I will discuss this further and set it up so I can do comms right.
S~
Looks like we've got the cross channel coms sorted for flight leaders. Well done, guys. User to User is what worked. The Voice Target option was fighting back.
I'll look into why the moving users to different channels part isn't working. I expect to have a solution tomorrow or the next day.
Thanks again to the guys that are using passwords now.
The plan is to have at least all HQ and Flight Leads using passwords so they can have access to more of the features vent offers.
For the rest of us, passwords are currently optional. Recommended, but optional. If you want a password, let me know and you'll get one.
thanks BB great job setting this up.
S~
Always happy to help when i can, and right back at ya. Thank all of you guy for your indulgence and patience while we work the bugs out.
I know Bear was having an issue early in the mission last night, but was able to get it working while in flight.
After Bear spoke to the other flight leads he could no longer hear the people on the channel he was on. I think he fixed it after a couple of tries of unloading and reloading the bind. Which is the part that concerns me the most -not knowing what caused the problem and not being able to pin point the fix.
My first guess is the "Mute inbound Streams option" being checked - which I think I recommended thinking it would mute others only while he transmitted across channels, not permanently. I'm not sure if that was unchecked during Bear's in flight troubleshooting session or not. Troubleshooting vent while flying- that had to be fun.
Did anyone else using their U2U bind find their own channel muted once they spoke across channels?
Hoping to have a block of time today to figure out how to enable any AH member ( that uses a password) to be able to move other people onto different channels, and also look into the problem Bear was having. Depends on how long I can deal with trying to get my :censored-015: :censored-015:piece of :censored-015: :censored-015: that is my :censored-015: jib again today since the weather looks right for it.
S~ All
I've made some changes to the Vent server. If you are having trouble logging on, shoot me a PM, or you might be able to create a new username and log on with no password. <----- Not expecting that to happen, but just in case it does you can still get on comms.
If you use a password you should be able to move people around to different channels now.
If you are HQ or a flight leader:
You can add, edit users passwords, and kick users if they need kicking. HQ guys can also ban users forever or for as long as they see fit.
Sorry BB I had computer issue as well and funny this is the first time it happened. When you respawn and hit the escape key it takes you too that screen, well that is what i saw on my screen. I hit the esc key to try and get it to go away ad not happening. I could tell I was flying and make the plane move but I could not see what was in front of me so I hit disconnect to save from ruining someone elses game.
More to the point on the ground it was working perfect for me and in DW room as well. I cant speak for during the mission sorry.
Wood thanks for the survival I was so pissed I realy didnt explain things to everyone before i left.
S~
Seems the binding feature to speak across channels is a bit buggy. So you
So for you flight leader type guys, I'd like to offer an alternative which is to run a second instance of vent and set a different Push to talk ( PTT) button there, and all flight leads can join an open channel on that second instance, and communicate there when needed.
TO run a second Vent is pretty easy. Here's how:
Create a desktop shortcut to ventrillo. ( find Ventrilo.exe, right click, send to desktop)
If you've already got a Ventrilo shortcut on your desktop, you don't need a second one.
Right click the vent shortcut and click Properties.
Click on the Shortcut Tab.
You will see the path to your Ventrilo,exe in the Target line.
Add a space and -m after the quotation mark. Mine looks like this: "C:\Program Files\Ventrilo\Ventrilo.exe" -m
Click Apply
Click OK
Launch Ventrilo from the short cut.
Launch Ventrilo again from the short cut.
There's a good chance it will look like nothing happened, but if you drag the Ventrilo window you should see you now have two Ventrilo windows. Pick one and change the PTT key. Flight leaders just need to pick an open channel and jump in.
You might want to use a different username in the second vent ( no password needed). It's less confusing. Maybe just add a 2 to your username. Your new username won't have AH rights, but you shouldn't need them to join and go to a channel with just flight leads there. You should be able to go to an open/empty channel, and using your second PTT key be able to talk to each other there when needed.
You'll also see your other self on the other channel with your flight. Use your original PTT button to talk on that channel.
There's a good number of guys that have used the two vent method without any bugs that I know of so far.