m4ti140

No MiG-21?

[Vodka] Matroshka EDIT2: Actually **** it, I'm not cancelling Su-33 F-18 if needed

For me the game freezes and requires killing it through task manager when spawning into cockpit. At first it only happened on 104th, now it happens on more and more servers... I think it might be related to the video memory management "improvements" they've done a while ago. I'm using a mobile system with only 2GB of dedicated VRAM (960M) but able to use up to 8GBs of RAM as shared memory once it runs out of dedicated VRAM. Before they've done these changes the system simply offloaded stuff to RAM and I could load fine into any server, though it tended to stutter. Now I can't fly at all on some servers and it's getting worse. If you could let us disable that VRAM optimizer "feature", or just disable it automatically on machines on which it causes more harm than good (like literally any optimus card) it would be helpful.

[Vodka] Matroshka MiG-15 F-86 if all slots for MiG-15 are full

[Vodka] Matroshka MiG-21

IIRC it's fixed by flipping the switch on the radio panel to РАЦИЯ, by default it's in ident mode which messes with vaicom for some reason (you're supposed to do this anyway, it's just that it's bugged and for some reason you can still use the in game radio while the switch is in the lower position).

[Vodka] Matroshka - MiG-21

Charts don't show you stuff like roll coupling. Nor extreme edge of envelope phenomena.

[Vodka]Matroshka MiG-29S

I have a couple of questions: 1. What order do the AI aircraft spawn in and take off if all wp0 times the same? I'm currently trying to get an E-2 to spawn with me and my wingman, then taxi to cat and take off before me. However, no matter what I try the E-2 won't budge until I'm off the deck, even if I have it set to be hot on ramp. I'd just put them into a catapult, however: 2. No matter what I try, the AI will always spawn in cat 1, regardless if it's blocked or not. The changelog from a month ago said that it is now possible to select catapult for the aircraft to spawn in in mission editor but it does not appear to be the case: is it only possible with player/client aircraft?

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...