Jump to content

B503

Members
 View Profile  See their activity

  • Posts

    14

  • Joined

  • Last visited

About B503

  • Birthday February 24

Personal Information

  • Flight Simulators
    DCS World/Falcon BMS
  • Location
    Japan
  • Interests
    Playing in fighter aircraft games

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. B503
    Rough looks but I think this is exact same issue happened in 2.7.7.14727 update. Missile doesn't get outrun, nor got dragged into chaff, nor getting notched, nor over-leading itself out. They just for some reason lost track possibly due to no correlation between range gate and velocity gate.
  2. B503
    Sorry for confusing you, but I know about HOJ mode. I wanted to mean, HOJ mode and burnthrough capability which is affected in worse way is cause of the "meme 14 thing" first. F-15C's case is just an example..
  3. B503
    Looks like thing is developing. We have to and only be able to just hope.hope.
  4. B503
    We may have ignored the important point. I currently only use F-15C and F-16CM so I don't know much about F-14A/B and F/A-18C. But I'm not sure F-16CM and F/A-18C has HOJ mode and burn through capability on radar(I think F-16CM don't have it afaik). This "Meme 14 thing" is possibly triggered by not only missile's API but also launching aircraft's radar modeling.
  5. B503
    Same thing happens to F-15C also even before this update. If you're shooting against jamming F-15C or F-14A/B, your missile doesn't go loft and just fly straight. Looks like this update heavily worsened 120/SD-10's CCM capability and seeker itself, and that's why the "meme 14 thing" happen. F-14's and heatblur shouldn't be blamed or made fun of.
  6. B503
    I found some interesting moment on GS server Tacview. In this one, this F-15C (possibly notch) dodged 120C from 4.5nm right behind, but missile shake itself at last moment just like re-acquired target or something. In this one, 120C almost went into ground and did sudden turn(I was recording this flight on game bar and reviewed it, in game F6 view it did 30+G turn all of a sudden) and managed to hit the targetted F/A-18C. Looks like new velocity gate thing made missile really sensitive against "notching movement" but not notch itself. If this velocity gate is the cause of the problem, the misses within 4-5 nm tail-on or head-on can also be explained. 4-5nm is somewhere close to the range which the 120 burn time ends, so 120 has so much increasing relative velocity against target in these moments. It may trigger seeker's velocity gate to think "It's false target" or something…basically, VGPO itself from target. P.S. If this thought is correct, I wonder why 120's pulse doppler seeker is affected only by velocity gate...is it overwriting seeker's range gate's information of something?
  7. B503
    That's explained. Fortunately, about the low to high shot WEZ is still around 8〜10nm. What mostly took a hit are co-alt and high to low. From my experience, even from over 30k ft high mach, 30nm is extremely lucky now if you hit due to the oscillation issue. Also in the high to low, it sometimes hits but hit rate is lower than previous due to the easier track drop. In overall I think it gets worsened. Some part like low to high barely stays close to the previous 120, but all the other part took hit hard.
  8. B503
    Not sure how you manage that. I haven't flown too much in public in the recent weeks, but for instance a few days ago 2 flights on GS with a Viper and 10 kills out of 12 AMRAAMs fired. I think both of you should tell about launch parameters. How long and how high? How is your speed??
  9. B503
    Looks like current 120's guidance logic is way too sensitive against targets movement. I got the same issue too in MP. When about to impact, missile oscillate itself possibly for over correction against target movement in relation to the missile itself. It makes this missile lose 100-200kt speed at over 30000ft(for this case before G counter jumps up from 1.3 to 14.3 at 1:28, AIM-120C got 1256kt TAS at 36945ft, impact speed at 1:29 is 1134kt TAS at 35274ft) right before the impact and sometimes almost make itself off the target.
  10. B503
    This "ECM effect" has already appeared before this active seeker update comes (In BVR, when launching on ECM active F-14, active seeking missile doesn't loft. But after burn-through range it lofts). And that update doesn't include any change on F-14's ECM. If this is actually ECM related matter, the thing needs to be changed is model of active seeker's burn-through capability and HOJ capability. Not the whatever aircraft's ECM model.
  11. B503
    What about Mirage at last part of this record? It's 4nm snapshot. Also, It's my personal opinion right now, but I don't think this Active seeker issue is onboard ECM related matter. If the onboard ECM is a problem, same thing should happen against F-15C like aircraft also. And as I searched around DCS movie on YouTube, looks like it also happens on F/A-18C. It's obviously not my video, but around 14:00 of his video, you can see 120C from within 7nm did some weird move too.
  12. B503
    Holy, it triggers my PTSD……I saw exact same thing happened in open PvP server.
  13. B503
    I'm not sure this picture can help you but only thing I can send now is this. This one is a screen cap of tacview, taken in one of the famous Open PvP server you may know. This was a launch from Over M1.1 within 8nm. As you can see from picture 1, the targeted F-14B is not in high energy state and not going for notch. Missile's sightline and Missile's flight pass is both far from 90° on F-14B's flight pass. But in picture 2, Missile for some reason lost track. and going into ground. It isn't defeated kinetically(Missile is over M2.0 and target was around M0.8-0.9, and target is not being cold from incoming Missile), nor dragged into chaff, nor falling down to the notch filter, targeted F-14B didn't even do a evasive turn. There is no possible reason to justify this Missile went away from the target. This is one of the case many of these people see, and the reason that being said "Current 120's and SD-10 has some issue".
  14. B503
    Pretty much same. Especially in deck, there's no more "Stern WEZ" and "Minimum Abort Range" for both variant of 120 and SD-10 in current version of DCS. Also 120's CCM capability is much lower and feels like notch window is now at least ±30° from complete notch. Not even capable for BVR to WVR.. Even more, new seeker code induces some oscillation in long range launch. I think this oscillation can be cured by introducing "Husky then Pitbull" feature, but I can't hope so much that ED is going to do it……
×
×
  • Create New...