jameslockridge Posted October 15, 2019 Posted October 15, 2019 Thanks for the help, it was strange I finally rebooted and it was gone next time I played
jameslockridge Posted October 15, 2019 Posted October 15, 2019 Does anyone have trouble with the F 16 getting the tanker to answer?
Bazmack Posted October 15, 2019 Posted October 15, 2019 Vaicom Pro Mic listening paused everytime I restart a mission in DCS The Vaicom Pro Mic listening paused everytime I restart a mission in DCS even if I am not loading the Vaicom profile. this ie very annoying as every time I gave to get out of DCS and click the mic icon to restart listening. Is there a way to stop this behavior? I do use PTT in the Vaicom profile but not when using VA at other times. (this behaviour is definitely from Vaicom as when I disable plugins it goes away).
Badass1982 Posted October 15, 2019 Posted October 15, 2019 I am having an annoying issue and I wonder if any of you smart people can help me. So I have set up a custom VA profile with vaicom pro and some custom commands that control certain custom f10 menu mission functions , however when I try to open the f10 menu using the warthog button that is mapped to my ONLY p2t button it doesnt open the f10 menu. Weirdly if I click the little listening Icon on the VA wndow and say my command "fighter support Sochi" it goes through my entire command after opening the correct path in the f10 menu. Is there a specific p2t bind I should be setting in the vaicom pro or base voice attack settings?
MAXsenna Posted October 15, 2019 Posted October 15, 2019 The Vaicom Pro Mic listening paused everytime I restart a mission in DCS even if I am not loading the Vaicom profile. this ie very annoying as every time I gave to get out of DCS and click the mic icon to restart listening. Is there a way to stop this behavior? I do use PTT in the Vaicom profile but not when using VA at other times. (this behaviour is definitely from Vaicom as when I disable plugins it goes away). I don't quite follow, as VAICOM doesn't have a listening mic. Only what you configure for PTT. What do you use for PTT? Can you take a screenshot of the VoiceAttack window to show the log? And have you checked the VAICOM log? Have you configured push to talk in VoiceAttack?
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Does anyone have trouble with the F 16 getting the tanker to answer? Have you tried the "old" way? And do you get answer then?
MAXsenna Posted October 15, 2019 Posted October 15, 2019 I am having an annoying issue and I wonder if any of you smart people can help me. So I have set up a custom VA profile with vaicom pro and some custom commands that control certain custom f10 menu mission functions , however when I try to open the f10 menu using the warthog button that is mapped to my ONLY p2t button it doesnt open the f10 menu. Weirdly if I click the little listening Icon on the VA wndow and say my command "fighter support Sochi" it goes through my entire command after opening the correct path in the f10 menu. Is there a specific p2t bind I should be setting in the vaicom pro or base voice attack settings? Does it work outside VAICOM in a standalone profile? Out of curiosity, what commands are those? :)
Greyman Posted October 15, 2019 Posted October 15, 2019 (edited) To display the Comms menu, you will need to press the PTT button that is associated with the radio, that has the right frequency set, and say "options". The menu will disappear if you let go of the PTT button, so you need to hold it in until you have completed your selections. Edit: I think there might be other commands that open the menu further down the hierarchy, but I don't use those, so you will need to look them up. IIRC, "other" or "other options" opens the F10 options. Edited October 15, 2019 by Greyman
Badass1982 Posted October 15, 2019 Posted October 15, 2019 That's just it though I don't want to go through the process of saying 1 options, 2 take f10 , 3 take f2, 3 take f5 etc. I want to just say Fighter support Sochi and have it press the option that is in my custom f10 menu. It works except for opening the f10 menu at the start. The weird part is without pressing my mapped P2T button and just clicking the VA listen button it works , obviously I can't just have VA listening for commands all the time though.
MAXsenna Posted October 15, 2019 Posted October 15, 2019 That's just it though I don't want to go through the process of saying 1 options, 2 take f10 , 3 take f2, 3 take f5 etc. I want to just say Fighter support Sochi and have it press the option that is in my custom f10 menu. It works except for opening the f10 menu at the start. The weird part is without pressing my mapped P2T button and just clicking the VA listen button it works , obviously I can't just have VA listening for commands all the time though. This should work, but I think it depends on how you have done it. Have you: Added the commands in the VAICOM profile? Made a seperate profile, that VAICOM "imports"/looks into? Tried using a seperate button as only VA uses for PtT, and is not a TX button or used by any other "commands" in DCS? I am actually looking into this myself, as I have pretty much made it work consistently for me now. I will not be using it for any F10 menu items though, but I was until VAICOM started working with the MB-339 and A-4E-C. I will be using it for stuff that's natural and I want off the keyboard, but lacks switches on the HOTAS.
Badass1982 Posted October 15, 2019 Posted October 15, 2019 So its definitely an issue with the way vaicom deals with the P2T buttons and the TX options set. I just tested by creating an entirely new command in a new profile that just had one command : to bring up the f10 menu as a test. I set the listening key in VA to my throttle button i use for P2T in Vaicom pro but without Viacom pro running (as I was running my default profile named test) it worked straight away.
jameslockridge Posted October 15, 2019 Posted October 15, 2019 Have you tried the "old" way? And do you get answer then? Yes if I use the keyboard the tanker responds.
MAXsenna Posted October 15, 2019 Posted October 15, 2019 So its definitely an issue with the way vaicom deals with the P2T buttons and the TX options set. I just tested by creating an entirely new command in a new profile that just had one command : to bring up the f10 menu as a test. I set the listening key in VA to my throttle button i use for P2T in Vaicom pro but without Viacom pro running (as I was running my default profile named test) it worked straight away. But are you sure that's the way to do it. Doesn't seem so to me, because I belive you're right and VAICOM blocks the PTT configured in VA, except that you must use the enabled joysticks for TX of course. But I haven't tried something like that, so who knows.;) As I've said I'm planning to do something myself, so I am really eager for you to make it! I don't know how you have incorporated those commands into the VAICOM profile. But I think I will do it this way. https://www.vaicompro.com/support.html 2nd video 8:20 Also looked in the manual now. Think this the solution, unless you've already tried it. On page 13. TX6: TX6 is also optional. It is currently reserved to be used as a dedicated PTT key for cockpit device control commands. These are not available at time of VAICOM PRO 2.5 plugin release but may come in the form of future expansion pack releases. Also, you can use TX6 as a PTT for your own voice commands if you want to enrich the VoiceAttack profile with some of your own commands which use VA’s standard method of sending virtual keypresses. If you feel no need for this you can disregard TX6 for your setup. Always use TX6 with your own commands if you want to use the plugin’s Exposed Variables
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Why is the UHF radio TX2 in the Viper anyway? Shouldn't it be the other way round? I was thinking the same, I'm having a blast reading the manual today! :-) The VAICOM PRO plugin always tries to map the available aircraft radio device types according to this logic: • TX1: → VHF AM • TX2: → UHF • TX3: → VHF FM • TX4: → AUTO • TX5: → Interphone • TX6: → AUX
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Yes if I use the keyboard the tanker responds. Before I might test this myself. Did you by chance do an "interrogate" for the tanker to make sure you have received the correct radio channel?
Badass1982 Posted October 15, 2019 Posted October 15, 2019 As for the tanker issues u guys are having , try this : say exactly "shell approaching for refueling" with a small pause after the shell. Repeat for Texaco and or Arco, I was having loads of issues with this until I said this exact phrase
Badass1982 Posted October 15, 2019 Posted October 15, 2019 Here's my next question can I map tx 4 to auto AND have tx 6 aux mapped at the same time. If so it might solve my issue but RN i cannot seem to manually choose which tx's to enable (is this even possible?)
MAXsenna Posted October 15, 2019 Posted October 15, 2019 As for the tanker issues u guys are having , try this : say exactly "shell approaching for refueling" with a small pause after the shell. Repeat for Texaco and or Arco, I was having loads of issues with this until I said this exact phrase Would've worked on first try with RedKites mission, except that I pressed TX1. :doh: Constantly confuse those...:music_whistling: And I had to say "Approaching for Refuel", as that's what's in my VAICOM profile.:thumbup:
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Here's my next question can I map tx 4 to auto AND have tx 6 aux mapped at the same time. If so it might solve my issue but RN i cannot seem to manually choose which tx's to enable (is this even possible?) From the manual, page 13. TX4: This node is reserved for the AUTO function. AUTO automatically uses the correct radio for the called recipient. AUTO is only available when Easy Communication is set to ON. With Easy Communication set to OFF, TX 4 has no function and the node is disabled. If you fly only with Easy Communication OFF or you do not intend to use AUTO, then there is no need to map any key/button to TX4. Ahh! You want to have Easy Coms enabled, AND TX6?
Badass1982 Posted October 15, 2019 Posted October 15, 2019 (edited) No I don't have easy comms enabled. I want TX 4 or 1 or any of the tx's as long as its ONLY 1 button to listen for VA commands to control my radios and cockpit stuff and one of the other tx's to control the VA to listen for commands for the f10 menu. Ideally I would be able to do it with one TX button for all , that's what I was trying to do. Edited October 15, 2019 by Badass1982
MAXsenna Posted October 15, 2019 Posted October 15, 2019 No I don't have easy comms enabled. I want TX 4 or 1 or any of the tx's as long as its ONLY 1 button to listen for VA commands to control my radios and cockpit stuff and one of the other tx's to control the VA to listen for commands for the f10 menu. Ideally I would be able to do it with one TX button for all , that's what I was trying to do. Ah, okay. I just misunderstood because of the mention of TX4, and then I got hung up in what was written in the manual. I have a feeling that it can be done. If you set the PTT selector to single. I'll go out for a little while, but now I ( I think) know what you really want, and I'll test myself, just to check when I get back. Anyway, if it doesn't work yet, it's probably easy to implement, because I was thinking about it why it wasn't mentioned how to do it in the manual. Because I was sure somebody would like one switch for all, even own custom commands. If you set it so single, then you can even choose wich TX to use, as far as I can see.
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Ah, okay. I just misunderstood because of the mention of TX4, and then I got hung up in what was written in the manual. I have a feeling that it can be done. If you set the PTT selector to single. I'll go out for a little while, but now I ( I think) know what you really want, and I'll test myself, just to check when I get back. Anyway, if it doesn't work yet, it's probably easy to implement, because I was thinking about it why it wasn't mentioned how to do it in the manual. Because I was sure somebody would like one switch for all, even own custom commands. If you set it so single, then you can even choose wich TX to use, as far as I can see. Well, I got it working. one TX, no PTT. Made a mini profile for the F-5E, and made it available inside the VAICOM PRO profile. Turned the switch to single, started the plane, issued the command, and the breaks where retracted. Should also work for your Coms Menu, just make a profile for it so you don't have to mess up the VAICOM profile, and then it should be globally available in all your modules where applicable. So that's the way to do it, if you only want to assign one button for everything in your setup.
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Ah, okay. I just misunderstood because of the mention of TX4, and then I got hung up in what was written in the manual. I have a feeling that it can be done. If you set the PTT selector to single. I'll go out for a little while, but now I ( I think) know what you really want, and I'll test myself, just to check when I get back. Anyway, if it doesn't work yet, it's probably easy to implement, because I was thinking about it why it wasn't mentioned how to do it in the manual. Because I was sure somebody would like one switch for all, even own custom commands. If you set it so single, then you can even choose wich TX to use, as far as I can see. Well, I got it working. one TX, no PTT. Made a mini profile for the F-5E, and made it available inside the VAICOM PRO profile. Turned the switch to single, started the plane, issued the command, and the breaks where retracted. Should also work for your COMMs Menu, just make a profile for it so you don't have to mess up the VAICOM profile, and then it should be globally available in all your modules where applicable. So that's the way to do it, if you only want to assign one button for everything in your setup. [ATTACH]219346[/ATTACH]
Badass1982 Posted October 15, 2019 Posted October 15, 2019 See that's my problem though , I have made individual commands for the things like flaps up/down, brakes , speedbrake etc. and imported to Vaicom profile. The ONLY one keybond i cannot get to work is the F10 key (whatever it is bound to ) so far i have tried space, \, `, and lctr + ralt + f12. All of them behave as if i have pressed nothing (but only for the f10 menu) if i add commands after it such as press f10 whilst IN the comm menu , it just brings up the map. I will try yours out tonight and see if i get any luck, Thanks. This part of your comment intrigues me, how was/is this done??? "and made it available inside the VAICOM PRO profile."
MAXsenna Posted October 15, 2019 Posted October 15, 2019 Yup! That maybe the point why I asked you how you got the commands in VAICOM. I have made a complete separete profile that is not imported, but VAICOM looks in it. I'll send a shot. Sent from my ANE-LX1 using Tapatalk
Recommended Posts