hornblower793

Glad you have it sorted

OK - I need to go out now, but will be back in about 2 hours if no-one else has managed to sort you out before then

Is there anything in the command phrase dropdown list?

Yep - your keywords database should show a lot more commands. Try the Reload button and see what happens

I think it is more to do with the setup - I am just trying to work out what it could be looking at my end. What settings do you have on the Voiceattack recognition screen

OK - the issue is not comms with DCS then, it is something in the VA / Vaicom setup screens

Does it do the same if DCS is not running?

Does Inbound also say awaiting additional input? It might also be worth trying to set Easy Comms On to see what happens Sent from my SM-T835 using Tapatalk

No - it is a command for all planes - it is not in your keywords list in the Vaicom Editor. Radio Tune still exists If you click on the pencil icon on the main VA screen it should appear under the Radio Control category on the Edit a Profile screen

There are quite a few of us with the d3d11.dll access violation. Sent from my SM-T835 using Tapatalk

OK - when you start VA / Vaicom has it recreated an Export.lua in the saved games on C?

Could you also post the log file - either dcs.log or just dcs

I tried this and got the crash at second mission load (log file and dxdiag attached). Having logged out and in again I then looked at my AV (Bitdefender) and realised I hadn't updated the exceptions list when I moved DCS, so it was still pointing at the old location. I changed this, have gone back into DCS and managed to start this training mission 4 times in a row without issue. I have also attached the log file from the run that worked happily in case there are any clues DxDiag.txt dcs-F14 crash.log dcs.log

OK - what date is the export.lua in the saved games file on C? It might be worth renaming the c drive saved games folder for DCS openbeta to something else assuming the F: drive is the one you want to use

OK - I cannot see anything strange in the config screens and I have just tried my Viggen and it comes up fine so at least there doesn't seem to be a fundamental issue with the airframe integration as a result of 2.7. Looking at your log from earlier, can I just confirm that your saved games folder is on your F: drive - we have seen issues before where there is more than one saved games folder. If you do a search for export.lua does it return more than one version?

Did this start with the update to 2.7OB?

We will get you running - it is something in the configuration. To help me try and diagnose more: 1. What plane(s) are you trying in 2. Are you running easy comms on or off 3. Please could you post screenshots of your Vaicom config screens 4. Do you run the NS430 addon as this is known to be incompatible 5. Do you run any other addons (SRS, Tacview etc.)

Sorry - my reply was meant for @j9murphy - this thread is way too long and it is hard to try and keep track of everything This was the solution another user found to the same issue so might be worth trying I discovered that repairing DCS with the file removal option does not remove the files in DCS World\Scripts\Aircrafts\_Common\Cockpit\VAICOMPRO. So I manually removed that folder and restarted VA to recreate it and that seems to have fixed the kneeboard.

This was the solution another user found to the same issue so might be worth trying I discovered that repairing DCS with the file removal option does not remove the files in DCS World\Scripts\Aircrafts\_Common\Cockpit\VAICOMPRO. So I manually removed that folder and restarted VA to recreate it and that seems to have fixed the kneeboard.

Which plane(s) are you trying and do the uncommanded entries show in the log file? What uncommanded entries are you seeing? Sent from my SM-T835 using Tapatalk Are you running VA as an administrator? Sent from my SM-T835 using Tapatalk

@XPACT Your and Flappie's efforts are much appreciated - while I have spent quite some time looking at crash logs on here I haven't had the time to deep dive any of it. I saw from another thread you now think it may be dynamic pagefile sizing (which I have on and also experience some crashes). The theory sounds good because the logs show lots of different dlls faulting with Access Violations. Either tonight or tomorrow I will try fixing my pagefile size and see what happens Sent from my SM-T835 using Tapatalk

I think the problem is that the F10 commands include a comma and therefore the recognised phrase is not the same as the imported phrase. Like the others here I use options to bring up the menu and the use Take x. Importing F10 sounds like a good idea but I rapidly ended up with a large database of words, and still had to look at the menu to work out which F10 phrase was needed Sent from my SM-T835 using Tapatalk I think this is because ten is used as part of many commands and Take 10 makes it clear you are wanting the radio menu option. This saves the software having to do additional work to try and determine the context. Sent from my SM-T835 using Tapatalk

It does - have you done the basic Microsoft speech training in Windows? I did this before I even started with Vaicom and it helped Sent from my SM-T835 using Tapatalk

I understand, but I am pretty sure it is not Vaicom since the log seems to be showing that you are transmitting on the correct channel and it is therefore another programme that is doing it. I also think if it was a core Vaicom issue we would have had a lot more issues showing here or on the Discord channel. Have you tried changing the order of the entries in the Export.lua to see if it does anything? The other option (having made a copy of the export.lua) is to leave only the Vaicom line in there and then have a quick flight to see if it works on its own.

I think it relates to Oculus updates - the developers are a bit naughty and just change your default input and output devices without asking - has caught me several times (including yesterday)