m4ti140

Actually, most of us have throttles with at least one knob, usually 2, coming to a total of 3-4 axes ON the throttle grip (not counting the throttle itself). The Warthog throttle is literally the only high end throttle with just a slew sensor. And not a single one has a self-centering axis that could simulate the one in real Hornet.

@Greyman Thanks! @Hollywood_315 OK... now it looks like VAICOM is completely unable to detect what module I'm flying. It was already dodgy in 2.5.3 (the module did not always update, and if it did, the exposed variables often didn't) but now I'm yet to have the module detected even once, it's just stuck in (default).

Pretty sure that's how it works in F-15 as well. Or in BMS. In ACM mode the range is fixed

@Hollywood_315 How do I update the keyword database? Neither the instructions in the user manual, nor the ones in the pop up window make any sense whatsoever. The former tells me to paste them into the "Keyword collections" but it's the name of the whole category, not of any command. The popup tells me to paste them into an AI communications command, but it's not there either. There's just a long list of individual keywords within a "keyword collections" category.

EDIT: Count me out again, won't be able to make it.

Su-27 doesn't have active missiles in DCS

What chart? First time I heard about this...

The latter is not possible with ships, because they lack the "Transmit Message" command in AWA

Also, cause it's happening more often to me now: Sometimes the first three exposed variables don't set properly, the module name gets stuck on "----" and the other two are not set. When it happens, the module specific functionality set with the exposed variables doesn't work. EDIT: It looks like the variables fail to update on numerous other occasions. For example: after flying the Huey for a while I fired up the cold carrier start mission for the Hornet. The aircraft updated correctly in the VAICOM config menu but the variables kept showing the Huey EDIT2: I also noticed that the settings don't update at all until the config menu is opened. Until it's opened, the plugin doesn't work correctly, it doesn't load the radio configuration, it doesn't load the player callsign, etc.

Guys, now that I have it sorted out and I highlighted the PTT issue with Huey: Are you guys planning to implement flight crew commands? E.g. for the gunners in the Huey and, in future, possibly for the F-14 RIO?

Could you add TACAN to your ships? EDIT: Also: the ramp start position is too close to the island for the Huey on Essex. The Osprey model on Essex is also missing textures - have you considered making a clear deck version, now that we can populate decks however we want in the editor?

Not him, but TWCS actually has a spring loaded switch that mirrors the Hornet throttle and should be used as an antenna elevation switch instead. It also has the analog paddles if someone wants more axis travel for control. So there are multiple ways to map the antenna elevation to a more suited input on TWCS, no need to use the rotary at all Other setups don't have this though. I use an X52 Pro and with every other module I can just set the antenna elevation to the RX rotary, mirroring the setup on the F-16C TQS, which the X52 throttle is loosely based on. This includes the F-15, which IRL uses a spring loaded switch just like the F-18C. F-18C is the only one that stands out. Even though the X52 has a notch in the middle, it's still a chore to control it, particularly because of the potentiometer drift that the X52 rotaries have when in the center notch. Similar issues apply to the X55 and X56. The VirPil and VKB throttles are both based on eastern HOTAS setups, with a range dial. There are cases where a compromise has to be made between realism and practical/technical aspects of the sim and this is one of those cases. There is literally one throttle on the market that can have the antenna elevation mapped correctly for the Hornet right now and it's a mid-range fidelity throttle. Every other one requires an alternative absolute axis.

EDIT: Count me out, I forgot about the race.

It's literally a fresh install of VA. Also no matter what I try it is completely unable to differentiate between "Arco", "Cargo", "Outlaw" and "Out Cold". Right now each of those brings up the "alternatives" panel. EDIT: A little update: Forcing AEC off and enforcing US version of MSR in VA options seems to have significantly improved recognition.

OK, putting it into a separate post for clarity, because this is most likely a windows 10 issue: The MSVR window keeps switching to dictation mode when in training, showing me the spelling window when it doesn't recognize something. The worst part is, if I try to add a word to the dictionary, from this point on it will show me the "alternatives panel" and trying to write it into the command phrase field. VA doesn't recognize the phrase either. EDIT: Judging by its behaviour, MSVR doesn't stick to the VAICOM command set but listens to every single word in its dictionary. Thank you Microsoft...

