Rongor

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?

Well so far I am experiencing good results with rudder trim on in the Mi-24 and in the Ka-50. Of course you have to get used to it, so that you do the necessary control inputs without thinking about it.

Consider the following method: 1. Switch on Pitch, Roll, and Yaw channels, then takeoff. Keep Pitch and Roll activated all the time, until after landing. 2. If you intend to turn your nose while hovering, switch off Yaw channel momentarily, switch on again after achieving the desired heading 3. While doing cruise flights, keep Pitch, Roll and Yaw activated. If you need to adjust heading or speed, press down the trim button and keep it depressed, then steer until you achieved a desired nose-pitch and heading, then release the trim button. Use enroute mode at your own discretion, if you are inbound a PVI-800 navpoint. Keep Altitude channel activated optionally to keep altitude, select baro or radar mode. 4. While doing cruise flights, keep Pitch, Roll and Yaw activated. If you need to adjust speed and or altitude, press down the trim button and keep it depressed, then steer until you achieved a desired nose-pitch and altitude, then release the trim button. Use enroute mode at your own discretion, if you are inbound a PVI-800 navpoint. Keep Altitude channel activated optionally to keep altitude, select baro or radar mode. 5. When you arrived at your destination, keep Pitch, Roll and Yaw activated. Switch on flight director. Deactivate Enroute mode if enabled before. Now maneuver freely adjusting flight attitude, the activated channels will now support your control by dampening out pilot induced oscillations. You have to keep pressure at controls to keep desired attitude. Optionally you can use the trim button to ease the pressure (for example to fly a continuous circle with a stable bank angle). Optionally keep also altitude channel active to have it support you keeping altitude, but don't forget to deactivate it if intending to descend or climb intentionally. Channels only = most stability in continuous flight profile, profile is defined by the use of the trim button. Helo will actively try to return to the exact defined setting. Channels with Flightdirector = stability augmentation during flexible flight regime, helo won't fight your inputs but use of trim button may help you keeping a momentary attitude. Leave the "trim button trims rudder pedals=on" for this module. It's realistic in this case, as the real Blackshark receives rudder trim at well und doesn't feature a spring loaded pedal setup or twist grip like our home cockpits.. Then of course, this all needs practicing. Hope this helps, good luck!

Thanks for the vid. Now I am struggling to keep interest in BS3...

You ask for the impossible. A 'regular' helicopter (whatever that is) is being trimmed constantly. If you don't like twhat the flight director in the Blackshark is doing after being turned either a) simply don't switch it off all the time or b) look up or check some yt videos how it's put to good use.

According to the manual p 6-107: Powering on the APU requires a power source and aft fuel pump on Just noticed I can shut the aft fuel pump off and still the APU keeps running. I can even restart the APU without any fuel pump switched on. Only requirement is an open APU shutoff valve. When I disconnect ground power and switch off batteries, a running APU instantly shuts down automatically. Manual claims the APU generates electrical power How can I verify the generated current? The electrical systems panel is not functional (p 6-98), unlike in all the other helos. On manual page 13-20, the APU is not even present in the electrical systems diagram, let alone as a source of power Why does the APU shutdown when all other power sources are disconnected? If the APU generates power, the disconnection of other sources wouldn't matter. The ABRIS needs AC to run. If I have a running APU with inverter on, ABRIS won't start. With batteries and inverter or DC ground power with inverter or switched off inverter with AC ground power, ABRIS starts. So whatever power the APU generates, it obviously doesn't feed into the electrical system. Is this correct? Ground power indication Manual on p 6-79, item 4: When DC ground power is on, lamp will be lit. In my Blackshark, this lamp only is lit when both switches, DC ground switch and AC ground switch, are on. If one of these is off, lamp will not light. As long as AC ground is off, DC ground on doesn't light the lamp. Special case: If batteries and the inverter are on, only the AC ground switch lights this lamp and the DC ground switch is ignored by it. Is this all so correct?

4. you are losing position lights after removing the pylons

according to this video by @Volk. it is exactly the way you stated.

I didn't compare at all and I think nobody did. I commented on a comment which implicated that U.S. gear would receive priority in DCS development. The answer is simple: Much more people around here are hyped for an Apache than for a BS3. These are interesting and agreeable facts you stated, but they totally missed the matter of the recent replies.

I would agree the U.S. prioritized development of the Apache way more than Russia did with the Black shark.

Sadly some people are so intolerant that even if you outright declare to not criticize somebody's motivation and just ask a neutral question showing interest for individual mindsets, they still have to lecture you about tolerance. What a mad world.

I could swear I had the landing light switch mapped in the controls settings, using 2 bindings 'switch up' and 'switch down'. Since it is a three stage switch in the cockpit, I could sequentially cycle up and down through all 3 positions. Today it doesn't work any longer, these bindings are gone as if they never were there. Only bindings available now seem to be 'control', 'off' and 'retract', so now I would have to map 3 inputs . I wouldn't rule out I only had this working in the Mi-8. The switch logic is the same there but it works with mapping only 2 cycling inputs there and in the Hind this is unavailable