Bricux

It's weird, @Wags marked Mk84AIR as ready in:

Dear ED Crew, It seems to me that the track is not necessary in this case. When sending via Link16 SPI or steerpoint in your description, they were supposed to appear as steerpoints from 71 to 80 at the recipient. Meanwhile, these steerpoints start at 500 for receiver plane. I kindly remind you of my previous topic which was marked as reported bug and closed some time ago.

AH64 Early access mission from Growling Sidewinder https://youtu.be/JhfD2gk1J-U

ED via Twitter https://t.co/8zHpwYHZDR

I have same joy as You and I don't have any issues in Viper and never had. As @BIGNEWY wrote without track its only a guessing.

When You are in CCIP mode TPOD looking (locked) in CCIP impact point.

@LetMePickThat that's why I wrote "From big Russian SAMs" I do not count SA-15 as big SAM like SA-6, SA-11 or SA-10. It's different class. Fact that SA-15 was designed especially for intercepting small objects like AGM88 etc. is true. And remember that first versions of SA-15 from '83 wasn't as effective as later M1, M2 versions.

I researched this topic for my Wing. From big Russian SAMs, "earliest" system that can successfully detect and fight with enemy missiles (smaller than cruise missiles, eg HARM) is SA-17 Buk-M1-2. With materials witch I found we can tell that SA-11 Buk-M1 (we have it in DCS) can't successfully detect and fight with objects HARM size (so AIM-120 also). If SA-11 can't, SA-6, SA-5, SA-3 and SA-2 can't either. About that parts of airplane compare size (RCS) of a wing witch fell of from a plane with eg size of AIM120 or AGM88.

Hi, I just want make a very, very gentle second bump on my topic from the Viper section with a small bug, however very useful feature that I reported 4 updates ago. With love to the entire ED team and of course the F16 itself.

For me in SA-2 test, missile firing range drop 20% for long pod compared to short. So I think there is a slight advantage of long one.

When You uncage TGP, You're turning laser search mode.

In HAD You can create custom threat table (with 8 emitters?) via ICP/DED

I brought up this topic in another section. In general, different bands are for different radar bands (types eg. AA, AG). But I guess this is for future usage when electrical warfare comes up to DCS. Now we're starting with ECM POD and first band activated, so I guess that now only first band is functional.

And what about these ECM band buttons? Somebody have any description of which bands are now usable and what is FRM, SPL (I guess self protection jammer)

So it's about way of doppler radar works? If tracked object travels at same speed as emitter there is no doppler effect.

@FuY Isn't that all about radar filtering slow objects approx. <20knts speed difference (closure rate, Zero Doppler Filter)? Notice that in F16 video You're attacking target that flying in same direction as You (so Zero Filter cutting it at the beginning, later You develop speed and we can see 60~70knts speed diff when You can lock it). In F18 vid You're attacking TRGT that flying opposite direction (we can see closure rate of 270~300knts) so You can lock it w/o any problem. Remember that, if You chasing another plane with minimum closure rate (speed difference below ~20 knots) You won't see it in any radar because of Zero Doppler Filter. That's why we're using also FOX-3s You can not always rely on radar. https://www.youtube.com/watch?v=N8Z3ta1v1po

Here we have Lockheed Martin F16V simulator. Guy attacking some air targets and we can see "hat" above J symbol. Of course it is newer RWR and Viper version but this is some clue. https://youtu.be/Bt4YKaeyX44?t=291 In addition we have A10 and Harrier witch have identical RWR symbols but with "hats" for aerial targets. Even F18 with little bit different way of displaying RWR have "hats".

@Frederf You have insane amount of knowledge about this bird, do You have any infos about this topic?

But pressing MARK shouldn't cause changing SOI (even if that screen is not displayed e.g. AGR). And problem is when You change SOI when MARK DED page is displayed, causing setting HUD as SOI even if TMS DOWN was used.

For external MFD screens useres during night flights, we need it LESS BRIGHT

