Rongor

In the attached track, which lasts a few minutes, I play around with locking/undesignating a target. In several occasions, the speed tag showed thousands and inconclusive numbers. This remained some seconds before returning to Mach values. shown are examples in RWS with active LTWS target.trk

Thanks for lecturing me.

This may be very much so, yet the manual doesn't exactly tell what you claim here. The manual says the SCS decides on which DDI the TDC is working. Since you don't need the TDC on the HARM page AND the HARM section in the manual also doesn't mention the need of putting SCS onto the HARM DDI, the OP has every right to be curious. Maybe you should get better at reading what the OP described. He explicitly told us that it does work UNLESS he doesn't SCS to the HARM DDI. As we all know (and that is what you correctly mentioned above) this is exactly how it works in the current state of the Hornet. Why would we need a track file to follow a description of something that you and me can confirm? We don't. A track file wouldn't have helped you understand the OP's instruction. Luckily I understood him much better and could explain it to you. The OP asks for confirmation that SCS is needed to have the HARM controls work. The answer is probably yes. Do we know if it maybe should work without SCS if there is no current active TDC role on another sensor? The answer is no.

switch to another channel and check if all the DL symbols on your SA page dissappear.

I can confirm this, track attached. AACQ lets the target only show up as it would in RWS. No lock. additional oddity: pressing undesignate then achieves lock. Further testing revealed that occasionally it might autolock when the target is already in the FOV of the sensor at the very moment you switch to AACQ. But never if you are in AACQ mode and steer to get the target into the sensor's FOV. Then it will remain a brick. AACQ.trk

I think from the wording he used it's obvious he expected to have cycling through emitters and handoff available without directing the SCS to the respective DDI showing the HARM page before. So either the answer is, he just has to SCS to the HARM DDI before or if it is indeed a bug as expected by him. I would be curious as well as I often stumbled about not being able to designate and handoff because I forgot to SCS to the HARM DDI. Seems a bit counterintuitive and inconvenient to have this mandatory SCS input as it's unclear how the cage/uncage and the RAID/FLIR FOV buttons could possibly bound elsewhere and be misinterpreted by the system in such situation. In other words: why do we have to unlock handoff and cycling emitters by use of the SCS first? I don't understand how this can be seriously tagged with can not reproduce need track replay Simply use the HARM and you can't prevent to notice. It's impossible to miss.

This thread was marked with track replay needed. So here is one. You will see me creating a markpoint via SEA radar. Then I switch into the HSI selecting the markpoint. For editing I get into the DATA section. O/S UFC will see me entering a RNG and BRG. Values shown in the O/S data block won't update though. MKedit.trk

Maybe it fits here: If you have a radar lock and then deselect the TGT box on the SA or the HSI, lock breaks.

I disagree. With that method you would have to guess the bearing from the HPTP. With the simple possibility to define the OAP of a MK, you would know the bearing. The MK data page even offers the UFC pushbutton. Only saving the entered OAP data doesn't work. Seems rather buggy than intentionally left out.

It's just hard to believe they would leave out this obviously helpful function in the RL Hornet. We are basically restricted to define HPTP waypoint pre flight. How is that realistic? Most targets will be mobile and the coordinates will be outdated... Locating the target by radar and then defining offset HPTP would be the obvious way to go.

That would be sad. Any way to copypaste Markpoint data into a new WP?

Depends on your intended evasive maneuvers and distance to the attacker. Option one delivers a strong fake radar reflecting cloud, offering more chance to distract the tracking radar. Could be good if you are closer to the attacker and need a stronger decoy to distract from your strong signature. You can afford option 2 if there is more room between you and the attacker so you can afford to draw the chaff dropping over 10 seconds instead of 5. If you are close, you may not have 10 seconds as the missile hunting you may impact in less time.

