Jump to content

Hulkbust44

Members
  • Posts

    1042
  • Joined

  • Last visited

Everything posted by Hulkbust44

  1. CBs in the Hornet don't necessarily "trip", they are used to deenergize or reset a certain electrical system.
  2. After start/before takeoff checks call for INS knob to IFA if GPS is available. Infact you get an advisory if you don't. P/INS on the ADV- line to tell you GPS is available but is not being used. null
  3. "Balance" being you primary concern is why this is a ridiculous notion. The Hornet is limited to 7.5G for the sake of the lifespan of the aircraft. The limiter can easily be outrun to 8G+ which would happen IRL too. (You can even see it in a few HUD videos) there would be nothing close detrimental that the aircraft would endure at such a minimal over G. Are there missing G effects? Sure. A/G stores would be damaged or ripped off at 5.5G+, targeting pod limit is somewhere around 7.8G. Now if ED dared to implement the same thing in the Viper, their would be riots. Difference is the -16 dosen't have a dynamic G limiter so in a simulation where you can't feel the G, you better be staring at the HUD or you're going to break something. While we're at it, at 8G+ simulate the pilot not being able to move their head.
  4. STEP + EXP seems to track better, but of course limits SA.
  5. On the EW side nothing would actually change so it would basically just be cosmetic
  6. Yeah the TD box should be less precise, but as I understand it would be more precise than the HTS initially, think TWS vs STT. The HARM seeker FOV is some 4x smaller than that of the the HTS. Correct me if I'm wrong, but an F-16 firing in "PB" at an HTS target that's just been detected would be terribly inaccurate compared to an F-16 using a HARM fired in HAS.You don't need triangulation to tell the HARM seeker to track a detected emitter. And in the Hornet, that emitter would've been processed by the ALR-67 and ASPJ helping the quick targeting process.
  7. @BIGNEWY Do you just need a reference for the IR marker? NFLIR Hardware in built into the pylon it's just a question of it it would be connected and activated or not.
  8. What functions you specifically need more info on? Some things missing are range known/unknown functions, land/sea select, PB target profiles, and HARM MSI trackfile creation and correlation, to name a few.
  9. There is nothing wrong with the Hornet TOO. Yeah it's too precise, but so is ever ED sensor. The "tables" are categorized differently in the Hornet where you can select a class to lessen the search time. However, the Hornet also has the ALR-67 and ASPJ contributing to tell CLC what to expect. So yeah the HTS is a more precise system overall, but the Hornet CLC puts it's way above a non-HTS Viper. Hornet has the ALR-67 and ALQ-165 that contribute, making "scans" a non factor when the other systems detect something. This is also how you have TOO emitters outside the HARM FOV.
  10. There is a delay for it, but not where you need to hold the trigger, that is a bug. @BIGNEWY Revisit this please. I'm pinging as it's the only way for someone to see a "correct as is" thread. At minimum the sidewinder being delayed can't be correct.
  11. It is absolutely functional. I just trimmed myself in to a constant 4G turn to test it.
  12. I found more relevant data, the PM will be in your inbox soon.
  13. If you just want pointing for the FLIR, use INR. If you're in SCENE or AUTO you would be in a targeting phase refining any initial designation. If a previous sensor made the designation, no action TDC slew should slew the FLIR in SCENE without designation until TDC depress. AUTO will take designation priority. No sensor should take a designation without positive TDC. action.
  14. That's not what they are talking about. It's a different AP nav function that at least was working. OVFLY and REF WP do work last I checked
  15. Cold? absolutely, here your target is at mach 1.1 Granted the LARs in DCS are too conservative last I checked.
  16. As per Changes since 15 May 2003, the SA format navigation data should be in white when displayed on the AMPCD. Lines, waypoints, nav target's etc should be in white. When COLOR on the Attk>DATA format is unboxed, all AMPCD format data should be displayed in white. @BIGNEWYPM coming later. white_text.trk
  17. As seen in the track, the radar contribution circle indicating that the radar is contributing to the displayed trackfile, is missing. In all search modes, and track modes, the circle never appears. For reference the circle in seen in the ED early access guide multiple times, but I haven't seen anything from ED about it. This is a crucial component of the A/A system for the Hornet. It's the radar contribution circle that will distinguish FLIR, HARM, L16, ASPJ, and CIT only onboard tracks from the tracks that have the radar as a contributing sensor. Knowing what sensor is building or helping the trackfile is critical to understanding how valid/accurate the data is. norcctrk.trk
  18. in SCENE and AUTO it will always try to keep that track. AUTO will even coast for a bit if looking at a moving target. Cycle to INR and undesignate if you just want to point it.
  19. Until we get the -210 we won't know for sure, but those numbers sound just fine, the -402 should be more efficient.
  20. It's what is stated in the radar manual, 742-100 I believe, and 600-100. Also rember the elevation scale is not always fixed, there's a option at OSB 11.
×
×
  • Create New...