Hulkbust44

It absolutely can. It's a tack file the jet created from a donor.

Not entirely true. You should absolutely be able to guide the missile with data from an off-board donor. It's just that it's your radar antenna that's used to send commands to the missiles so you don't need to see them on radar, but the nose needs to be pointed in that direction.

As a matter of fact, there are one or two real world clips where you can see this exact thing happen. Ther *is* a bug here though. The B-sweep is fixed at 0 ATA, the radar being silenced should not stop the sweep. (Easily observable in cockpit videos)

No problem here. Pressing NWS steps to the next trskcifle, and you have a trackfile as an AOT for a jamming target.

TDC depress should be the control. You said that you are undesignating each time right? The BFL being tied to the point is correct. I can't view the .trk for a while.

Make sure you have the TDC set to the FLIR display and not the HUD moving the target point.

From level flight pressing TDC depress with priority set to HUD will designate the point on the aircrafts heading 7.5° below the horizon. When you dive at an angle below 7.5° the targeting reticle will be caged to the VV. Edit: word

Nope, the Nite Hawk was the original FLIR which was replaced by the LITENING for use from air bases. The Navy kept the Nite Hawk until the ATFLIR.(had to)You can also see that the logic for the DCS LITENING is ancient.

I was strafing a convoy of light vehicles right after the patch it was dead on. Only been using the PGUs, but it felt like there was a difference in the reticle precision.

With the unrealistic TDC slew option, I propose the following changes to the control logic to make the A/G radar compatible with HOTAS systems that can not depress and slew simultaneously. (No change) The top-level TDC slew control will be the TDC captains bars cursor when applicable. (No change) When there is no target designation, TDC depress within the TA will command a TGT designation at the point under the cursor. If there is a TGT, TDC depress will command the TGT to be immediately redesignated at the point under the TDC cursor. (This bypasses the logic of the in-video cursor initializing at the current TGT.) When there is no TGT and EXP 1/2/3 is selected, the radar FOV in-video cursor (the trapezoid) can be slewed without TDC depress. In this state, TDC depress will command the radar to the selected EXPand mode. (same as releasing the TDC with the current logic) No change to the SCS and acquisition cursor logic is required. Hopefully @BIGNEWY can pass this along to the team to improve the unrealistic TDC slew functions that many in the community struggle with due to hardware limitations.

I understand it. I just put my TDC depress on my stick and called it a day. Can and do have depress on the slew, I just don't like to use it with my hardware. Explain to me exactly how you think this would work. A/G master mode, SCS right assigns TDC to RDDI. Select EXP 1. Now what?

It can not work that way.

Again, how would this work with the Hornet logic? You have three cursors for the A/G radar. Positive action is how you tell the system what you want. Standard slew is the TDC cursor, TDC depress is the in-video designation cursor, and SCS to the radar is the in-video acquisition cursor. There's also supposed to be a TDC depress and hold over the azimuth select the in-video cursor for scan re-centering.

Why do you think this is an issue again? If you step to another station you need to manually change the channel.

LITENING is the older model but it's in primary use by the USMC fromand bases. Not carrier rated. ATFLIR is what's used off carriers and is much more modern.

In the video RW? HMD position indicator.

Interesting, So with this later in the video when it's alternating 18 and 29 you're saying the RWR can't tell the difference between a Hornet radar and a Fulcrum radar?

Where did you get this from? Just curious.

Common misconception that TWS and RWS targeting is fundamentally different. RWS L+S 120 shot is the same as a shot from TWS man. Each can track 10 targets.

There's no targets on your radar

I'll leave this here again. 2:36

Could you possibly elaborate? Because that response goes against all logic. If the target can be detected and a trackfile created, you can absolutely tell the radar to focus the scan and processing on that track. Only time this wouldn't be true is with VS I would think, but of course we don't have VS modeled.

But you need it to for a realistic ITR as it is in DCS... I've been practicing my precise pull so I can get my ITR while not exceeding G-limits in lieu of the current FM. Just no. Paddle switch disables NWS and is the only way to disable autopilot without forcing the aircraft.

Can you give us an example? NFM-000 for sure as on the RU side ED encouraged people to read it before the Hornet release. Does that mean anything internet available that is statement C?

What public figures? Everything you can find for the 68v5 points to some 28nm for a 5m^2 target. In DCS the range is 45nm, which is absolutely absurd. The simple issue on the DCS side is the interleaving of HPRF in RWS/TWS. Seeing as the MPRF range would then be 25nm, bump it up by 3-4nm for a 5m^2 target and we're good.