There is this vessel on my SEA radar. I intend to Harpoon it. To make the job of its missile defensive system a bit more difficult, I want to use several Harpoons on different attack paths. We have a feature for this: Harpoon Turn Points (HPTP). So we need to create a necessary waypoint to define it as HPTP. Having a radar lock on the ship's location, pressing Mk creates a static Markpoint at the location in that exact moment. I want to have the Harpoon attack this area but via an off-angle attack., using HPTP. Now I select the Markpoint and select DATA on the HSI. This brings up the usual waypoint page, representing the Markpoint in this case. Pressing UFC opens up the editor. On the UFC I press the OAP to define bearing and range of an Offset Aiming Point. The idea is to then select this OAP in the HSI, and designate as the HPTP on the stores>Harpoon>program page. Unfortunately, all my entries for the OAP are ignored. I can enter BRG and RNG and so on on the UFC scratchpad. But the O/S data block for for the Markpoint remains filled with zeros. Is this correct behavior? Or is this bugged? Doesn't the system allow to create OAPs for MKpoints? Why wouldn't it? It would be the logical and intuitive thing for employing the HPTP function. Or is the HPTP meant for static prebriefed targets only? If it is not allowed to create OAPs for MKpoints, why does the UFC offer the OAP data entry? This smeels like "should be possible but is bugged" It would be a bummer to not have this functional. Basically it would then demand for us to take rulers and protractors on charts to readout suitable coordinates for the HPTP and then enter them by hand to create a new waypoint. Seriously, this can't be true. Is it?

Yes, probably you misread the 'isn't' as an 'is'. Also since I stated "what would be the method to create a bearing/range to Bullseye, provided A/A WP is set?" in my opening post, I would have expected you rubbing my nose onto that BRA readout in your edited post right from the start. Thanks! I am counting on you when further questions appear! by the way WarbossPetross, are you still unable to get TrackIR? There are compatible no-name Track-IR replicas for around 150 USD available on Amazon... It's not cheap but it's not as much as 2 full-size DCS modules.

wonderful, this could be the solution. Will try that.

Now you are both on the wrong track. As I already stated, I have a designated Bullseye A/A WP. If I wouldn't have this, my initial post wouldn't make any sense right? There seems no way to display Bullseye relative coordinates (bearing/range) on A/G radar pages nor the SA page. That is the major issue here.

The problem isn't that I don't know how to tell my Hornet where the Bullseye is. The issue is that there seems no bullseye readout available on A/G radar, nor on the advertised SA page.

regardless the future outcome of this investigation, I want to thank you all for participating. When I tried to get into the Hornet for the first time, inconsistencies like this made me put the module back into the waiting cue. The behavior of stuff like this some times felt illogical, unexpected and counterintuitive. Worst part of this, it wasn't conveyed transparently in manuals. Things like these confused me that much, I wasn't even able to deliver a reasonable report, as I never could say if I simply wasn't understanding the concept but at the same time couldn't find the exact concept definitions anywhere.

I assume this issue is still not cured? Expecting the Harpoon to drop from cruise altitude to sea skimming after seeker achieves target lock still doesn't work a year later. Regardless of seeker range setting, seeker always only acquires at around 5 NM distance to the target. The Harpoon then barely reaches sea skim height upon arrival at the target. The seeker range setting is useless in the current state. Harpoons will follow set cruise altitude and initial heading until arriving the 5 NM range. Defeats the whole sea skimming concept. Randomly I see Harpoons launched by me and other players dropping down to 150 ft cruise altitude initially. I still can't make out on what this behavior is based. It would be great to see anything being done about it, eventually.

You are correct, I should investigate the possibilities of putting the SA to better use, Still I don't see how to create a quick bullseye call or determining coordinates for mates who don't fly Hornets and therefore have no access to a TXDSG location...

So if there are 12 Hornets on the server doing ground attacks, we would see 12 TGT markers?

On MP servers, I only know the SA page extensively cluttered with SAM and ranges. How would they find it?

Recently I designated a naval contact in SEA radar mode. After communicating this to my buddies, they asked for the contacts position. Bearing/range call to my own location didn't help, as they weren't winging me and were somewhere else. I was confused how to figure out coordinates. Is there any method to receive a coordinate readout of your radar lock? Only things I came up with so far: I could set a MK point, then review DATA and this would get me the coordinates. FLIR could determine the coords, but only if FLIR is attached loadout So: Is there any way to do it without these 2? Disregarding coordinates, what would be the method to create a bearing/range to Bullseye, provided A/A WP is set?

I can't reproduce it anymore now in SP. Happened on a MP server. Your suggestion so far might still be the probable cause, which would be a shame.

Yesterday I was flying stable level flight, 300 kts, below 5000 ft. RALT refused to get selected. Only BALT was available. Under no circumstance could I get RALT activated. Any idea what could be wrong?