Dear ED Crew, There is a problem with how the creation of a new Markpoint works. When press ICP 7, MARK DED menu appears. Default sensor for MARK is HUD, while pressing ICP 7, even when you have another SOI, MARK causes to set HUD as your SOI. In my mind MARK shouldn't ever have HUD as default SOI because it making HUD as SOI. Examples: 1. Plane in NAV mode. Left MFD AA RDR, Right MFD HSD. Left MFD (AA RDR) is SOI. Pressing ICP 7 MARK causing to set HUD as SOI for MARK and RDR set in AGR mode, and HUD as SOI generally. It's bad. (Doesn't appear in Plane AA mode [MARK default setting is OFLY]). 2. Plane in AG mode. Left MFD AG RDR, Right MFD TGP. Left MFD (AG RDR no lock) is SOI. Pressing ICP 7 MARK causing to set HUD as SOI for MARK and RDR set in AGR mode, and HUD as SOI generally. (Doesn't appear when You lock SPI in AG RDR). It's bad. 3. Plane in AG mode. Left MFD AG RDR, Right MFD TGP. Right MFD (TGP no lock) is SOI. Pressing ICP 7 MARK causing to set TGP as SOI for MARK. It's good! 4. Plane in AG mode. Left MFD HAD, Right MFD TGP. Left MFD (HAD) is SOI. Pressing ICP 7 MARK causing to set HUD as SOI for MARK, and HUD as SOI generally. It's bad. 5. Plane in AG mode. Left MFD HAD, Right MFD TGP. Right MFD (TGP) is SOI. Pressing ICP 7 MARK causing to set TGP as SOI for MARK. It's good! BUT! You create new MARK, and You try to TMS DOWN to switch SOI (to unlock HAD, w/o closing DED MARK page) causing to set TGP as SOI for MARK, and HUD as SOI, causing TGP to crazy. Generally You can' switch SOI from TGP to HAD with MARK DED page open. MRK_HUD_BUG.trk Post scriptum: when MARK set Your HUD as SOI every weapon switch to VIS mode. What it's generally good but not with this problem described above.

@Hobel +1

In GMT it is adjustable by OSB16 and OSB17 described as MAP. It's that because in GMT we are adjusting background (map) gain not moving targets detection gain.

Once I made simulation. I created a mission with steerpoint (as HARM designated steerpoint) and placed radars in different distances from steerpoint (radius). Sorry for visualization in CAD but it's only what have in workplace So I placed SA-19 in 25nm radius from steerpoint (one emitter for each test), then launched HARM in RUK/PB/EOM (one after another). My conclusion was that: Every HARM RUK/PB/EOM tracked every target and tried to fly to the target, Every PB/EOM HARM tracked and striked every target (notice that steerpoint in center of the circle is beyond SA-19 radar range), RUK HARM flies to target but fall short due to lack of kinetics or battery life, Every HARM, after lunch, flies straight. Then turns to detected threat [turns earlier on bigger emitter (S) and later for smaller (SA-19)]. So honestly I don't see any difference of footprints for RUK/PB/EOM. (For my test max. radius was 25nm, next I tried 27nm but it was too much and rockets do not track). In HAD we can see difference in range between RUK and PB/EOM, and difference between launch parameters between EOM/PB (PB have narrow launch angle). I don't think so it is exactly mode footprint but rather like range coupled with launch parameters.

@Duervol thank You for patience. I check Your track and made my own test. At first my results. HARM seeker do not depend on Your plane RWR. I shoot to SA-19 from 60nm (both PD and EOM), radar have any chance to see me, and in both tests rockets hit. Now Your track. Firstly I watch it, later played on my own. At first I noticed that You launched Your HARM from very short distance. So I assume that your first rocket, just stop to loft and then steer itself to the target. Second one, even don't finished lofting and already pass by Your steerpoint. Later I played Your mission, just fired HARM from greater distance and it work well. Next I tested even closer range, shoot 2 rocket (PB and EOM). Both fly above target, turn back and attack radar from the back. So my conclusion is that HARM in EOM/PB have like couple phases of flight. 1 - launch; 2 - lofting with rocket motor; 3 - lofting w/o rocket motor; 4 - INS guiding; 5 - seeker guiding. In this case Your rockets, have no time to stop lofting and start guidance. Your attack distance is so short that rocket must like turn back to the target. I think better mode for this situation will be RUK (loft rocket little bit by Your plane and shoot). In my test rocket hit hypersonic with rocket motor on. Thanks