Greyman

are you copying the updated commands list into the profile, as per the Import F10 section of the manual, on page 19. If memory serves me right, that involves pressing the "FINISH" button, which copies the commands list to the clipboard, and then pasting the results back into the VP profile. "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." sorry if you've done this, but i thought it worth asking.

https://www.digitalcombatsimulator.com/en/files/3305957/

If you can, maybe try changing the name of the mission file in question, just in case VAICOM Pro keeps a list of missions that it has imported and it is that which is stopping it being reimported. If it does maintain a list, it might use an identifier other than the file name, but it's worth a try.

Thanks @Hollywood_315 and I hope you had a good break The F14 module and the AIRIO extension will be my next purchase, so that is good to know. I take it that the improved ATC comms extension will be useable for all carrier-based modules, the F18 and F14 for example?

Maybe try turning off power management on the associated USB device(s), via Device Manager.

For me at least, the A10c cockpit, in VR, has always been slightly off, despite some claiming that it is a realistic representation. When I originally bought the module, the default pilot position in VR was really far forward, almost on top of the stick and leaving loads of space behind the pilot's head to the headrest. This allowed the whole HUD to be seen, but did feel a little odd and made reaching for controls at the back of the side panels a little less than ergonomic. Then ED moved the default position back in the seat, so that the pilot's head is closer to the headrest, which feels better, but creates the issue where you can't see the whole of the HUD. It is possible that this is realistic, but why would the aircraft's designers create such an ergonomically unfriendly environment. I may be being overly optimistic, but I am hoping that this will be addressed as part of ED's overhaul of the A10c cockpit. I think their problem will be, if they do want to amend it, that it might not just be a case of shrinking the HUD graphics to fit on the HUD. as the HUD graphics need to line up with the outside world, for bracketing targets for example, there may be more fundamental changes required. In the meantime, it might just be best to either lean in and out, as required and maybe make creative use of the recentre VR view function.

https://forums.eagle.ru/showthread.php?t=247044 might be of some assistance

Hi @Hollywood_315 Will the F10 Import Menu option automatically add the new ATC commands, which will come as part of ED's carrier module or will your profile need to be changed? From Wags' recent video, https://forums.eagle.ru/showpost.php?p=3951507&postcount=162, it looks like there will be a new set of improved ATC commands for peeps that buy the module and that everyone else will be able to carry on using the current comms.

Try button 29 for right engine off and button 30 for left engine off. These two switches are triggered when you lift the two throttle levers back over the idle detent.

Is anyone running the VoiceAttack profile, kindly provided by @Chic in post #50, alongside VAICOM Pro and, if so, how did you combine the two profiles? Edit: Ah, never mind, i've just found post #65. Thanks @Crowebar, for answering my question before i asked it. :)

You shouldn't need easycomms on to be able to access the f10 menu though. I'm using options with the Hornet and as long as i use one of the two active PTT buttons, the comms menu does appear.

I'm fairly sure that which PTT buttons are active will depend upon the module currently being played and that the AUTO button (TX4) might not work, for the options command, with easycomms set to off. Maybe just try another PTT button that you know is active in the aircraft you are currently sitting in. Edit: I've just got into my PC, which is probably what i should have done before posting, and it would appear that if easycomms is off, VP throws out a "PTT key not in use: check configuration" warning, when you press TX4 or any other inactivve PTT key. With easycomms on, it does display an, albeit limited, comms menu. Therefore, my above suggestion is probably not likely to help. Sorry

VAICOM PRO for DCS World.vap should be in the folder at ....\VoiceAttack\Apps\VAICOMPRO\Profiles\ If it's not, then maybe do a search for that file across you hard disk(s). It should be there.

it's good to hear that you have got it working

From the following excerpt from the VP user manual, linked on the first post of this thread, it sounds like you have definitely done the first two, but i'd check whether you have also done the rest, the "FINISH" steps in bullet 4 in particular. Setting up • The AIRIO dialog extension is a separate download from the http://www.vaicompro.com website with a separate license code. Use the About tab of the Configuration Window to activate. • After your license activation, confirm on the EX tab that the Enable option is selected. • Enable Extended Command Set on Preferences page. Restart both VA and DCS. • After VA restart, new keywords will have been added to your alias database. Follow the regular FINISH steps (see page 30) to update your VA profile with the new keywords. • Restart VA again, and then start DCS. • In DCS options under Special, confirm the Radio Menu setting for the F-14 is Default.

I am having the same issue, having used Bankler's excellent Case 1 landing mission for the last few days. The issue leads to a truncated assessment summary, but only while i have VoiceAttack and Vaicom Pro active. I had previously selected disable menus option, which i had to do to prevent the comms menu from appearing constantly, but mission messages still appear in the bottom right of the screen, as per @trgriffin's screen shot, instead of the top right, where the messages appear, in full, when VA/VP is not active. It's not a real biggy for this mission in particular, as comms aren't essential, but it could be a pain for other scenarios.

I've just returned to DCS, after a few months off, and i am also seeing the ODCSParticleSystem.... error in my log. There is a slight difference however, in that my client CTD, after a very short period where the performance drops dramatically. I can reproduce the error, despite having repaired DCS. The CTD occurs just as my first AGM65D maverick hits the bridge in the easy spring A10C instant mission. I play in VR btw, in an Oculus Rift. Edit: My issue appears to have gone away. I'm not sure which was the cure, but i both removed all mods as well as installing the very latest Nvidia drivers for my GPU. My money, if i had any left, would be on the latter. :)

Any other noise, especially verbal, is likely to interfere with Voice Attack, either by causing it to hear commands that you haven't spoken or not not hear those that you have. Going through windows speech recognition training as many times as possible will also improve VA's ability to understand what you are saying.

Just make sure that you clear the field before pasting in the new contents. Ctrl&a followed by delete should do the job. I'll be well happy when the VA devs fix that "invisibility bug"

I don't use it myself, but you might also want to check your settings in OH, as they contain an option to mirror the rift's audio to the default Windows output device, which could make it look like the VP feature isn't working.

It sounds like you are going through the right steps to add an alias, but the check for duplicate words that the alias system uses, appears to view plurals as being the same as the singular variant, hence the "1" postfix. I tend to use "2, engage triple A", which still results in the same wingman response as engage air defense. Alternatively, you could use the correct English spelling and try adding "air defences" as the alias. ;)

Voice Attack does display the commands, combined or otherwise, in the profile, but the box that was highlighted in red did appear to be empty and that is how the VA bug usually manifests itself. Either way, as long as the commands exist within the profile, it should work. Edit: unless there is another issue that is.

There is currently a now long standing bug in Voice Attack (not Vaicom Pro) that makes it look like that field is empty, when it actually contains what it should. If you follow the ctrl&a, delete and paste steps, you should therefore be good.

The Vaicom Pro thread might not be a bad place to start as everyone there will at least have VoiceAttack and Vaicom Pro and I'd guess it is likely that someone will already be doing what you are trying to do https://forums.eagle.ru/showthread.php?t=198297

IIRC VAC takes its input from the Windows default MIC, so maybe make sure that you have the Rift's MIC set as default.