Badass1982

Yeah but not all of the f10 menu items are actually being imported as *action do something*

Ignore my previous post guys I found a workaround for the F10 menu I had to create manual commands for all the options but I find it works so much better now, Problem solved!

So using the Import f10 option i have gotten VCP to import all the commands to my profile, my question is how would i say the full sentence if these are the commands i wanted to use in order so as to make VCP understand me, this is how they are listed once I export them to a html file then import them to Excel: *Action SEAD Commence Attack* *Action Sector Gudauta* thanks M

So I sort of made progress @hollywood_315 and i got the game to import the f10 menu commands (from other) to Vaicom Pro, but it's having a hard time understanding the phrases, for example one phrase that works is, action request f15 support. But if I want to call in a said strike for a particular region on the map the following which is listed as the phrase, in the keyword editor doesn't work..... : Action, SEAD attack commence. Finally, when importing f10 menu commands is there a way to not have to say "action" every time?? Or can the entire phrase be changed

Thanks just found it. I HOPE this works the way I want it to. Importing F10 Menus Some missions make use of the ‘Other’(F10) menu for special commands. If in Preferences the option ‘Import F10 Menus’ is enabled the F10 menu items will be added to the keyword database. The imported keywords cannot be used immediately, the updated keywords list must first be added to the VA profile. See Keywords Editor section in the Configuration Window chapter.

So to answer hollywoods question, I'm not sure exactly how the import f10 menu works (other than what he mentioned above) but I have never been able to get the menu to work by saying anything other than (in this order) 1 Options, 2 Whatever option you want e.g. flight but say the f number or "take" then the number However if i dont want to have to say all those commands to get to say the 5th or 6th nested option in the comm menu I tried to create my own voice attack command to do all the commands for me when i say one phrase: So if i have a custom command that reads as the following: when i say Voice command "Fighter Support Sorii" 1: press "" (Which is the open comm menu keybind) 2: press"f10" (which is "F10.other" in the comm menu) 3. press "F1" (which is "F1.Request Support in the comm menu) 4. press "F1" (which is "F1.Request Fighter Support in the comm menu) 5. press "F1" (which is "F1.Sori" in the comm menu) There are others which i intend to create to take care of the myriad other commands but i hope you can now see what I am intending to do, I want to be able to say 1 command phrase to choose all those menu options in one go , it has to be possible but for some reason none of the three programs will accept the initial command despite what keybinding i give it. I am running the Missions Operation Snowfox and in this case Operation Clear Field. Thanks in advance. M

In reply to Hollywood, mind you it works fine using the way u implemented it in saying things like options, take f12 for example but if we want to add specific commands to say do a bunch of comm menu commands at consecutively for some reason va/Vaicom Pro won't recognize our menu command example as follows One command that is set up such as: When I say "Fighter Support" <<< my custom comm menu command. Press "/" to get Into the comm menu <<<< this is the command that doesn't work no matter what you map it too. Press "F1" to select whatever option Press "F2" to select whatever option. Not sure if it's a DCS issue or VA or VAICOM but I can't figure it out , thanks for all your hard work Hollywood, and the other guys in here helping out.

Nope they are completely unbound until I bind them of course.

How can it be that only one command (despite trying different keys) won't work.

Tried all that still doesn't work for me, I can either leave it listening all the time by making sure the red Cross is not on the headphone icon. Or use push to talk and have it not work .

Thanks I figured it out with some friendly help from the guys and DCS Liveries Discord. It was indeed my description.Lua

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."

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.

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?)

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

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.

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.

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?

Quick question (i know u can do it in the client) but is there a way for me in my server to disable the firing sounds by default?? Thanks Martin

Forgive the ignorance I have looked through the manual but cannot seem to find the answer to the following issue I'm having. In the F18C I'm aware it has two radios, is there a way without using easy comms to operate both the radios using just one push to talk button on my hotas? I'm struggling to get it to activate and use radio 2 radio one seems to work great though with one p2t button

Eager to try this mission out tonight on my private servers, but just for clarification, is it just the server that needs to do the following or do all the clients need to do it too?? Thanks "Ok so here is the deal. Persistence is very possible, but it would require people to de-sanitize 'lfs' and 'io' which is part of MissionScripting.lua in their installations. This allows for the exporting of data from the mission into a file that can then be loaded at mission start. I imagine some people may already do this to get things like TacView to load? Anyway ... it is very possible to add it in. I figure if people are comfortable with this then I can implement it for a future version. The downside to this is that if you want to start the mission again 'from scratch' you would need to delete the exported data before starting up the mission. How do people feel about this? Feedback is definitely required for this one."

Hi all, I have an issue which I'm sure is super simple to resolve but I have no idea what I am doing when it comes to the bort numbers ..... So far I have managed to get the numbers I want to come up on the tail and the front of the nose as shown in yellow in the picture included. I'm having trouble the stoppinf the other places from showing up. What would I need to do to the description.lua to prevent those numbers from coming up on the skin (the grey ones). Thanks in advance you guys are awesome.

Oh I didn't UNDER-CLOCK my card. I just made the overclock slightly less. I had it set to an offset of +150 on the core and +500 on the VRAM on an RTX 2080ti. I have been testing most of today and have found that by lowering JUST the core to +140 core instead of +150 offset my flickering has completely gone, It should be noted that for the sake of science I did try and was unsuccessful in running a 3dmark benchmark using my prior settings , however lowering my offset by +10 seems to have done the trick My card is the factory overclocked EVGA FTW3 RTX2080ti and I have it under custom liquid cooling, It really is funny as this card doesn't even hit 45 degrees Celsius under heavy load but its pretty well publicized now that the RTX series of cards are renowned for not being very good overclock-ers (not that they need it).

Well once and for all I have managed to stop the flickering (in my case at least) it was directly related to the overclock that I had set on my 2080ti. Zero idea why every other game I run on it overclocked runs perfectly, but by creating 2 profiles one at stock clocks for DCS and another overclocked for every other game I have managed to stop the black squares entirely. Temperatures were not an issue with my card not getting higher than 40C under a full load. No idea why this is still happening to others whom dont have overclocked cards though.