Zyll

Set your acquisition source from the TSD page to the TADS and you will see a broken cross where the CP-G had his sensors pointed.

If the airbase has no bluefor near it, and it has redfor ground units, they will capture the base. If you want to prevent that, place blue ground units at the base to keep it defended. They could be invisible and immortal if you don't want the red ground units to engage them.

I agree the ASE screen should correspond to 12 o'clock always being the top of the screen. However, I think logically the TSD screen should adjust the position of ASE contacts in accordance to the orientation of your own ship. This is only my opinion on what makes sense, and you are right, the SMEs would need to weigh in on what is correct behavior in real life.

When using TSD - MAP - ORIENT N-up (north up), when you get an ASE vocal warning (e.g. SA-8 12 o'clock), this is correct, however the TSD should visually show the symbology in front of the aircraft. What is instead happening, is the symbology in this case is at the 12 o'clock position as if we were in TRK UP orientation. north up.trk

That's interesting. I didn't do Caucasus, I was on Syria and maybe Marianas. Not they I think of it, my timing might be from the moment I start the battery in my startup procedure. What I had noticed, is that turning on the Doppler has no effect on the speed to alignment.

The charts on the TSD also appear once the alignment is complete, 4:20 to be exact.

How do you get Vaicom to work with the radios in the Apache? Specifically, do you need to map multiple Vaicom radio PTTs, or can you use the RTS rocker to select the desired radio, then use one Vaicom PTT to communicate on the selected radio? I'd like to be able to rocker to the UHF, speak "Truman Select" and it would tune the UHF to my Truman freq. It doesn't seem to work that way though. I've used Vaicom successfully in the Hornet and the Huey, so I have a good idea what i'm doing, but the Apache is still a mystery.

Main thing that Vaicom brings is immersive radio comms with AI, like tankers and jtac and the super carrier. I like it alot, but it's not a macro button pusher, that's where VoiceAttack comes in.

Ahh yes, that's it, good catch

Barometric alt appears in the top right when you have the pitch ladders showing with transition symbology, but it would not appear otherwise. Radar alt should show all the time.

Hop into an Apache (PLT or CPG station), and turn on your NVGs. Turn down the brightness to a comfortable level. Now turn the goggles off and back on. You will notice the brightness is back to its default setting. Note, I'm referring to the NVGs and not the IHADSS w/ FLIR.

i've been using one PTT in Vaicom which in SRS communicates with the radio selected via the RTS rocker switch. I've also had 4 hat buttons mapped to 4 bindings in Vaicom, but it seemed inconsistent whether Vaicom would be listening to me. It's a different kind of setup from the Hornet.

Is the Vaicom trigger (like push a button then speak "chief request rearming") being finicky for anyone else in the Apache? It works sometimes, but often doesn't. I think that its toggling between VoiceAttack listening and not listening depending on the Vaicom triggered keypress action, as opposed to acting like a push-to-talk. I assumed that I just need to wait for a Vaicom patch in order to support Apache, but @MAXsenna above indicates its working fine already. Other modules (Huey and Hornet) are working as expected, so my Vaicom and VoiceAttack install should be fine.

Hmmm, I'm going to guess it won't work unfortunately, as the programming would be to the base not the grip. That's just a best guess though. If it doesn't work, a third party software like Joystick Gremlin might accomplish what you are looking for, I don't use it though.

I don't have alot of experience with multicrew, but there are posts mentioning desync. Honestly, I'm not going to be very helpful here :)

In the virpil software (the one that you use to update firmware) take the physical button mapping for the flip trigger, create a new logical mapping, but have it be an INVERTED button. That way, when you pull it, it will cause one logical button press, and when you don't have it activated, it results in a different logical button press. Then you can map both states separately in DCS.

Did your pilot switch to transition mode for his IHADSS symbology? That should cause the wp info to appear.

It hasn't been released yet. Eta March 31

I was wondering if Instant Action mode is using the game flight settings for some reason, which would then explain the issue you are having if the control mappings are set different between game and sim. Otherwise yeah, it's an odd one, I can't think of any other reason.

Are you perhaps changing the control mappings under game mode vs sim mode?

Yeah this is what I'm thinking. If you cold start and spawn on the catapult specifically, your chocks may be placed, and worse yet, the ground crew can't remove them.

You may want to start a separate thread in the Viper forum and continue the discussion over there, since we are talking about an F-16 skin. Looks great!

I believe the change they implemented, is that pressing undesignate while Mav is SOI now allows you to slew the mav seeker from it's original position. Handy when you want to unlock the seeker from what the tpod is looking at. Before, in order to do this, you had to make the tpod SOI, undesignate, go back to the mav seeker, and you could then slew. This is all with respect to the IR mavs

Wait, iff is not just depress? I've been using it wrong all this time? Lol

Make sure in the Mission Editor to specifically place a supercarrier. This means NOT to use the Stennis or Forrestal.