Jump to content

DAZnBLAST

Members
  • Posts

    431
  • Joined

  • Last visited

Posts posted by DAZnBLAST

  1. Hello

     

    Just been messing around this evening with bullseye A2A waypoint and decided to lock the AWACS to test Bullseye BRA.

     

    Get this, AWACS flying away from me, shows up on radar page. I TDC over him and lock. I lose lock. He appears again, so I lock him again. I lose lock again etc etc. I change the rate at which blocks disappear from radar from 4 to 32. He appears. I lock and constant lock. I don't lose lock.

  2. The correct button for locking a specific brick is Sensor Select Right (AACQ) - if you use TDC depress and there are two bricks on the same azimuth separated by distance, you run the risk of locking up the wrong target (TDC depress just does a spotlight search and locks anything within 20 degrees of the TDC, AACQ when your TDC is over a brick will lock that specific brick).

     

    This is what I want the radar to perform like. Currently, place your TDC over a brick and radar, just goes and locks whatever it likes off to the right or left.

  3. I'm using the X56. Have tried realistic TDC checked and unchecked. The radar is doing some random locking. Try the 8 vs 8 and see for yourself. Noticed, the AIM120 is showing "LOST" right off the rail too, even with a diamond lock box.

  4. Has 2.5.6 broken A2A target locking? If a bandit is placed between the TDC cue and Sensor Control Right is pressed, it does it's own thing and finds a bandit 90nm away and ignores the bandit inside the TDC cue?

  5. Only flight engineers equiped with specific, often classified, data and knowledge can discuss 'about the BVR missiles high performance'.

     

    Opinions of other common folks, including me, without producer's or test energy charts and knowledge to interpret this data precisily and knowing all conditions of the test, is close to worthless - a strange mix of false expectations, wishful thinking and imagination.

     

    I admit some guys have something interesting to say but some with posts like

    "increase the range by xxx % because i feel it will be just accurate (with 0 mathematic proof)" or

    "in conditions X and range Y the missile should hit because i feel so (with zero mathematic proof)"

    Yea, for sure:music_whistling:

     

    If the 120B,C is modelled as correctly as can be at all altitudes etc, benchmark all other ED and partner A2A missiles accordingly, otherwise you have an arcade game and not a simulation. If you cannot benchmark said missiles, what are they doing in the 'simulation'?

  6. Thank you for tracks!

    Why do you think the AIM-120 is not correct?

    Let's not pay attention to the SD-10.

     

    Hello Chizh, You must pay attention to the; SD10, 530D etc etc. All missiles mentioned are incorporated into DCS, so must be (benchmarked) simulated accordingly. Otherwise what's the point? No good having a beautifully simulated AIM120B, C and an un-simulated SD10, 530D etc.

  7. When in TWS, press RAID and then press Undesignate to switch between targets, cancels the RAID view. Is that correct behaviour? Should it not stay in RAID view when switching between targets?

  8. Hello

     

    Is there a way to get the TGP in the F16 to behave like it does in the FA/18?

     

    Basically "-" and "=" keys zoom the TGP in and out when in A2G mode.

     

    The same keys above control radar elevation up and down when in A2A mode.

     

    Separated by mode and or SOI, this saves running out of POV hats on your HOTAS.

  9. But...The Hornet isn't further behind the Viper.

    The Hornet has;

    JDAMs

    JSOWs

    MAVs

    HARMs

    Harpoons

    Center pylon fuel tank

    exterior lights

    moving map

    IFF

    Jettison

    etc

     

    You guys have got to calm down a bit, the order of features coming on line is irrelevant.

     

    I think he is referring to TWS in isolation, not the airframe as a whole.

×
×
  • Create New...