OK, thanks for the replies. Is it even currently possible to have one of the TX buttons override to one of the radios while the dial (SEL/AUTO) mapping is active, or will it require additional coding on your part? I'm going to get the PRO license today and start setting up the profile for my module-specific setups, I will PM you if I run into further problems. Looking forward to updates on the Huey functionality. EDIT: As for why this wasn't raised previously - my impression is that most Huey pilots either use a standard mapping ignoring the actual functionality, or only map the second stage due to limited use for the Interphone in DCS (ground crew only). I planned to map the co-pilot/gunner orders as additional commands attached to the interphone node (TX5) to give it additional functionality besides communication with ground crew but the single button mapping we have right now kind of defeats the purpose. Can the module configs be edited manually in the PRO version or are they all locked up?

@Hollywood 315 With regards to 2: The thing is that the Huey uses both single and multi mapping at the same time, if that makes any sense. Is it possible to have one TX button force Interphone and another stay as "SEL/AUTO" (which would replicate the real Huey setting)? As for 1: Do you mean setting up multiple TX inputs with their actual commands wrapped in conditional statement checking for the currently active module? I suppose that could work for me, thanks, I will check out the pro version. Still, do you have any plans for using the in-game assignments as PTT (assuming it's even possible within the VA API in the first place)? EDIT: Why does VAICOM change the behaviour of in game PTT buttons? Before installing VAICOM pressing the trigger to the first stage opened the interphone menu and pressing the second stage opened the selected radio menu. Now, regardless of which button I press it opens a "SEL/AUTO" menu even if VA is not running at all. Easy comms are off. Did the scripts installed by the plugin change this behaviour? EDIT2: Resetting lua code brought back the old functionality. I uninstalled VAICOM for now. Why does VAICOM make unrealistic changes to how the radios work within the module itself? Huey uses two PTT buttons, not one.

I have 3 questions: 1. Is it possible to use completely different control assignments for each module? I use completely different buttons/hats as PTT depending on which module I fly, for instance when flying the MiG-21 I use a throttle button, for the Hornet I use the throttle hat as PTT and for the Huey I use the stick trigger instead. This was never a problem with the in game radio or with SRS but it looks like VAICOM requires a single setup for all modules. Is it possible to have different buttons assigned to the same "TX#" inputs depending on which aircraft is used? Or, alternatively, are you planning to allow the in-game mappings to act as PTT in the future? Otherwise I don't think I'll be purchasing the pro version (EDIT: unless it's a VA limitation). 2. Is it possible to switch between "single" and "multi" setups for a given module? Is it a PRO feature only? Or is it permanently assigned to a module? I'm asking, because the Huey has two PTT inputs (first stage of trigger for the Interphone, second stage depending on the dial selection) but in VAICOM it is listed as "single" key, with only the "SEL/AUTO" key available for assignment. EDIT: 3. Is it possible to assign multiple key commands to the same TX function within the same profile? Or does VAICOM rely entirely on the spoken command name to work? I want the PTT on a two-stage trigger to release the first stage command both when the first stage is released and when the second stage is pressed (on X52 pro the first stage remains pressed when the second stage is pressed), to make room for the second stage command. Analogously, I want it to switch back to interphone when releasing second stage. EDIT 2: Disregard 3, made it work by manually editing the input order within the tx commands. It's nice that you have the actual commands sent to the plugin exposed.

Matroshka - MiG-21

This may be old info by now, but it looks like they recreated the entire city of Shiraz.

Same here. Managed to get it unstuck by disabling force trim and applying full pedal

For some reason, no matter what weather I set, the active runway is stuck at 7R on McCarran. Heavy AI aircraft struggle to align to the runway due to terrain. They refuse to use the reciprocal runway even if it results in heavy backwind.

Same here, installed according to instructions and it just refuses to work.

Second this, there should be a "salute" keybind as well as ability to signalize abort (followed by unhooking from the catapult) when things go bad. Even the carrier mods for ArmA 2 had something like this.

Isn't the whole point of flight simulators to NOT have to do simulated exercises like those? I mean, I doubt during sim training the pilots do field traps... that would be pretty pointless.