Florence201

Ok, but again, why would you want the Autopilot on during AAR? Very unrealistic

So TWS needs to see the radar paints twice in 6.2seconds to create a track file. If the contacts are closely spaced, then using EXPAND may help you see them. Also detection range is RCS dependent.

Why would you do this? That’s dangerous

On the Viper front page. Hasn’t been updated since July last year though

You know Viper is WIP right??

Google is your friend

Off by default

Wasn’t til I saw the screen shot that it was apparent!

It appears you are in MSL override mode. An A-A sub mode. This is selected using the DGFT switch. You need to ensure that this is cancelled before going to A-G.

3/7 will get power automatically once jet is powered up. Then SMS page in A-G to power up 88Cs

What stations do you have the HARMs? If they’re on 4&6 they won’t work And you don’t need L/R chin power on for HARMs. That’s for TGP power when fitted (5Right)

Drawing a line will give you True Hdg. You then need to convert to Mag hdg using the declination for map and DTG

NWS toggling is pilot operated only

A colleague experienced this in MP yesterday, but without the use of gnd power. reselecting the same function on OSBs cleared it

I have no such issue with wheel brakes with my toe pedals set up. Try adding a dead zone of 5 to each keybind, such that you have a little "wiggle room" before the brakes are applied. Plus, with the Viper, you Aero brake to <100kts, then slowly apply wheel brake. If you're trying to wheel brake from 160Kts, you'll struggle and things like what you're experiencing will happen.

The wheel brakes are locking up as you brake, hence the black skid marks on the runway. Set rudder toe pedal wheel brakes in the assign axis menu, then they will be incrementally applied as you apply pressure, rather than digitally on/off

So if you’re using rudder pedals, ensure you have both L/R assigned i also notice from your pics that you’re locking up a wheel. This will cause the nose to slew towards the locked side

No problem at all. Should have 45 seconds per JTAC message now

Released V1.4 17 March 2021 Increased text time for any positional data displays (ie, JTAC 9Line) MISSION 3: Moved C-17 so landing does not conflict with taxi Copy/paste new files if campaign already started

Thanks for the feedback point1. Wholly on DCS that the AI won’t taxi if another is on the runway, despite ATC clearing you to taxi??? point2. To have the 9line indefinitely available would mean having the F10 menu option constantly there. Happy to increase text time to 45 seconds on both showings if that would help? I could probably get a release out this week with the text time increase.

So many different docs saying the carrot is TA/AA,HCA. be nice to know what it is ED have modeled it as

HUD AA is incorrect in DCS Viper. In the instance above it will show ref the 12 o'clock position in the HUD carrot, where as in SHOULD shows what the FCR shows. ie, 030L watch at 9:20 as wingman locks lead for rejoin.

Uncage will reset any lock you’ve had with the 9X

You may find the online server has easy comms on. This will override your local settings. When you go to the multiplayer screen, click the server you want then check bottom of the screen (Right hand side iirc) and it will tell you what settings the server has.

New verion released. V1.3 15 March 2021 Multiple Missions: Fixed CASEngagement Issue MISSION 2: Fixed rogue Static unit Copy/Paste over files if already downloaded