hornblower793

Have you tried using the ATC callsign (e.g. Batumi....page) Away from PC - sent using Tapatalk

No problem - we have all been there:thumbup:

Is it just VA / Vaicom that crashes or is it all of DCS? are there any specific activities you have been doing just before the crash, or is it after about the same amount of flying each time

Thinking about it, my knowledge might be not up to date looking at the Razbam forums (I don't use Tarawa at the moment) - what happens if you try using the options command to select the option? The thread in the Razbam forum implies it might be that the Harrier is not supported by the Supercarrier module and that this might be why SC ATC does not work. Another thread from August says that all non-SC landing ships have been affected with messed up comms. Realistic comms were pushed as being for SC modules only so I am sure the issue is in DCS and not with Vaicom. Away from PC - sent using Tapatalk

You need to say JTAC....page , Air Traffic Contol.....page etc. Note that AOCS is Crystal Palace and Ref is Chief Away from PC - sent using Tapatalk

The answer is in the log - realistic ATC is only available on the ships that are part of the Supercarrier module. Tarrawa is not one of those and therefore runs on the classic ATC model. this is a game limitation and not a Vaicom one

What symptoms are you getting? I am curious as I have it working with KneeboardBuilder and would like to see the differences

I definitely think this is a Microsoft speech recognition issue. Have you set it to recognise non-native accents? Away from PC - sent using Tapatalk

I wish I could help, but I am just a user like you and haven't had any chance to get on my rig recently. I also typically fly using a mouse to change the selector before I transmit so it is not functionality I really use. If you could post images of all your Vaicom config screens where options can be set then I can have a look and see how it compares to my set-up

I think the only option is to do more voice training - I am not 100% sure, but dictation uses the inbuilt Microsoft speech recognition engine and will not be interpreted by Vaicom Away from PC - sent using Tapatalk

Which editor list are you talking about - the one in VA or the one on the Vaicom editor tab?

Sorry, I should have explained better. There is a Vaicom alternate wheel available (see page 43 of the manual), but there are technical reasons why the Heatblur one cannot be displayed. I don't have the deep knowledge to know what these are what command did you use and on which radio? In some of the instant action missions one radio will be tuned to the carrier (and possibly all support ships) and the other to a ground base. When checking in, don't use inbound - use Marking Moms or Inbound for carrier

The Jester wheel cannot operate if Vaicom AIRIO is installed. Did you follow the installation instructions in the Vaicom manual (summarised as install the AIRIO dll in the Vaicompro extensions folder, open the Vaicom config, go to the editor page, click on the Finish button and follow the instructions given, enable AIRIO in the Vaicom config (on the EX page))? if you have and it is not working please could you turn on debug in the Vaicom config and post a screenshot of the VA log file when you try to use a command

Which versions of VA and Vaicom are you running, and which version of DCS. The Syria airbases are in the latest version of the Vaicom plugin. If you have this, have you completed the Finish steps after the update (open Vaicom config, go to the editor tab, click on the Finish button and follow the instructions given) Away from PC - sent using Tapatalk

What is your exact issue - is it that your commands are added to the Notes page when you are on it and you issue the command? If so, have you turned dictation mode on by accident? Away from PC - sent using Tapatalk

This should just allow you to browse the tabs without saying page in the command but will be interesting to see whether this is a side effect Away from PC - sent using Tapatalk

Do it the way you have - it then works for every airframe (unless they have decided to have different keybinds)

I also use one and have assigned keys using the Razer software - works really well. Some are assigned to keys, other keys to joystick buttons and the 4 way controller is set up to adjust my cockpit seat position

What issues are you having - the manual covers use - some of the tabs need to use special commands to access so the Ref page is brought up by saying Chief...Page, ATO is Show Log, AOCS is Crystal Palace. It will then auto populate with the relevant information during the mission, for instance JTAC nineline information will appear automatically on the JTAC page. Also, I have kneeboardbuilder pages in mine and it works fine

Vaicom now does this really nicely Away from PC - sent using Tapatalk

I think the order of the radios might have flipped in the DCS model - have reached out to @Hollywood_315 to see if he can confirm Away from PC - sent using Tapatalk

I would be interested in trying this Away from PC - sent using Tapatalk

It was our pleasure. I will carry on looking to see if I can work out how to stop the squelch on release Away from PC - sent using Tapatalk

@MAXsenna gives good advice. I have just tried setting a modifier on my TX1 to move the view down and it only changes view if I press the modifier before the TX key (VAICOM still fires because the TX key is pressed). If your problem is that you do not want Vaicom to work when you hold the modifier down then you will need to do either of the following from the Voiceattack Edit a Command screen for each TX: A. Click on the ... button to the right of When I press button and check Shortcut is invoked when no other buttons are down, or B. Modify the When this command executes, do the following sequence: code to exit the command before invoking Vaicom Option A is easier but B allows you to do more complex things (such as have 2 modifiers held down). Both work on my setup but you still get a squelch sound when you release the coolie For option B the following is code I have just put in to exit the command if the CTRL key is pressed (the last line is the code that was already present to make Vaicom work) Begin Device State Check : Keyboard Key 'Ctrl' Is Pressed Exit Command End Condition Execute external plugin, 'VAICOM PRO 2.5' To edit the command for option 2 do the following: Double-click on the Transmit TX1 press command (as you did to set the HOTAS command). 1. Click on the Other > button, select Advanced > Begin a Conditional (If Statement) Block > Single Condition. In the box that appears select the Device State tab and then select the Device you want (e.g. Keyboard Key) and then the modifier key you are using in the list below. Click on OK 2. If not already highlighted, click on the line starting Begin Device State to highlight it and then click on the Other > button. Select Advanced > Exit Command to add this line 3. Highlight the top line (starting Execute external plugin) and press the Down button to move this to the bottom (line below End Condition) 4. Click on OK 5. repeat steps 1 to 4 for each Transmit TX press command As said above, A is definitely the simpler solution but B can be very powerful if you understand some basic logic principles. Hope the above helps - either post again here or PM me if you need further help or this doesn't solve your problem:thumbup:

I have just tried an instant mission in the F-14 and can confirm that I am seeing the same behaviour with the ICS switch.