Jump to content

Zergburger

Members
  • Posts

    145
  • Joined

  • Last visited

Posts posted by Zergburger

  1. On 9/13/2021 at 5:37 AM, LJQCN101 said:

    In -1 section 6 Flight Characteristics, Landing Configuration, there're two described techniques that you can use to land a Viper.

     

    One is the 11 deg technique: stick for attitude and throttle for AOA. The reasoning behind is that the FLCS Take-off & Landing Gains is a pitch-rate command system until 10 deg AOA, which means your stick is commanding pitch-rate, instead of G or AOA. A zero stick input will translate to a zero pitch-rate, regardless whether your aircraft is inverted, decelerating or accelerating. This technique allows better pitch control.

     

    Another technique is to trim for 13 deg AOA: stick for AOA and throttle for glidepath. When flying above 10 deg AOA, the FLCS starts to add nose-down command to your stick input, a negative pitch-rate command proportional to (AOA - 10). It's called a blended pitch-rate and AOA command system. 

     

    When you manually trimmed to 13 deg AOA, you're essentially commanding a positive pitch-rate, while at the same time the FLCS is commanding negative pitch-rate proportional to (AOA - 10). What's happening is that the aircraft will now tend to hold the trimmed AOA. Adjusting the throttle will now pitch the nose up and down. This type of approach primarily allows better control of touchdown point and more efficient energy dissipation, but less stable in gusty wind conditions.

    Maybe I am struggling to understand what this means in terms of the aircraft's characteristics....

    But, shouldn't the nose stay parked where we put it with L/G gains and AoA < 10 ?

     

    I am further confused by the reports that with weight on wheels this 0-pitchrate behavior still applies,
    AKA when I am on takeoff roll and i park my nose 9 degrees high it should stay there, correct?

    same with landing rolls?

  2. On 9/8/2021 at 3:44 PM, Florence201 said:

    IDM is not TADIL associated. It was an early 9L type CAS and EW data transmission. 
     

    Link 11 was originally HF for Naval vessels but then terminals were put on larger aircraft 

    IDM simulation would give me the warm fuzzies

  3. On 9/10/2020 at 2:54 PM, Frederf said:

    v7 doc is calls it TTS. Yeah, that's SAM MANUAL. SAM AUTO is when the cursor are stuck to the bug (or more exactly just above it). That's the only way to get two tracks in SAM is to unstick the cursor from the bug and go and designate the secondary. DCS might have TTS but you could never enter it because you have to use manual SAM to enter it and there's no manual SAM yet.

     

    In the you-know-who sim you go between the two SAM modes by cursor input. The bug is "sticky" and the cursor snaps to it but enough input and it breaks free. This sticky behavior is described in any real manuals though. All it says is that cursor or antenna elevation input causes the search volume to be independent. There is no mention made of how to go back to AUTO. Maybe it's just slew over and let the stickiness take over or maybe you have to TMS up on it again.

    with dual target track being implemented perhaps we can hope for the dynamic scan volume that SAM is supposed to carry

  4. On 7/24/2021 at 9:31 AM, Breakshot said:

    The infamous roll miss in DCS MP can be attributed to the desync warp that happens when an aircraft exceeds a certain roll rate for a sustained amount of time. This is likely the cause of missiles missing due to "roll".

     

    To be honest, in the Flankers it is hardly possible to reach that roll rate, hence doing rolls against missiles is a fruitless affair 99% of the time and would result in certain death. It is however sometimes possible to defeat a close range shot that way due to aiming error inherent for every missile. 120 suffers the LEAST of the missiles in this respect. Try that against say an ER or others and they would miss more often.

     

    Instead of tweaking the 120 to be a death-ray in all scenarios, rather ED should look into netcode and desync improvements, IMHO.

    thanks for the op-ed.... but this is a bug report.

  5. On 4/30/2021 at 5:11 AM, deadpool said:

     

    You don't need to. Apparently the AGM-88C serves as one in the hornet. Physical criteria like antenna aperture size vs. frequency and range into the wind. 

     

    all sarcasm aside, still waiting for word from ED

  6. On 4/28/2021 at 12:09 PM, CAPT_Kirkpatrick said:

    Knowledge passed on from a friend who is much more knowledgeable than myself:

    Active countermeasures: Sites keep their radars off and rely upon a central search radar to acquire the target (IADS)

    They first turn on smaller decoy radars to try to bait a HARM/ARM shot on those rather than the main tracking radar, which comes on shortly after

    And as said above, just shooting the missile down

    Passive, Sidelobe reflectors: Some tech that uses Radio waves in the same frequency band to cancel out emissions to the side of the main array or passive structures that just reflect the emitted wave itself, making it harder if not impossible to shoot at the site unless its targeting/looking directly at you. This also harms use of ELINT like a HTS as you cannot triangulate an accurate position easily without being the one they are firing upon/in the bleed through.

    never heard of decoy radars, i know one of the lesser talked about benefits of AESA is the small sidelobes and backlobes when compared to mechanical or even PESA systems. when you talk about sidelobe reflectors, are you talking about a physical device used to bounce sidelobes? wouldn't that mess with the automatic gain functions?

  7. 13 hours ago, mvsgas said:

    Target Isolation (TI) and Geographical Specificity (GS) are not POS sub modes and will vary depending on the missile. TI should only apply to block III, IIIA, IV and V (missile block, not aircraft). Block IIIA and V will have additional options and different settings. Further more, TI is only available to some missile and not all (meaning some missile of the same block may not support the feature). GS is available only on IIIA and V.

    This setting affect the behavior of the missile and if ED does not plan to implement those behaviors on the missiles, this options are irrelevant for us as players.

     

    yeah i wasn't implying they were submodes of POS.
    I was asking about these other settings/features since they play a much bigger role when using POS modes with long range and long time-of-flight on inertial guidance. Also, with the upcoming HTS pod these features will play an even bigger role.

     

    All AGM-88Cs started on block IV software, with block V being fielded 1999 time frame. If this is a 2005 viper it stands a good chance we are using AGM-88C with blockk V software. so... stands to reason we could get these.

  8. I will try and ask my wingmen for their tracks, otherwise it will probably be a week before we run the mission again.

     

    If you view the ACMI file you will see the harms obviously misguiding. although i know you can't extrapolate causal factors, at least you will be able to verify that it's a true bug.

     

    EDIT: attached is server track

    server-20210419-185857.trk

  9. (apologies if this should've been posted in weapons section instead of FA-18)

    Flew a mission tonight that had 3x SA-2 sites in a line 20-miles apart perpendicular to the vector of attack. Behind these sites were a pair of SA-6 sites 6-miles apart.

     

    ALL SAM SITES HAD WAYPOINTS DIRECTLY ON TOP OF THEIR RADAR SITES.

     

    Using HARM PB (A/C Pullup) we had 3 separate hornets prosecuting the Fan Songs at the same time, all hornets engages from ~30k MSL at around 30 miles. The HARM from the center aircraft made a hard turn (~50 degrees azimuth) off the rail and went for the righthand most SA-2 site, which he had not designated nor was he facing.

     

    The SA-6 prosecution did not fair any better. with 2 hornets designated on separate sites; the first HARM guided on the correct site, but the second HARM fired by the other hornet decided to guide on the wrong SA-6 radar, then switched to the correct site after the one it was targeting was destroyed. Cool to see flex-logic working, sad to see it working when there's a large bug in the mix.

     

    Attached is a zipped ACMI of the shots

    Trackfile too large to attach, google drive link included: https://drive.google.com/file/d/1KBvV5mbKeb8kevJLNKnt41PitKY_r9i0/view?usp=sharing

    Bugged HARM PBclipped.zip

×
×
  • Create New...