hornblower793

In use they were fine. Not quite as comfortable in socked feet as the combat pedals but the ridges are needed to give a great level of grip. I have not played around with the pedal angle since I have them set for fixed wing toe brakes Sent from my SM-T835 using Tapatalk

Received both the revised combat pedals and the Huey pedals in the post today. Have only had a chance to try out the rotary wing pedals so far but they worked very well on the test flight (lots of hovering and landing / taking off to push them around a bit). No feel of flex and no sounds coming from them. Really good level of feel and control. For other users - the bolt holes are tight and you may need to apply a bit of force on the hex key to get them to engage with the nuts.

Yes you can - you need to use mklink to create a symbolic link from the _downloads folder in your DCS folder to the location where you want the download to occur. Run command prompt as an administratore and then use the following command mklink /D <DCS install path>\_download <target path> In my case <DCS install path> is E:\games\eagle dynamics\dcs world openbeta and <target path> is f:\dcs download Make sure that you make the target path a folder that will only contain the DCS download files since it will be cleared after update is complete. Also note that it cannot already exist on mklink will tell you that it cannot create if the target already exists Sent from my SM-T835 using Tapatalk

Or, if it is related to delayed responses in some / all modules post in one of the existing threads related to this

I think they are all related - I have issues with the take commands once this has occurred. Like Maxsenna in the post below, pressing the DCS radio keyboard command seems to clear this, although pressing it too many times can totally confuse the system.

I would argue that this is even more dangerous from previous experience with users - couldn't the updater just check that it is not being set to the root of a drive.....

@Hollywood_315 I have reset the database as suggested and still have the same problem in the KA-50 as before (and therefore assume it will be the same in the other problem airframes). I went to the instant action Sukhumi free flight, tuned the radio for Sukhumi and then called inbound without calling select (which is what I do in the airframes with multiple radios). This set the ATC recipient to 0 and showed the pilot inbound message in the top left corner with no text before the first comma. I then used Select...Sukhumi and repeated inbound. This gave me the log entries below, with the pilot inbound message only appearing just before the response from the airfield. You can see from the log timings that it is just over 1 minute between the Done. entry and the response 10:58:48.126 ATC (Sukhumi): 104, Sukhumi, fly heading 139 for 29, QFE 766.93, runway 12, to pattern altitude 10:57:43.239 Listening suspended 10:57:43.214 Joystick : 'Transmit TX1 release' 10:57:42.841 Done. 10:57:42.839 Constructing message... 10:57:42.837 TX1 | SEL/AUTO: [ Air Traffic Controller ] , [ Inbound ] 10:57:42.836 Recipient for ATC set by call contents. 10:57:42.834 Identified unit: Sukhumi with id 5000018 10:57:42.833 Getting selected unit for category ATC 10:57:42.832 Have result, identified as command: Inbound 10:57:42.830 Captured sentence: inbound 10:57:42.824 Recognized : 'inbound' (Confidence 98) 10:57:40.461 Listening resumed 10:57:40.452 Joystick : 'Transmit TX1 press'

I do them one by one to make sure they have properly initialised Sent from my SM-T835 using Tapatalk

Alternatively, you can also start a separate thread per question / bug. This thread is long because it was, until recently, the only VAICOM thread on the forum. We now have a dedicated sub forum Sent from my SM-T835 using Tapatalk

Open the AIRIO profile in VoiceAttack (select from the dropdown list on the main screen). Edit it, select the Map Marker command and then copy it to your main Vaicom profile Sent from my SM-T835 using Tapatalk

It mostly works for me, but they appear every now and then, particularly on inbound calls Sent from my SM-T835 using Tapatalk

Some of us are experiencing issues in the KA-50 at the moment. It is a recent issue with the latest release and is currently being looked at and relates to the non response you are getting. It seems to work OK for me with Easy Comms on so might be worth giving this a try to see whether it works for you. The issue only seems to affect some modules. In terms of the language, use the Force options on the preferences tab of VAICOM config. Sent from my SM-T835 using Tapatalk

And yes, you can use open beta Sent from my SM-T835 using Tapatalk

Which plane are you trying in? Sent from my SM-T835 using Tapatalk

Which plane(s) are you trying, which version of DCS and what type of mission? Sent from my SM-T835 using Tapatalk

Has this worked for you before today's update? Sent from my SM-T835 using Tapatalk

I am seeing the same thing

I have just tried my TM Warthog with today's patch and it works as expected (I have tried all three autopilot modes) - I don't run target and just use the control mappings in DCS

patience - patch notes are posted before the update goes live. It could still be a few hours

Have you changed the path in the Windows registry? Sent from my SM-T835 using Tapatalk

TACAN Tune is part of the AIRIO extension and therefore only applicvable to Jester. With the exception of the 'Select tunes radio' option VAICOM is not intended to undertake cockpit control. You can either add your own commands to do this or daisy chain other profiles (such as Bailey's) which are designed to do this.

There is a checkbox on one of the Vaicom config tabs for automatic updates Sent from my SM-T835 using Tapatalk

Are they in the VA list of commands for the VAICOM profile? They will not appear in the keyowrds list in VAICOM config Sent from my SM-T835 using Tapatalk

Even easier is just to move the whole dcs installation to the new drive and then run a repair to update the registry key Sent from my SM-T835 using Tapatalk

I have both TM WH and F18 grips on my warBRD base quite happily. Just need to select the grip in the Virpil configuration software and save it Sent from my SM-T835 using Tapatalk