Greyman

I wonder if the VA profile that features in the latest F14 cold and dark startup video is already part of the VAICOM PRO profile or whether it will be linkable to it???

It is worth noting though, that VAICOM refuses to work if you don't spell its name correctly. :) It does use one profile for all DCS planes and from recent videos, there is definitely some VAICOM amendments incoming for the F14.

I'm guessing/hoping that the assisted startup profile for VA will be able to be linked to VAICOM PRO and between them they will hopefully also deal with the general voice interface commands between the pilot and RIO, thus removing the need for the radial interface.

Is your VoiceAttack still being launched in Admin mode? There have been some reports of shortcuts mysteriously having their properties changed. Maybe worth checking.

Hi @Kariyann71 - does your "Vaicom panel" correctly identify the aircraft/module you are flying? if not, there are quite a few posts on this thread that relate to what appears to be the same issue. #872 might be a good place to start. Also, if its the F18 that you are flying, post #793 might be of interest.

My experience was a positive one also, as my headset was about a month past its 2-year warranty (EU) when the right side audio failed and Oculus replaced the headset without any argument. Probably like others above, I found that contacting Oculus directly, with a polite enquiry, to be far more effective than moaning aggressively on their forum, an approach that seemed to only succeed in getting the customers' blood pressure up.

I'm fairly sure that ASW is causing the issue, as it apparently doesn't deal well with displaying the line-type images that will appear on a HUD. It should be easy enough to test though. Just disable ASW and check out the results.

Just to check that it isn't the quality or position of your mic that is causing the issue, maybe try speech recognition in Italian, to see if it yields better results. I know that Vaicom only works with English, but this might help to understand where the problem is

The "invisible text" is a long-time known issue with VoiceAttack and once it has been fixed, hopefully in the next release, the instructions will be fine.

https://forums.eagle.ru/showthread.php?t=218861 might reduce that difference, especially in VR

or just leave the canopy open when you speak and all that complicated stuff isn't needed, as the ground crew will just hear you in the old fashioned way. seriously they will ;)

Maybe checkout post #1102 and onwards, in this thread, for a potential solution(s)

Maybe posts #1133 and #1140 of this thread might be of some use

This is a known issue with VoiceAttack, that will hopefully be fixed soon, but even though the field might appear to be empty, the contents are still there. Just make sure that you do the Ctrl-a and Del to clear the field, before pasting the new contents.

Are you running VoiceAttack as Administrator?

Or just get an Oculus Rift and "kill two birds with one stone". :)

maybe the AI pilot of the Mig29 had deliberately targeted the aim120 and was too close to the resulting explosion? Does the R73 explode before hitting its target or does to explode on impact? If it's the former, then the resulting "ball" of high speed fragments wouldn't discriminate between targets and might explain why the kill was attributed to the R73. Excellent modelling either way

Which request is ATC not responding to? If it is "request taxi to runway", maybe try "request takeoff" instead. The former does not always work for me, probably due to some sequencing issue that either i or DCS is suffering, but the latter appears to result in the same response, ie ATC telling you to taxi to the chosen runway. Also, it might be worth making sure that you "request startup" before either of the above requests. To confirm that this is not a Vaicom Pro issue, maybe use the Dcs comms menus to check if the same requests result in the same behaviour that you are experiencing with VP

Or make sure the canopy is open before you speak, so that the ground crew can hear you without the radio

I'm hoping that the menu is compatible with Voice Attack and/or Vaicom Pro, so that we can just tell the RIO what we want them to do, without having to press any keys. In VR, that would be especially useful.

yup, sorry, i should have checked first. i have just installed the latest DCS update and everything appears to be working as normal.

Now you've done it. You've just gone and spoiled Heatblur's big Oct 7th announcement. ;)

maybe follow the link in Badget1815's post, two posts above your first post. (post #1062) it looks like you might need to install the files manually for now, due to a change in the way that DCS organises its files. it'll be worth a try at least.

are you running voice attack in admin mode?

I've just given it a try and didn't appear to have any issues. If you want to do it "by the numbers", approaching with the left engine's RPM set to to 81 and the right to 82 and then adjusting the right engine down to 81 and back up again to maintain position, that should take the throttle variable out of the equation. Have you checked that one of your controllers isn't generating some unwanted "noise"? Maybe just sit on the tarmac and watch the surfaces for any movement that you haven't asked for. If it looks like that might be the case, then a re-calibration or just setting a bigger deadzone might help. by the way, with the default settings for the mission, the tanker appears to fly at around 13,300ft and not exactly 13,000 Edit: it looks like this is not the exact science that i had hoped, as just trying it again, on the same mission, needed the throttles set to slightly lower values to avoid flying "through" the tanker. I still find it useful to use those numbers, but it appears that they will need to be adjusted for the prevailing conditions.