Jump to content

dundun92

Members
  • Posts

    1314
  • Joined

  • Last visited

Everything posted by dundun92

  1. and yet ED has said the opposite. And when you look at polls on, say, hoggit, or even on these forums about ratios of A2A players to A2G/Multirole, you will immediately see why a dedicated A2A fighter, while IMO would be a great addition and would be rather popular, will not outsell a multirole such as the F-16/18 or F-15E. They can do it, theyve stated in the past that they have the documentation, and at one point way back afaik they were going for it. TBF, its not like ED, until this recent interview, has said outright they wouldnt do it. Wags himself commented at one point a year or two back that theyd "consider" a FF F-15C after the F-16 is finished, which appears to no longer be in the plans, but the point being, ED really has never ruled it out until recently. AKA, this looks like a marketing issue, and it makes sense.
  2. Its the AIM-54 desync issue. If you looked at that clients replay youll find that it guided normally.
  3. Granted you wouldnt, and thats fine. To each their own. But im not sure the majority of DCS players would say the same. Personally, I find AMRAAM BVR to be rather interesting in a coordinated NvN (e,g 2v2, 4v4, 6v6 etc), but thats just me. But I think we all know that something like a Su-35 would sell really well
  4. Yep, according to this paper the V9 range is 38nm vs 1m^2: Factor in that the V9 had a claimed 33% improvement in detection range over the V5, and using 5m^2 target, you get a 43nm detection range vs 5m^2 for the V5. Thats considerably less than in DCS, where youd be detecting a 5m2 at 65+nm.
  5. @Kev2go I think that was a reference to how badly over performing the DCS F-16/18 radars are. APG-68 should not use HPRF in RWS/TWS (only in VS), yet it does and has nearly double the detection range it should because of it; the DCS APG-73 radar is better performing than the much newer and more powerful PESA N011M Bars IRL. The RL APG-73 was said to have less range that the AMRAAM, as in AMRAAM range was outside max radar range; even using Rmax, this is nowhere near the case in DCS.
  6. Su-27 yes (not that it really matters thb though), but in the F-16 im using the built in CM programmer. And that ET, yea thats what happens firing by forcing LA too far off boresight :P.
  7. nope, just 5 sec memory mode, nothing particularly wrong either.
  8. Cockpit Visual Recon perhaps?
  9. OK this is way OT but for the record, a) it has been fixed for almost a year now, and b) this wasnt just an AMRAAM bug. ALL ARH was affected (R-77, SD-10, AIM-54 etc).
  10. They dont in DCS Nope, its super easy to chaff AMRAAMs in MP:
  11. Alamo 1-1 | dundun92 - Blue - F-16C or J-11A BTW, im assuming nukes are banned?
  12. Also, to add, spotting at 12km, even 20+kmn isnt particularly hard if you are expecting a threat since ED added the small dot labels a few weeks ago.
  13. As a TLDR, for missiles on the old chaff model, ECM tends to increase missile Pk. This is especially noticable on SARH missiles, as now notching the carrier doesnt work, itll just HOJ. But it doesnt have any direct effect on chaff afaik. For missiles on the new chaff model (AIM-120/SD-10), its a bit undecided. Ive seen tests showing a decrease in Pk, but this was from before the reduction in ccm resistance. From the tests ive done recently, ECM means that a chaffed missile can still reacquire. So again, increase in Pk. So overall for A2A ECM is pretty useless in terms of defeating missiles.
  14. The patchnotes indicate that only the AIM-120 (and SD-10 since it uses the AIM-120 scheme) uses the new chaff model, AIM-54 used to but HB reverted to the old chaff model. So anything but an AMRAAM/SD-10 works fine, the R-77 would probably be the best to test though, since stuff like the SARH chaff bug arent factored in
  15. @Arctic Foxgreat find, have you tested this with a freind in MP? SP ccm resistance has been wonky for a while, but MP ccm is different from SP ccm for some reason. Also, hace you tested this with any missiles on the old chaff model (ER, R-77, etc), so we can rule out this being simply due to the new chaff model?
  16. The ccm_k0s are a bit misleading rn, as the missiles are using different chaff models. AMRAAM/SD-10 (maybe sparrow?) are on the new chaff model, while all the others are on the old model, so you cant really compare ccm_k0s across the board. And the AIM-120B/C do have CCM_k0s, theyre in the missiles_table.lua. Its
  17. pretty sure its not AI, but rather SP vs MP.
  18. AT this point, you just pretty much have to accept that we are gonna be dealing with chaff-loving missiles for some time, at least until EW gets overhauled
  19. or maybe it just takes more than a week to fix considering their workload
  20. I mean, you could just not lock F-18s outside 22nm, solves the "issue" of his jammer, and why do you need to blink ECM anyway? (not defending the 15sec timer, it does need to go, but the way ECM is handled also needs to be changed as well). Why not just leave ECM on all the time?. Like personally from my experience flying the F-15 and Flanker, I never need to blink ECM unless i was trying to reproduce missile exploits like the current one. Just turn it on before engagment, then turn off if I need to notch.
  21. You could technically, yes
  22. Indirectly, as the missile is hardcoded to go active at 15km. So just see when the missile-target distance hits 15km
  23. ive gotten 50+km ER and ET kills on PvP, apparently people think you can just out crank a 50nm ER from 12km M1.2
×
×
  • Create New...