hornblower793

Flappie - slight error in your instructions. Step 2 should be "C:\Users\your_username" I have done this (FolderChange log attached) and can confirm I also have the second bin file modified at the same time as the crash file is created. The Last Mission track file also has the same modified time on it FolderChanges - 2nd Mission Crash.htm

I have already tried disabling Tacview and have still experienced crashes. When this happens I don't get the option to click FLY, it stops at mission load done. Should have an opportunity to try running FolderChanges later to help broaden the information base. Sent from my SM-T835 using Tapatalk

It is on the Help tab Sent from my SM-T835 using Tapatalk

If you start Vaicom, open the Vaicom config and then press the Diag button on the Help tab, what paths does it say it is using for saved games? Sent from my SM-T835 using Tapatalk

I have just tried both the 14B and 14A cold and dark on the SC and can confirm that it worked for me

Are you in a cold and dark Tomcat - if so have you tried using the interphone (TX5) to make the calls?

I know, but the chatter not available issue seems to be triggered by the Vaicom profile not being the top level at the moment - it is something changed in 2.7 so I am sure will be resolved Sent from my SM-T835 using Tapatalk

You are seeing the chatter not available error because Vaicom is not the top level profile - I got this the other day trying to help someone else. Elsewhere on the forum,@Hollywood_315 has stated that 2.7 has changed how some of the communications work and that there will be an update to the plugin. However, he also stated that this will not happen until 2.7 is released onto stable because ED are still changing things. I think all people can do is therefore wait patiently. I am guessing they will not make a stable build until they have resolved the constant / intermittent crash that some people (including me) are experiencing. Sent from my SM-T835 using Tapatalk

What plane(s) are you trying in. Are you saying you can switch between the tabs on the interactive Kneeboard page or to the other 'normal' pages of the kneeboard if you have the TX button pressed. How have you set up your TX buttons since you are saying that the Kneeboard closes if you don't use the TX - do you run other VoiceAttack profiles as well as Vaicom?

Beta version for me - can always swap back to stable if there are major issues

@Screamer63Karpyion has / had a different problem - he was trying to get the Comms menu to show using a voice command while Vaicom was running - it wasn't to do with the mic shutting off. Is your problem that the mic stops listening while you have the PTT button pushed?

I haven't set up my attached profile to run without pressing a TX, but when I do press a TX all I have to do is press the TX and then say the command twice to show the menu. It then works on / off as expected each time I say the command until I release the TX. I then changed this to use a conditional loop to run the command twice if necessary. Because you are running open mic for these commands I think all you probably need to do is have a condition loop that checks whether you have initialised the chat (using a variable that you set once you have started chat). I didn't change my setup round so still need to press a TX button for this to work. All I did was reset myToken to false on release of the TX button and got it working quite happily

I have just had a thought - do you have Disable Menus ticked on the Preferences tab of Vaicom (I forgot I always fly with this on and that is why my keybind was not appearing to work). If you have this checked then Vaicom is working as intended.

The \ (I have to use # as I have a UK keyboard)

OK - I have managed to replicate the issue and I think the answer is you will have to either not use Vaicom or wait for it to be updated. In 2.7 ED changed how some of the comms work and are still changing them - this is obviously one of those cases. With Vaicom running the keybind does not work so that is why your voice command will not work Options does work in the meantime though

I still need the log to see what is happeneing - run with Vaicom debug on

But why are you not using the built in Vaicom command to show the radio menu? Vaicom doesn't do the speech recognition that is the Microsoft speech engine (unless you are using VSPX). VA will then see if the command is in the known Vaicom list of commands and, if so, execute the plugin. If it doesn't find it there then it will check the first linked profile etc. I have linked profiles that work quite happily. Your issue might be that the words you are using include words that are Vaicom commands and it might therefore be trying to execute a Vaicom command. Please could you try it again and then post the Vaicom log file (found in <voiceattack install directory>\apps\VAICOMPRO\logs) - this will help identify what is happening

Answered on other post Sent from my SM-T835 using Tapatalk

This is not a Vaicom question - you are trying to use a VoiceAttack command. If you have Vaicom the way to bring up the menu is to pushh and hold the PTT and then say Options. Sent from my SM-T835 using Tapatalk

@Hollywood_315 hasn't visited the forum since March 27th so I assume real life has intervened. Sent from my SM-T835 using Tapatalk

Yes - for most of them you need to run with Easy Comms on at the moment, otherwise they will communicate on the ground but not in the air

@MAXsennais correct - there is some technical reason why the Heatblur Jester wheel cannot run at the same time as Vaicom.

As a workaround, does it happen if you exit to the menu and then go in again as opposed to just hit re-fly?

Glad it is working and it will definitely add to the fun