Radar Newb Questions

[Nagilem]

So working on A2A engagements in the Viper and found I am struggling with:

 

1. Once a target is STT, where do I find the range and closure to the target? Not seeing anything in the HUD that I would associate with range to target and my closure. I'm sure I'm just missing it.

2. Once I use the DGFT switch, how can I change missiles from 120s to 9s from the HOTAS? For some reason after the first use of the DGFT switch, the missiles on the gun / no radar mode moves to 120s and I have to look at the stores MFD to change back to 9s.

3. Is there an auto acquisition mode for the radar that goes out beyond 10nm? having to adjust the radar for both elevation and cursor for lockup is painful when enemy is between 10 and 20 miles. I usually end up eating missiles while trying to lock up the enemy.

4. having issues with EEGS without tracers - is there any other gun modes? I suspect these are WIP - LCOS and other radar gun modes.

 

Thanks for any replies!

[Frederf]

1. "F" figure in lower right corner text block of HUD.

2. You'd normally step missile types with long press of MSL STEP button, not yet implemented. Each selection of DGFT should select priority SRM (or last selected SRM I think).

3. As far as I know all ACM in DCS's version is limited 10nm. There are MLUs with up to 40nm boresight mode (other modes 10nm max). Yes, outside WVR but inside 20nm CRM is a challenging situation.

4. LCOS and SNAP, not yet implemented. FEDS and BATR display should provide good EEGS feedback without tracers.

[Harker]

Several items are WIP, but generally it is:

 

1. In all AA modes (AA button, MRM and DGFT throttle switches), range to the target is displayed on the lower right portion of the HUD. You can also get a an idea of the range by estimating on the FCR page (you have 1/4, 1/2 and 3/4 range tick marks on the B-scope). The closure rate is provided on the HUD as the number next to the range caret on the DLZ in AA modes (not in DGFT in DCS, but I'm not sure IRL) and on NAV mode.

2. It's not implemented yet, but the long-pressing the NWS button on the stick should switch between available A2A missile types. The DGFT switch should always select the AIM-9 (if available), so that's a bug. So you have to wait for fixes on 2.

3. Not as far as I know. I do not think the Viper has something like the AACQ mode of the Hornet.

4. We'll get both EEGS Level 5 (with firing solution and other cues) and LCOS at a later date. In the meantime, you can switch the gun ammo type to a type with tracers, via the Mission Editor.

 

 

Hope this helps :)

[Alfas]

1. Closure Rate is also at MFD(FCR) top-right corner

3. TWS mode can bug nearest target with just a TMS right

Edited November 20, 2019 by Alfas

[Harker]

1. Closure Rate is also at MFD(FCR) top-right corner

Yeah, that too, I forgot to write it. Alongside other target info. In the sim, it's the only way to get closure rate in DGFT mode, because DGFT doesn't display closure on the HUD right now, IIRC.

[Nagilem]

Perfect guys - thanks for the responses!

 

A follow up - is there anything additional that can be added to EEGS for more useability? Also, any way to set the tracers as a default? I like the challenge of no tracers, but it becomes hit and miss with the EEGS funnel. I think a pipper would make no tracers much easier.

[Harker]

Right now, you can't add anything more with EEGS. Place the target's wings in the funnel and fire using your best estimation. Use it as a general tool for now, since you can't adjust it for wingspan yet, so you have to rely on "more-or-less" estimations. There's a MAN option in the DED (List->5) to allow you to set the target's wingspan manually, but it wasn't implemented yet last time I checked.

 

Having a working director makes aiming much easier. I never use tracers in the Hornet, for example.

 

As far as setting tracer ammo as default, not from within the game. If there's a way, I suspect it'd be in the F-16C.lua file, but that would lock you out of most MP servers.

[Nagilem]

Thanks Harker - that helps. I guess I'll just have to practice with the funnel until another few updates give us more modes to work with. Will also try the no tracers in my F-18.

[Wicked.-]

Tracers definitely help but if your pulling G's and the target is rolling it's a bitch. You're best bet is to have patience and close on the target, dump your G load and shoot. When I say close on the target, I mean to a distance where the target fills at least a quarter of the HUD.

Any time you reload with ground crew, choose the top option for gun rounds. HEI with tracers I believe.

[Nagilem]

@Wicked - thanks!

 

One other question - where do I find the bulls of my cursor or the bandit?

 

I think the bulls on the hud lower left is my position from bulls, correct? where is the info on my cursor on the radar or on the bandit once I either sam or stt the target?

[Harker]

You're supposed to have the cursor position from Bullseye on the bottom left part of the FCR and the HSD, IIRC. It's not implemented yet. For now, the HUD and both the FCR and HSD (blue circle) pages display your own position from Bullseye.

Edited November 26, 2019 by Harker
corrected right to left

[Wicked.-]

@Wicked - thanks!

 

One other question - where do I find the bulls of my cursor or the bandit?

 

I think the bulls on the hud lower left is my position from bulls, correct? where is the info on my cursor on the radar or on the bandit once I either sam or stt the target?

 

The Bulls is not fully implemented yet. For now, all Bullseye references on the HUD and MFD”s reference your position. Eventually, the FCR will tell you your cursors bulls in the lower left side. At least that’s where I’ve had it for 20 years.

[Wicked.-]

This is what I’m used to seeing in the Viper. Whether or not it’s correct and implemented the same way remains to be seen.

 

Edited November 26, 2019 by Wicked.-

[Kid18120]

where is the info on my cursor on the radar or on the bandit once I either sam or stt the target?

It isn't implemented yet, i believe

[Nagilem]

ok thanks guys. wasn't sure if I was just missing it or didn't have it configured.