Jump to content

Muchocracker

ED Closed Beta Testers Team
  • Posts

    792
  • Joined

  • Last visited

Everything posted by Muchocracker

  1. waypoint is likely not exactly at the altitude of the bridge. It "looks" like the pod is drifting but it's actually just rotating along a point above your intended target.
  2. semi-stable trackfile built at 77nm in 4/40 HPRF.
  3. Collect a trackfile that demonstrates the issue and post it.
  4. Cant't really help you if you don't give us trackfiles showing what you're running into. Check your scan volume in azimuth and elevation to make sure the target is within the frame. Reduce the azimuth setting to decrease the frame time and get more hits to build trackfiles at long range. And use the correct PRF for the target's aspect. I use the radar mutliple times a week and have no problems detecting and tracking fighters at +60nm.
  5. It absolutely does. For DPCA and thus STAP to work. It requires many different receiver channels (commonly done at every single antenna element) and digital beam forming to process and filter the main lobe clutter by weighting normalized dopper and look angle. Thus requiring a phased array antenna. The difference is the SU-27's IRST is not a fully integrated sensor into a unified trackfile processing architecture. It can't use it in the same way the F-35 can.
  6. EOTS, DAS, RWR, and MADL donations all contribute weapons quality track data to its closed loop sensor fusion
  7. I think you misunderstand how these fuses work -The Mk-339 is a mechanical time clock fuse that functions based on time from release. PRI and OPT are just 2 different timing sets that can be chosen. -The FMU-140 is a radar altimeter proximity fuse with a secondary time of function. VT1 is rad alt, VT2 is time function. Your problem is not with the accuracy, your problem is with their spread. Which you can change by editing the fuse settings to either burst lower (VT1) or by setting a longer function/release them lower. Not comaprable weapons in the slightest. The 97 and 105 are sensor fused weapons with heat seeking submunitions, of course they're going to be more effective. The 99 and rockeye are not designed for killing heavy armor.
  8. This is evidently not true anymore considering the update some months ago that allows it to reach upwards of 60 AoA now.
  9. And that's what makes it so powerful.
  10. It's still very much an issue with AESA's, no radar is immune to main lobe clutter. But being a phased array it's afforded some advanced processing algorithms that you can't get with mechnical types. Space Time Adaptive Processing as i understand through the limited reading i've done on it significantly reduces the minimum detectable velocity around the main lobe clutter. (makes the notch window extremely tight) Can't really just do that either, By scanning at very high rates you cut your dwell times significantly. That reduces the amount of pulses on target, and reduces integration gains. It would be a huge step back in the radar simulation in doing so.
  11. What is ED's information. Because there is zero documentation of the amraam's TDD on the internet. I can't even find out what designation it has
  12. TEF and Aileron scheduling in HALF and FULL flaps configuration has been a problem for ages. Best practice is to drop to HALF below 200 knots. Then select FULL at 160 and lower. It'll stop the ballooning.
  13. post a track
  14. They show as unknown if there is no offboard correlation.
  15. just because the radar works out to that range, doesn't mean it's actually tracking and shooting you from that range.
  16. only if you're using Pre-Planned with the manual lat-long input. It doesn't care about the jet's current selected format in TOO
  17. Yeah i dont ever remember it working for SRS I balance my pri and aux to full left/right to know which radio i'm transmitting on.
  18. could be a control gain issue, entirely speculation on my part tho. I havent looked at the files for it or know how they schemed the autopilot/guidance.
  19. 6 years ago bro
  20. When you make the handoff to the selected JDAM that information stays on your HUD as it's the steering release cues for that bomb. When you undesignate you're removing the aircraft's designation. They are 2 separate things but they're going to share some symbologies. to remove all of it you have to switch to a JDAM with no handoff information, deselect jdam's, or hit the erase jdam option to wipe the info. To update the handoff information on the bomb you have to do another handoff. Which is by TDC depress, or by creating a new designation.
  21. As it says. It is the transmit power of the MIDS terminal
  22. You have to designate and step to the next station and designate for the first 4. Which will input into TOO1 with no additional work. You then have to switch to TOO2 and designate, switch stations and select TOO2 then designate for all 4 stations. Then when you drop. You pickle the first 4. Then on the 5th swap to the OTHER TOO preset, pickle, then do the same thing for the other 3 stations.
  23. Yes. That is what the jet should be doing
  24. That is the DUD cues being bugged and i believe has been reported previously, and it's a problem with a bunch of weapons. The SMS gets told what the timings are when the weapons codes are loaded by the ordinance handlers.
  25. You don't have to. The Bombing computer accounts for it in both CCIP and AUTO.
×
×
  • Create New...