ricktoberfest

I haven’t flown the mirage for a bit, but I believe when you launch it automatically changes modes.

I believe you wouldn’t get negative g reported on the hud as that’s measuring G in relation to the vertical component, not acceleration or deceleration.

As for the flaps, if you have asymmetrical flaps extended it’s likely you’ve oversped them. Raise them before you hit 225 knots.

Would be handy when you want to create a mission in pancake, then fly it in vr

If we’re being honest here, the AI are just as quick to see, target, and engage us. I feel it levels out the playing field a bit. Do you really think a tank can spot, target, and shoot down a fast moving low altitude target in less than 5 seconds?

That’s correct. Even using the default radio menu doesn’t work properly in the Apache when VAICOM is running. Mostly an issue with trying to command wingmen. I don’t even bother with ATC anymore.

Turns out it doesn't quite work like that. My main problem is that the radio commands for the apache don't execute when they're recognized. Sometimes I can force it by repeatedly pressing the radio button but thats not really a solution. I've alread got other commands on voice attack in that profile, but radio commands won't work while VAICOM is running as it takes over the radio. Alas, having a different profile doesn't seem to work either as the plugin isn't connected to a profile so its still running in the background even when I've deleted all the commands. Looks like my only solution is to disable the plugin and restart voice attack each time I switch to the Apache. Even creating a new profile still loads up VAICOM in the background preventing my own radio commands from running.

I never thought of that! I don’t use profiles for voice attack and so forgot it could do that. Thanks.

I myself added the command “inbound for fuel” as I was always getting confused about which command to say. It’s actually a pretty simple process. Since Hollywood hasn’t been back in awhile, anyone know a way to disable VAICOM for a specific module (Apache)? It’s really unusable for me but I have voice attack commands programmed so I don’t want to just shut it down each time.

The LMC needs to be manually moved doesn’t it? Not gonna lie, haven’t played the Apache much since latest update (and since Viacom doesn’t work with it) but the LMC only moves if you move the joystick, it’s not actually tracking the target like a point track would. I think you might have a different problem than you think is happening.

If you over-stressed your engines during the dogfight they might create less power (like during landing when you notice it). Keep an eye on your engine temps and try not to go over 645EGT for more than you have to.

The tabs aren’t mouse clickable. The terms for the pages that work for me are “fuel page” “log page” “notes page” “flight page”. At least I believe that’s so as I haven’t used it for awhile. Not sure about the JTAC page anymore. If you use the vspx processing then you have to change some stuff up but I can’t remember exactly what. It’s in the manual near the end.

Yes

It’s got issues with the Apache right now. Waiting for an update.

Check keybinds i guess.

Yes. Action missile, check box is solid meaning guidance locked on laser, fire.

I know you made this comment awhile ago, but I’m having that queue issue too. Vaicom beeps like it heard the command, but it can take several minutes before it sends the command to DCS. I’ve noticed that if I key the mic several times I can jump start the queue but did you have a different work around or fix? (Apache only)

These a mission here in the forums/user files called Foothold (version 1.3.2). It’s a dynamic mission with persistent destruction of enemies. I’m assuming one of the scripts it uses is similar or the same as whatever script blue flag Syria uses. The graphical corruption doesn’t show up right at the start which leads me to believe that some script is causing the issue. Previous versions of this mission didn’t seem to have this problem, but the latest does for me. Blue Flag Syria has this problem consistently for me after I load up and access the F10 map

I also have this problem occasionally. It started on the blue flag Syria server but I’ve also seen it while playing the foothold mission. I’m thinking there’s a script somewhere that’s causing the issue.

Press lock and then slew the shkval with the uncage button pressed. If it passes over a target it should stick to that target. If it takes more than a second or 2, release cage button and go back to beginning (press lock then slew) adding in here: make sure the size gates are appropriate for whatever you’re trying to lock. Practice locking a friendly target that isn’t moving and then practice with another helicopter.

Its already there, just labeled different. Its the option that says FFB Friendly I think. Instant trim or something.. cant remember but Casmo had a video talking about it.

I figured it out. Needed to press the lock button within a very short time of slewing the HMD. Too long and it stops trying to lock. Works for a second or 2 then you have to repress the lock button.

How do you activate auto tracking? I’ve tried with pressing the lock button, then slewing the hmd but it hasn’t seemed to work that way.

There is a dial in the cockpit (front left lower I believe) that adjusts the brightness of your head mounted display if that’s what you’re talking about. Try turning that dial up. There’s also an axis binding for it if you have an extra axis on your joystick.

I remember at some point being able to lock a target by simply using the hmd and holding O to move it and lock it when it came within the sight picture. Was that a bug or have I simply forgotten how to do it? I’ll add that I was shooting down Apaches the other day like flies, but it was hard to get a lock on any closer in maneuvering targets.