Greyman

Using just the DCS ATC, I don't recall hearing messages like "hold position" or "continue taxi". Are you sure that those are not messages that the mission creator has built in to the mission? For example, the recently done red flag missions just require a space bar to be pressed and do include more verbose instructions from the tower.

sounds like the audio device that DCS is sending sounds to is not the one that is being used by VoiceAttack and the latter is switching the selected audio device on startup. Maybe check the settings on the VoiceAttack Audio tab.

I might just call "Arco" "Fred". ;)

i added my, perhaps rather odd, pronunciations of the Georgian airfields, as there was no way i was going to get the default ones correct. i'm actually going to have to add one for "Arco" as, for some reason, i can't get that one right at all

LOL, i feel that :)

If you just want to test it up to the point where it tries to communicate with DCS, then yes. the other thing that looks a little odd is that there appears to be more than one TX button held down at once and that is not something i have seen before, let alone know what it would do to the VP logic. Edit: i use a hat switch on my WH throttle, with the four main PTT buttons mapped to each of the axes, so it is not possible to have more than one TX pressed at any time

i can't see it on the update log, but you might have seen it on the todo list that came out just after the patch, IIRC.

the module will need to be live and from your second image it does not appear to be. the PTT screen should contain the F16 label and have the almost correct TX buttons displayed, like the second image of your previous post.

that would probably be a mode that has yet to be implemented, unless it was included in the latest release.

maybe check that your windows default audio device, via the speaker shaped icon in the tray, is set to the device you are using and not to another device, as that is where those "beeps, blip, click, thud and flat beep sounds" will be sent. Either way, your PTT screen, from your second image, looks "right" as it is, apart from that display issue, so you can probably forget that being the cause of your issues. btw, it's VAICOM PRO

those before and after pics are exactly the same as mine. the first shows how the PTT screen normally looks before you select a module and it doesn't change, to the second pic for example, until you actually get into the cockpit and press the OK button to start. as @MAXsenna says, the TX1 button should still work, even though it isn't displayed in emboldened text. the display issue will apparently need to be fixed by ED, according to that post of Hollywood's that i linked a few posts back.

on the PTT tab, can you only see TX2 or can you also see an unemboldened TX1, as I can see the latter and although it might look odd, it does still work? Edit: I might have TX1 and TX2 mixed up, as I am away from my PC atm, but either way, one is displayed as bold text and the other not.

How do you handle comms as I had a similar experience when using voice recognition. As the track replay just appears to start the aircraft and then apply the commands that you did during the flight, it might not pickup the "approaching for refuel" command or "ready pre-contact", so the track can't show you getting fuel. However, mine did then crash into the tanker, which it hadn't done in the actual flight, so comms may not only issue.

There has just been an update of DCS, so make sure that you have deleted the export.lua file, in ../saved games/<DCS folder>/scripts and then restart DCS and voice attack. If you then open up the config window, with Ctrl-alt-c, and go to the PTT tab, when you get into the hornet, it should correctly identify the hornet and the active PTT buttons.

There is, I'm afraid, a hierarchy of bindings and the general and UI layer bindings will always overrule the ones you make for your aircraft. You might get be able to change the general ones, but finding a different one for your aircraft might be a better idea.

an open refuelling door does appear to have a significant impact on the smoothness of the flight, especially for a relatively small "hole".

make sure that you don't have game avionics set in the MISC tab, as that will probably result in you changing one profile, when your aircraft is using a different one.

2.5.12.1 recognises the F16C as the F16C. It looks like your autoupdate hasn't worked, so it might be a good idea to do a manual update.

https://forums.eagle.ru/showpost.php?p=4063228&postcount=3062 This post, from just a couple of pages back, might help

I had no issues with it after the update and although I didn't do a ground start, I did make great use of the AR DISC button, it let me take fuel subsequently. Give it a try

apparently it affects all aircraft, but is likely to affect WWII aircraft more than the later jets.

https://forums.eagle.ru/showthread.php?t=151478&page=22

no worries. for some reason, that checkbox appears to be the cause of quite a few controller issues at the moment. i think the main issue is that when you adjust controls from within the aircraft, it appears that you are changing the sim profile, when in fact its the easy/game mode profile that is active.

you're probably going to have to change it again, as the latest update to the AB meant that it activated at below the detent. for me at least. i just raised all of the numbers by a few points and that seemed to fix it. 0-6-13-21-30-41-54-67-90-100 if anyone is interested.

well it looks like the Viper's carbon footprint has risen dramatically, as the fuel usage in AB appears to have been fixed. Suffice it to say i have changed my thrust curve to avoid the AB kicking in early. :) oh, the AAR appears to have been fixed also, with the NWS button no longer having the undesired effect of preventing you from refueling good job ED