Jump to content

KlarSnow

Members
  • Posts

    561
  • Joined

  • Last visited

  • Days Won

    4

Community Answers

  1. KlarSnow's post in JTIDS or FDL was marked as the answer   
    JTIDS and FDL are exactly the same in a mid 2000's context. If they are modelling Link-16 in an F-15C in the Mid-2000's it doesn't matter what they call it JTIDS/FDL/MIDS, its all the same capability and functionality on the Link-16 network. I sincerely doubt they are modelling the mid 90's JTIDS and if they are any of the limitations it would have (still Link-16 remember) wouldn't be relevant to how DCS does Link-16, or TNDL since that's what they are calling it now.
    the Knob in the cockpit is Still labelled JTIDS to this day (just like in the F-15E btw that you can see in DCS), and several of the MFD options reference JTIDS, regardless of what terminal is actually in the jet. Its still all Link-16 and can talk to and do all the same messages as any other jet, with all the same track display and reporting and link capability.
    Basically this is a non issue, if its a mid-2000's jet its going to be link-16 compatible whatever they end up calling it, and there wont be any difference between JTIDS/FDL/MIDS in DCS because that level of detail is well out of scope, and wouldn't really matter anyways since even if it was modelled, everything would still be able to talk to each other and display all of the data appropriately.
    If they said it was a "Mid-90s jet with JTIDS" then maybe you should be concerned it was whatever that small experimental group of jets was, but if its mid-2000's as they have stated its a non issue. The terminology FDL/MIDS/JTIDS is interchangeable once Link-16 becomes standard in the early 2000's. What specific radio you have in the jet does not affect your ability to get on the link and transfer information in any meaningful way that could be represented in DCS.
  2. KlarSnow's post in MK-84 2000lb LD bomb missing from inboard wing pylons 2 and 8 was marked as the answer   
    Mk-84 LD's are not approved on the inboard pylons, the fins and tail kit are too long and interfere with the landing gear doors. This is correct per approved loadouts in the F-4E-1 and talking with SME's. If you look at the external view you can see that GBU-10 and Mk-84 AIR are both significantly shorter length wise than the Mk-84 LD. They do not interfere with the gear doors.
     
     
  3. KlarSnow's post in TDOA was marked as the answer   
    You should go look up the principles behind TDOA, TDOA is Time difference of Arrival, not angular measurements. Each station is receiving and synchronizing the time of arrival of a particular signal and using that time sync to generate a location. With 1 station all you get is a range, thus a circle around your aircraft. 2 stations would give you a pair of potential locations, and 3 stations gives you a very accurate location.
    This does not work the same way as angle based triangulation systems.
     
    Each intersection of a circle is the potential location of the target, only where all three intersect is the true location.

  4. KlarSnow's post in CDIP uses tgt point designation elev data. BUG was marked as the answer   
    This is accurate and not a bug. If there is no active sensor providing the height above target then the CDIP calculation pulls the current designation or closest steerpoint elevation and uses that.
    Suite 4 as implemented does not have DTED tied into its bombing calculations.
    Your only sources right now for height above target are SYS, wwhich isaircraft barometric or GPS corrected altitude compared to the steerpoint elevation. Or LAS which is the target pod latched to the CDIP reticle with the laser firing. The other parts of the height above target hierarchy: Air to ground radar ranging, Radar altimeter, HRM and Passive are not implemented. of those, only Radar altimeter an Air to ground radar ranging would help with CDIP bombing.
  5. KlarSnow's post in How to designate OFFSET target? Bug I suppose? was marked as the answer   
    designating an offset designates the target. Offsets are not additional targets they are offsets. When you have TGT cursor function and designate with an offset in PB17, it will designate the target point associated with the offset at the bearing and range from the offset that was saved.
    The behavior you are seeing is correct.
  6. KlarSnow's post in The 25000 feet limit on the LANTIRN tgp was marked as the answer   
    No, its automatic and part of the pods safety features so it doesn't damage itself.
    SNIPER has no limitation like this, so whenever it arrives you will be able to use it at whatever altitude you desire.
  7. KlarSnow's post in AIM-120C Seems to defy laws of physics - low/no drag and impossible turn rates was marked as the answer   
    Here 
    1
    l
    2

    3

    4

    5

    Tacview HUD view of the missile in question during the time period in question. It is falling, its pitch angle is decreasing, so it MUST accelerate.
  8. KlarSnow's post in AIM-120 maximum guidance time was marked as the answer   
    80 seconds for both versions of the AMRAAM
     
×
×
  • Create New...