Jump to content

Raptor9

ED Team
  • Posts

    1889
  • Joined

  • Last visited

  • Days Won

    3

Community Answers

  1. Raptor9's post in using LIMAs with FCR vs George from backseat was marked as the answer   
    If the FCR is not available for targeting, such as if it has been damaged, it is being used by the Pilot for another purpose at that moment, or the FCR simply isn't installed on the aircraft. The FCR has many uses beyond just sending AGM-114L missiles toward targets on the battlefield, so it may not always be dedicated to targeting.
  2. Raptor9's post in Temperature units? was marked as the answer   
    Well first of all, the ECS is there to keep the avionics cool.
    Second, and this has nothing to do with the Apache obviously, I don't think making generalizations about a specific nationality with regards to perceived "reason" will win you any points on an internet forum. Just some respectful advice.
  3. Raptor9's post in Target sharing / Utilising queries was marked as the answer   
    As shown in the corresponding Wags video, sending an FCR Target Report does not permit direct engagement; it is simply a target report, similar to sending TSD target points. This allows other AH-64D's to gain situational awareness of targets in the area or their PFZ before unmasking. But you can CAQ on the TSD to make any of the FCR targets from the report your ACQ source.
    The FCR TGT Report does not transfer the entire FCR data, which includes an FCR-driven priority "shoot list", it just sends targets. Therefore there are no NTS or ANTS designations, stale timers, shoot list order, etc. Only RFHO may be used to handover a target directly to another aircraft's RF missile for engagement.
    Yes, it is often said that the AH-64D can transmit multiple targets to wingmen for rapid engagement, and that is true, but that doesn't mean it is only performed with one button push or that the non-FCR wingman can engage simply by repetitively pulling the trigger like the FCR-equipped aircraft. But that also doesn't mean the wingmen can't engage targets rapidly using RFHOs. Watch the video I linked above. You can send multiple RFHOs back to back, which can be engaged just as rapidly and is demonstrated in the video. I also recommend reviewing the latest AH-64D EA Guide on the DCS website, which describes all of this in detail.
    Each time an RFHO is transmitted, the NTS advances to the next target on the FCR shoot list just like if you fired an RF missile yourself (you don't need to cursor select each one like in the video, unless you want to send RFHOs in a different order than the shoot list). An RFHO is essentially firing a missile from a wingman's aircraft, which is why either method advances the NTS through the shoot list.
  4. Raptor9's post in SAM Threat Rings Unreliable was marked as the answer   
    Air defense engagement zones are never perfectly sized cylinders. Even winds aloft at higher altitudes can affect a missile's kinematic performance, not to mention the other factors mentioned here.
    The point is that the SAM rings on the HSD are only a rough estimate of danger based on pre-mission intel, rather than a binary state of "safe" or "not safe". Understanding the nature of the threat system capabilities and how they function is much more critical in determining the degree of the danger a threat poses at any given moment.
  5. Raptor9's post in George-as-CP/G - laser Hellfires in LOAL HI/LO trajectory was marked as the answer   
    LOAL LO and HI trajectories really mostly applicable to "Remote" engagements in which another platform is lasing the target instead of the launching aircraft. When self-lasing in LOAL, DIR trajectory is sufficient.
    On that note, George currently does not have the ability to select a point in the database to cue the constraints box for a LOAL shot using LO or HI. Since DIR is sufficient for a self-lasing LOAL shot, I recommend just using DIR for the time being.
    However, if you do intend to fire on a target using LO or HI while someone else is lasing, you can do this all from the Pilot seat yourself.
  6. Raptor9's post in ATT Hold works, ALT Hold does not? was marked as the answer   
    Please reference the FMC section of the DCS AH-64D Early Access Guide starting on page 186.
  7. Raptor9's post in Weapon loadout was marked as the answer   
    Nowadays, rocket pods are carried exclusively on the outer pylons, but Hellfires can be carried on the inner or outer stations. It was a lot more common to see both variations as you described prior to the mid-2000s.
    There is no impact to flight characteristics or maneuverability since a full rocket pod weighs roughly the same as a full rack of Hellfires (it could be slightly more or slightly less depending on what type of rockets are loaded in the pod). So no impact on roll moment or inertia by swapping one or the other.
    The reason rocket pods aren't loaded on the inner pylons nowadays is to reduce the possibility of hot gas ingestion into the engines when firing large salvos of rockets. But personally, I always assumed that such measures were based on rare instances of such effects under specific flight conditions, since AH-64s had been rocking the inboard rocket configurations for decades without any significant issues. But, I could be wrong.
  8. Raptor9's post in FCR Target Symbology was marked as the answer   
    Such information will be included in the next version of the DCS AH-64D Early Access Guide, which is planned for inclusion in the next update to DCS itself.
  9. Raptor9's post in TGP Drift VIS mode Maverick was marked as the answer   
    This was reported during internal testing and is already fixed internally. However, thank you for the report.
  10. Raptor9's post in TGP logic changed? was marked as the answer   
    This was a deliberate change. The DTOS, VIS, and EO-VIS sub-modes will no longer incur a slew to the Navigation cursor. Meaning that entering post-designate in these weapon delivery sub-modes should no longer cause the steerpoints to become offset. After further research and seeking some SME feedback, it became apparent that designating the "Target" location with the TD Box did not mean the TGT sighting point (like in CCRP or other Pre-planned sub-modes), but rather it was simply designating a physical target location on the ground, since sighting points are not used in Visual sub-modes like DTOS, VIS, etc.
    This small but significant distinction is what led to the correction of this behavior, and is what the following entry in the changelog was referring to.

  11. Raptor9's post in BOB UP mode reference heading wrong behaviour was marked as the answer   
    This was already fixed internally. Expect it in the next update.
  12. Raptor9's post in my noob f16 problem, datalink and landing was marked as the answer   
    After landing and repairing, you must set the MIDS and GPS back to OFF during the shutdown sequence. When starting up again, set the GPS back to on and wait for at least two minutes. Confirm by going to the DED TIME page and check that GPS SYSTEM is displayed.

    Once you see "GPS" displayed here, you can switch the MIDS LVT knob to ON.
  13. Raptor9's post in SMS page S-J performs swap function when used on left MFD was marked as the answer   
    @TAIPAN_, in your video, you set the left MFD to SMS format while in A-G master mode, and then press S-J. When this button is pressed on the SMS page, Selective Jettison master mode is entered.
    As @Tholozor mentioned, each master mode has its own set of MFD formats. The default format for the right MFD when in the S-J master mode is SMS format. But if you press the S-J button at OSB 11 on the SMS format while already in S-J master mode, it exits S-J and returns you to A-G master mode and the MFD configuration that you had when last in A-G master mode.
    You will notice that an MFD swap is not occurring, because the right MFD is set to BLANK format while in A-G master mode, but when you enter S-J master mode, the left MFD is set to FCR.
  14. Raptor9's post in DL members without TEAM and without PRI? was marked as the answer   
    Just because you can de-select both TEAM and PRI, does not mean there is a functional purpose behind that possibility with regards to datalink. I think you are inferring that potential combination of settings as having a datalink function, rather than simply a result of the fact that each are independently selectable. If you have two separate rooms in your house, both likely have a switch controlling lights in each room independently of the other. You could have lights in either room turned on while the other was turned off, you could have lights in both rooms turned on, or you could have lights in neither rooms turned on. But that doesn't mean that walking around in the dark bumping into things with neither rooms' lights turned on serves a distinct function.
    Having said that, having potential network members already added into a network but de-selected from receiving traffic serves a function of contingency. They may not be needing to receive datalink traffic now, but they may at some other point in the mission. It's a lot easier when planning ahead than assuming that everything is always perfectly configured as planned.
    Also, I would like to point out that you have the TEAM and PRI functions backwards. That might be leading to confusion with understanding why one might be set up to receive only one type compared to the other, and why you can have everyone in a given network as TEAM but not PRI. This is described in the DCS Early Access Guide.
  15. Raptor9's post in FCR - Gun not working as Pilot. was marked as the answer   
    @AndreNL, regardless of whatever weapon system you have selected, the weapon system can only be targeted by the sight you have selected within the crewstation. If you have selected the gun, it will only follow your head if you have selected HMD as your sight. If you select FCR, the gun will point toward the FCR target with the diamond around it, it will not follow your head. However, if the FCR has no target, the gun (or any weapon you are using) has no target to aim toward which is why you have LOS INVALID displayed. If you wish to aim your weapon with your helmet, you must select HMD as your sight. This is the same logic in both crewstations, regardless of what weapon you are using.
    Also, you cannot select TADS as your sight in the backseat. This Sight Select switch position only works in the front seat since the Pilot has no way to contrll the TADS.
    @Grennymaster, you can use the FCR with any weapon system. Gun, rockets, and missiles. You just can't use the laser-guided missile variants.
  16. Raptor9's post in Possible to transfer all net members to other radios? was marked as the answer   
    Each COM Preset can be tuned to any radio, which means that whatever COM Preset network you are using for datalink, you can tune it to any radio you like, as long as everyone is on the same corresponding frequencies.
    If you want to use the same network settings for any of the other 9 Presets on the COM page, you must configure each network individually. But if your intent is to use datalink on a different radio, the only thing you need to do is tune the corresponding Preset on that radio.
  17. Raptor9's post in Make this playable on Xbox/PS5 controllers and M/KB was marked as the answer   
    @NineGzuz, thank you for your interest in the DCS AH-64D. Unfortunately, what you are asking for is not planned.
    There are plenty of reasonably priced joysticks, some with twist-sticks for yaw and sliders for collectives; and such devices are worth the investment in my personal opinion. But an arcade flight model that has been designed for use within a "first person shooter" genre is not in the plans for DCS AH-64D.
  18. Raptor9's post in DTU Page was marked as the answer   
    Hello @HMSSURP, the DTU page is not implemented yet and is not available at this time. It was shown during early versions following the release of the DCS AH-64D, but was subsequently hidden while the devs work on it. That is why you may have seen some early videos showing it, but there is nothing wrong with your install.
  19. Raptor9's post in Radio Presets accept invalid values was marked as the answer   
    The DCS AH-64D Early Access Guide is accurate. The tuning ranges and intervals for the four primary radios are listed below:
    VHF radio: 108.000 - 151.975 MHz, in 0.025 increments
    UHF radio: 225.000 - 399.975 MHz, in 0.025 increments
    FM1/FM2 radios: 30.000 - 87.975 MHz, in 0.025 increments
    As stated, there is already a report submitted to rectify the radio tuning capabilities in the AH-64D cockpit, and in the Mission Editor; although in the case of the Mission Editor the tuning interval is the only issue whereas the tuning ranges are accurate.
    However, after reviewing the DCS EA Guide, there is one location on page 267 that fails to mention the possibility of tuning 108.000-115.975 for receive only operations. Although the VHF receive-only frequency range below 116.000 is mentioned in other locations in the EA Guide, this particular location needs to have it added.
  20. Raptor9's post in Realistic F-16 Startup Checklist was marked as the answer   
    The DCS F-16C Early Access Guide includes such procedures in both the Procedures chapter and Appendix A.
    It is as close to a realistic checklist as what can be publically researched.
  21. Raptor9's post in FCR Target Priority was marked as the answer   
    Only Priority Schemes A, B, and C will be implemented. Additional priority scheme selections were added for future "growth options", but were not implemented in the real AH-64D. Further, the Mission button below the Priority scheme option will not be modeled either since that button was only relevant to those "growth" priority schemes, which rendered the Mission button non-functional anyway.
    As such, the tag that was added to the title of this thread was in response to the original questions and remains "not realistic", since only Priority Schemes A, B, and C in their current form are available.
  22. Raptor9's post in FCR: slewing and buttons was marked as the answer   
    Hello @Donglr
    1) There is none in the Pilot cockpit. However the CPG may use the MAN TRK controller to slew the FCR scan area left and right.
    2) Please see this comment:
    3) Each time the arrow buttons are used to slew the FCR scan area, the scan area moves an entire "scan width". So if you have the FCR set to a full 90 degree scan zone in Wide, it will slew 90 left or right. If you want to move it partially to the left using the arrow buttons, you can either slave the FCR to your helmet (PHS in the Pilot cockpit), or you can set the scan size to Zoom (Z), press the arrow buttons a few times to center the scan on your desired heading, and then select your desired scan size to a different setting prior to performing a scan. Using a smaller scan size gives you more "button presses" in smaller intervals when using the arrow buttons to move the FCR.
  23. Raptor9's post in FCR Slave - Yes master was marked as the answer   
    The Slave function is always enabled by default in the Pilot crewstation, whereas the CPG can toggle Slave on and off using the SLAVE button on the right TEDAC handgrip.
    As a result, the Pilot is given two functions to mitigate the absence of a SLAVE button.
    1) The WPN->UTIL page displays a CUEING option that allows the Pilot to hide the ACQ LOS Reticle and the Cueing Dots around the central LOS Reticle. These symbology elements are only displayed in the CPG crewstation when Slave is enabled, but this allows the Pilot to selectively remove these elements from the symbology.
    2) If the Pilot's selected sight is FCR, Slave is enabled by default when the FCR is initially selected. However, if the Pilot moves the FCR centerline by pressing either of the arrow buttons on the FCR page, Slave will become disabled in the Pilot crewstation.
    Slave will be re-enabled if the Pilot selects any Acquisition source from the ACQ selection menu, even if the existing ACQ is re-selected; or if the Pilot selects HMD as the sight.
  24. Raptor9's post in Dogfight mode documentation error? was marked as the answer   
    Most likely an error in the DCS F-16C Early Access Guide.
  25. Raptor9's post in FCR detect targets through forest/trees was marked as the answer   
    The tree collision models will block FCR transmissions, which includes the trunks and branches but not the leaves/foilage. So depending on the thickness and luck, it is possible that the FCR is still getting through.
×
×
  • Create New...