Jump to content

NeedzWD40

Members
  • Posts

    592
  • Joined

  • Last visited

Everything posted by NeedzWD40

  1. @Amarok_73 has done a good job of explaining the why, but I'll try and answer as well. The PRIMARY box under the PRESET EDIT menu is only an indication as to what the primary radio is for that preset. It simply highlights the radio, frequency, settings, plus puts an arrow next to it. It's for a quick at-a-glance overview of the preset for awareness/coordination. Suffice to say that it's entirely contextual in how/why this functionality is used, and normally in much busier commo environments than we simulate in DCS. In here, I've edited my first preset to be called A-CHAN and the callsign to be ACH. In addition, I've replaced all the frequencies with custom ones. The PRIMARY is still VHF for that preset, thus VHF is highlighted and arrowed. However, I've gone through the top row for each radio and tuned them to the frequency in the preset, which is indicated under the left side with V U 1 2 H. This all means that right now, all my radios are tuned to the first preset as indicated. Unless I tune the radios differently (EUFD, COM preset, COM manual setting), they'll stay on that frequency until changed -- there's no deleting of a radio from a preset. This is entirely an organizational thing: Instead of PRESET 1 I might instead call it BDE HQ, whereupon the frequencies preset are all the available frequencies that brigade headquarters is on, but the primary might be the VHF radio. I might have PRESET 2 as my inter-flight frequencies, where FM1 is the primary radio used, and so on. The idea is that instead of punching in numbers to tune radios each time, you simply select a preset for a known party (ie JTAC), select their primary radio, then select the appropriate mode. This applies whether you're speaking of datalinks or commo. The PRIMARY just makes a fancy highlight so you don't end up calling Juan's Taco Joint for a fire mission because you selected FM2 instead of FM1. The second half is the EUFD, where the DL rocker comes into play. All five radios can be used for the datalink and each crewmember can independently select a radio for the datalink. Your crewstation is an open box indicator, while the other crewstation is a diamond. For example, the pilot can use the VHF radio to send a datalink message to brigade, while the gunner can use FM1 to send a datalink target to nearby flight members. TL;DR: Presets are just a way to tune radios for both commo and datalink. Select your preset, select your radio, select mode at the bottom, and voila: radio tuned to that frequency. Use EUFD DL rocker to select radio for datalink, RTS to select for commo.
  2. HF > VHF > UHF > FM1 > FM2 is generally the order of performance between the radios. The FMs should have virtually no NLOS capability, much shorter range compared to the others. I haven't done any detailed testing in DCS (lack of players in my group with thorough AH-64 experience makes this difficult), but generally I find the VHF performance to be ideal. The HF should give the most range and have an NLOS capability, but I want to say the HF is only good for specific, narrow data types. The FMs on the other hand should have the most data type compatibility. As we're really only concerned with sending data between AH-64s, VHF and UHF should be the go-to, followed by FM if range and LOS requirements are met. Generally speaking, the FMs should be adequate for most tactical situations involving target data, etc. but I've no idea what usage conditions or expectations are for the datalink.
  3. To my knowledge, all the audio files are encrypted, so customization/replacement isn't possible.
  4. After he receives your targets, he should be able to sight select the FCR after receiving the targets. This should enable him to engage with AGM-114L if available or set his ACQ source to FCR for slaving. You can send individual points via the TSD's POINT submenu with the XMIT function.
  5. We're only trying to help. Oftentimes the solution can be incredibly simple, thus the dumb questions. You can record a quick track and use that to report the issue, as frustrating as it is.
  6. Can you post an image of how it looks when you boresight from the front?
  7. Do you have the same problem with a hot start aircraft without boresighting?
  8. He should lase during the last few seconds before impact. When I last used him this way, I had him acquire the target before doing anything else. I'll have to (painfully) test again to see if he still works that way. Did I mention how painful I find George to use?
  9. Don't think this applies right now. You can have 3 points in the database and delete them to clear it out entirely.
  10. That would be correct then, should be RFHO > Sight select FCR.
  11. I haven't tested if it's implemented yet, but certain datalink functions like RFHO should include sight selecting the FCR, even if it's not present.
  12. To expand upon this: moving target with LOBL will arc straight toward the target, static target LOAL will curve left or right, <2.5km will be LOBL with a small arc. Missile maximum altitude is based upon launch altitude, ie if you're at 5,000ft, the missile climbs above that reference altitude.
  13. The baseline JTAC is persnickety, you need to call out "IN" before you make your attack, or he'll call out abort. He'll also call out abort if you're not in the right direction. Basically, until he says "CLEARED HOT" you can't make an attack.
  14. Kodori Gambit and Battle for Saipan don't have all weapons available from the FARP warehouse (you can see this in the rearm menu when it says "not available"). If you check the Marianas Runway Start instant action mission, you'll see it available on the arming screen. There didn't appear to be any restrictions in any of the instant action missions that I tested. I was however able to add the MMA via the mission planner, both to the warehouse and to my starting payload.
  15. TSD > UTIL > INU1/2 reset. It takes ~4 minutes to reset an INU, so keep that in mind. Reset one INU so it'll be ready for action, then after it's back up, reset the other one. I just generally cycle them in 10 minute intervals to keep drift in check, which is about 5m a minute.
  16. Try resetting your INUs a few minutes before you're in place to engage. There's currently an excessive INU drift glitch that isn't being corrected by GPS (and it's very hard to document with a short track), which is feeding bad data to the missile. Easiest way to see this is to use the STORE function with TADS and observe how far off the generated point is from the actual crosshairs.
  17. RFHO is sending targets via datalink to other aircraft. It allows the FCR equipped aircraft to find targets and send them back without exposing the other flight members. This would be the true masked capability for the aircraft, as it would be possible for one aircraft to scan, prioritize, amortize, and assign targets to the other flight members, then execute a rapid engagement from concealment and/or cover. Without that, you could unmask, scan, then mask and fire as a single ship, provided ideal circumstances.
  18. 2500m isn't a limit, it just means it's too close for the missile to do DBS. You can get LOBL further out, but the target has to be moving. LOBL Inhibit would be used if you wanted the missile to always use DBS (where possible) and projected target position. Ie you have one static target and multiple moving targets nearby and you want the static target to take priority (with the understanding the missile still may acquire one of the moving targets). Long, complicated subject short: the missile itself has several ways of acquiring targets and the information passed from the aircraft to the missile is same/similar data, whether it comes from the FCR, TADS, or RFHO. Main use case for TADS with a 114L is being able to reach out further for static targets, plus VID of the chosen target. We'll have the ability to link TADS to the FCR (and vice versa) in the future, but if your TADS is already there then you can just laze and fire.
  19. Currently, if you equip the TARPS, you can't put anything other than the ECA and ALQ-167 on the pallets in front. However, there's documentation of loading and utilization of dropped ordnance with the pod: https://theaviationgeekclub.com/the-story-of-the-us-navy-tarps-equipped-f-14-tomcat-that-took-a-photo-of-its-own-gbu-12-heading-for-its-target/ I'm not certain if this means a basic A or B should have the capability or if it was restricted to the B(U) and D, but I wanted to bring this up to see if anyone had more information on the subject. If it's not a restriction that should be imposed with bombs, then perhaps we could have it changed?
  20. You can also press the right pedal inward and move the cyclic around, which seems to cure the problem for me.
  21. Reload or repair? If you shut off after initially starting up, you can lose the FCR; this is an acknowledged issue:
  22. There's a few tips and tricks you can do to make them less bad, but it heavily relies on scripting to lead them around by the nose. I made a thread a couple years back that got moved to the core wishlist:
  23. Thanks, NineLine. As noted, the purpose of the thread isn't to cast shade on the current state of the WIP FM and SCAS, but to have a dialogue on what we should focus on learning now and what we can expect in the future.
  24. Make sure to document and get a track so it can be reported, that's definitely a bug.
×
×
  • Create New...