Florence201

Looking at the posted roadmap for Viper, i'd say a little while yet.

Tried multiple variations of head position, now have a 34" widescreen and still having issues seeing all of the RWR

Real world docs are quoting 5m2 tgt at 65nm

Snow Plow mode is declinated lower than HUD. I can’t remember the number but it’s shown in the TGP screen by the Cross/Nth point

Viper pod doesn’t have IR marking. Just laser designation only.

You need to enter the ILS heading for command steering bars/bug to show you L/R deviation from course. Without a heading, reference you’ll not get correct information

You can have either TACAN needles or ILS needles. If you fly the approach as per the plate, you won’t get ILS localiser until approximately 12nm, then glide path activates at around 8nm. use TACAN to get to within 12nm then switch to ILS localiser

Whatever you set pre start in the kneeboard, be sure to set in the Laser DED page too

You are correct wrt real life, would be nice if ED could confirm their modelling of this

Can we not mix Viper and Hornet issues in the Viper forum.

I thought FCR speed was Ground Speed????

As the title says, when loaded with AGM88C, no BULLSEYE information is displayed in the HUD. Once you have MAGNUM'd all, BE info returns.

If you want a game, play BMS. MiG you want an attempt at realism, stick with DCS

I find it far better this new setting

I would check for double keybinds. I haven't watched the trk file, but if you're pressing one key and another action is happening, then check binds

Hidden on Map is the one that works for not showing up on an MFD

It’s been adjusted to what it is now, as the consensus was it was too slow!

There are a multitude of skins available in the DCS user download section

You're in PRE mode but without the TGP sending any form of information at the minute. So the Mav is looking at it's boresight.

Yes. Certain ship radars are in the Additional ALIC code tables

Over runs by approximately 3-5 seconds in all testing/sorties I’ve carried out possibly linked to “incorrect height for different Baro alt settings bug” that has been reported

Taz, Why the 2 versions if i may ask?

Having had another look at your picture, did you correctly BORESIGHT the Mavericks before this point? That would explain the offset between TGP and Mav LOS

If you don’t set and Alt, then the default is 6600’ iirc. But it can still float above in the HUD despite correct Alt set.

Have you input a waypoint for TGP to be slewed too? If so, increment away then decrement back.