Kharrn

From a quick test on nevada. Never used hellfires from the Pilot seat with George lasing. I either let him lase and shoot or i use them remote on a FAC/JTAC/... laser from the pilot seat OR most times i switch to CPG and engage targets myself (cause of faster fire and target switching). So for the engagement with Hellfires from the Pilot seat but George in CPG lasing: Be in Pilot seat -> bring up George interface -> give him hellfires but ROE yellow (no fire at will) -> give him a target (slave) and select target from the list. George will beginn to lase -> WAS hellfires on the Pilot seat, get in position -> shoot -> watch fireworks K

as one example: your question was "is it possible...", this i did answer and this is also answered in the linked thread. Maybe be a bit more specific on what you need to know!? If you need to know "how to", i would ask you to consult the quick start manual for the AH64D at first, page 313ff, chapter "Laser-guided Hellfire engagement (Remote Fire)". If you need to know how to set up an AI FAC/JTAC or A-FAC in the Mission Editor (ME) i would consult the google search or forum search in the ME area. Casmo also has a nice vid on this topic. Many thanks as always to @Casmo K

sounds like you have an axis or a key (that has input) bound to that knob. Would adwise to check that first. Never happened to my MFDs so far, neither cold nor hot start. Please include a trackfile so we can watch and maybe replicate the possible problem. thy K

simply put: yes has been asked already. JTAC (DCS FAC) and also scripted JTAC and also A-FAC (AI) or multiplayer buddy lase, all work.

Late but anyways: 1) pilot or CP/G ? 2) turned down and up again the Master Volume on the right Com Panel? (known bug) 3) checked squelch -> deselect and then select it again (known bug) Just as a small solultion finding idea. Cant watch the track atm. K

Even though ED is checking this already, i made some tests myself. Can provide screenshots and track tomorrow. (AH64D TADS view) My assumptions are: 'late activated' units with 'show befor activation' may use the old FLIR models from before AH64D launch. At least they look a lot like that. And they are therefore "hot" (and white if you have whitehot selected). When they are activated they use the new FLIR models instantly, that is why they are "cold" (look nearly like surrounding). Only when they then start to drive/shoot/etc they will 'generate' heat and show up better in FLIR. I think this is also the point the OP was missing when he wrote '[they went] flir signature off'. So for mission creators, we now need a way to set the heat signature of a unit when it spawns or gets activated. Otherwise you will only get cold units all over your missions (as long as they didnt move etc). Thy K

nice to hear As Pilot im using my old n (t)rusty X-55 Throttle as collective and my fairly new TM Warthog Stick as cyclic. For the CPG i have a "real button box". An old logitech G13 "keyboard" with 22 G-keys (programmable), 2 "mouse" keys and 1 mini stick. This is kinda my left TEDAC handgrip plus extras. On the right i have the old X-55 stick as my right TEDAC handgrip. So yeah, table is pretty full but its working fine. And i can transition easily from CPG to flight controls or Pilot, depending on the situation. Also i can switch mode on the G-13 for more keys.....but have to bind them all in DCS first... XD Greetings K

Just as a side note: Have you checked that you are below 1.428 feet? Cause only below Radar Altimeter will function atm and you can only then set Auto Ranging afaik. Sry i wont watch modded tracks. IMHO you cant ask a developer to bughunt modded gameversions cause the dev cant know what the mod is changing codewise, especially not during EA. Just my 2 cents. K

oh well i totally forgot that step, my bad Thank you for claryfing this Raptor! So yes, the TOF is using the NAV range to the different TPs in my example. So when i shoot the hellfire it has the Nav range of 8.0 or 4.0 depending on the TP and when i laser, it cant correct that for the missile already in flight (i guess). I will test if the next launched missile will have a correct TOF (on the laser range). back in a minute or so ^^ -------------------- edit: tested. T01 N4.0km -> TOF LOAL LO 12 sec / lased 3890m TOF LOAL LO 11sec T02 with N8.8 -> TOF 35 sec For testing reasons firing a missile at T02 (TOF 35sec), then shifting laser to around 4.5km and lasing, second missile firing, TOF around 13sec. second missile hits, first missile hits, TOF of first missile still counting down. It is really nice to find out how all this works together with you guys. thy for sharing all the info im pretty confident in LOBL/LOAL now it damn, its fun --------------------------- Hope i did explain that correctly now - else i have to relearn english K

Thy for that insight! edited my parts. Maybe i did write that a little bad. The ACQ Target Point though will be used by the computer to estimate the ToF of the hellfire. Should be: The range to the Target Point, which can be used as ACQ in LOAL, seems to be used as the TOF calculation source. Btw just fired 4 missiles on a ground FAC lase in LOAL-DIR at 5.6km with 6sec between shots. Worked like a charm (as long as FAC is shifting laser quickly)

there is a lot of helpfull stuff in here but also some kinda wrong (lets say not fully correct) information imho. afaik: 1) LOBL trajectory is an own traj, there is no LOBL DIR or something, only LOBL. 2) LOAL can be DIR, LO or HI trajectory. All these can be used by the Apache that is firing the hellfire before lasing the target and also when firing on a "third party" laser (e.g. ground FAC or JTAC, Airborne FAC like Kiowa, other Apache,...). If you lase before firing and the laser is acquired by the missile seeker, the system will switch to LOBL automatically. 3) the ACQ source, like a Target Point will drive the constraints box of the hellfire (only in LOAL LO or HI and it is caged forward in LOAL LO and HI). The TP can be a reference to where you have to put the nose of your Apache to, to fire the missile in the direction of the target (and the laser energy). It is NOT where the hellfire is flying to like some sort of GPS fly-to-point. Each LOAL "mode" (DIR, LO, HI) has its on trajectory or "flying arc" and the hellfire will immediatelly search for a corresponding laser energy on that arc. The range to the Target Point, which can be used as ACQ in LOAL, seems to be used as the TOF (time of flight) calculation source. Just tested the above by 1) putting a TP to 8 klicks, firing "on" it with a hellfire in LOAL LO, but then lase a target at 4klicks = missile hits lased target, but ToF will still count down, cause the onboard computer does not know that the missile is "dead"; 2) putting a TP to 4 klicks, firing "on" it with a hellfire in LOAL LO, but then lasing a target at 8 klicks = missile hits lased target, but ToF will end at 0 befor missile hits. ("on" hereby is having the TP as ACQ and aligning the aircraft nose to it) So i have seen every expected behaviour of the missile which i read in Apache documents or from youtube vids. K More on this topic:

WPN -> Util -> L6 so 4 down from the RFI. Should be a "donut" on cold start and a filled one on hot start.

to that written above an also page 313 in the AH64D quick start manual Check that Hellfire (btw HF is the abbr vor high frequency...) is on [PRI A]. The little missile readout should be [A R] (for Lasecode=A and R=ready) when hellfires are WASed. Check that LRFD (not LST) is on A. Now there shouldnt be a REMOTE message. if there still is there is something rly wrong. Try to attach a short trackfile like BIGNEWY already stated, thy

thy for the kind words Though i have to say, much of this is written in the manual, expecially under "gun employment" and the rest is scattered in the cockpit overview and controls sections. But i know what you mean, manuals per se can be a difficult read. Just remember that the 'quick start manual' we got is also WiP! so after EA i guess ED will have a fully fledged out manual for the AH64D. During early access always except a lot of trial and error without lots of advice or documentation. For me, that is the fun in EA. There is always something new to find out around the corner (plus i have much time during train rides to watch youtube vids ^^) K

No intention to be rude, maybe use the search next time. Questions have been asked and answered in multiple threads. the title "Questions" also does not help with that. NVG search for "goggles" in the keybind for AH64 Pilot and CPG as BIGNEWY already stated. Put your game on "easy comms" in main menu options or use the correct frequency on the correct radio and the correct key command (Radio ICS)! Cant be more specific cause i dont have the game available on my phone ;) Maybe as i advised, consult the forum search... K

^ that Just to re-cap: Pilot 2 stage trigger with trigger guard on the cyclic (guard in reallife is springloaded and you have to kinda fiddel you finger under it, lifting it in the process / 1.detent will fire when system permits / 2.detent will fire overruling "some" system constraints - nfi) CP/G 2 stage trigger with trigger guard on the cyclic (rarely used afaik, everything else like Pilot cyclic BUT you have to action ("WAS") the weapon with the collective WAS) 2 stage trigger on the LHG (TEDAC left hand grip) for firing weapon of choice (1.detent and 2.detent same as on the cyclic trigger BUT you have to action (WAS) the gun with the LHG WAS) 2 stage trigger on the RHG (TEDAC right hand grip) for laser usage (LRFD). Master Arm has to be on ("arm") to fire laser. 1.detent for short burst ranging. 2.detent for continous ranging and target designation for laser guidance (manual page 74). Hope i got everything right in there K

My bad, sorry. My post was solely intended to give reply to dmatt76s post. Now on the topic, i do also experience the PNVS "stutter" while TADS is smooth. All with average of 50+ FPS in SP. Thy K

From the Manual for the Pilot seat HMD (Forward). The IHADSS is selected as the active sight. IHADSS line of sight (LOS) is used for weapons targeting. FCR (Left). The FCR is selected as the active sight. FCR Next-to-Shoot (NTS) is used for weapons targeting. TADS (Right). No function for pilot’s collective. LINK (Aft). Slaves TADS LOS to FCR Next-To-Shoot (NTS). If the CPG’s active sight is TADS and the pilot commands LINK, the CPG’s active sight will become HMD. Since FCR is not in, and TADS (right) has no function, only HMD will work at this time...so no switching needed/working at the moment in the Pilot seat. For the CP/G: please try the "C" for taking control of the Apache from the pilot (George) and also un-stowing the cyclic. After that please try to use the collective SightSelectSwitch. If this is not working it really might be a bug, maybe some SME can give more insight on how this works in real-life Apache. If you want to work around, just use the TEDAC RHG (right hand grip) SichtSelect commands and bind them to your liking. K

Trigger guard is necesarry on Pilot seat, not CP/G. Also, lasing a target as CP/G for the gun versus using AUTO range (which is utilizing radar altitude and terrain data) are 2 different methods of employment. And they will differ in accuracy, promise. Greetings K

I think a lot of work from ED and the SMEs was going into the FLIR system. But it is still WiP i guess (EA and beta version an such... mentioning againandagainandagain). As far as i can tell, yes, optical zoom (versus digital) will alter how the camera recepts the wavelength of the infrared light (short version ^^). Most new IR cameras n such can automatically adjust the effect. You can even see it in youtube videos when they zoom in, the brightness/contrast will change automatically. TBH sometimes i find the effect in DCS AH64D is pretty strong. maybe merge with this thread? K

I used military tech (vehicle mounted) IR from around 2005 and i can tell that with this (cooled, 2. gen) it was still hard finding targets 5+ klicks away (mast hight around 3 to 3,5 meters AGL). Everything more then 8km is luck or a lot of heat differnece between target and sourrounding. There is so much heat deflection by ground surface, weather has effects. Found some producer info on that IR we used: ^^ K edit: i think the newly and fresh implemented new FLIR system is still WiP (again: we play an EA module in a beta version of a game!)..... thy

NVG just puts a green filter and brightness stuff over the normal 3D render. PNVS does that AND puts a continously calculated FLIR picture over your 3d render AND also renders the normal lightning and all (like light bulbs etc) in the backround of the picture! Software and hardware are hard pressed with this. DCS rendering/source code/"tech" is pretty old to be fair so new - and truly amazing - modules like the AH64D and the tech that comes with it (like the new IR heat signatures) can even make it worse imho. This is all a quick description in "laymans terms". Lets just all cross fingers and hope for the Vulkan API and multicore/multithread Here is the latest "news" about it from BIGNEWY and also some info about it from SkateZilla, an ED Beta Tester (just scroll down a bit) Have a nice read and lets just be patient! K

a) did you change the keybind in the CPG tab or in the Pilot tab? if you are sitting in the CPG seat, make sure to change keybinds under AH64 -> CPG b) did you try "take over controls" from the Pilot seat by pressing C ? Maybe CPG collective is only "active" when you have controls. edit: and if you are in the Pilot seat you cant SightSelect at the moment (no function). Will play a role as soon as we get the FCR afaik. Sry cant be more of a help atm cause i cant check ingame. later maybe. K

Hey Raptor, thy for that insight info Sry to be so off-topic here: Source: https://meggittdefense.com/wp-content/uploads/2020/03/12-PAK-magazine.pdf Guess it was never fielded or only for prototype usage BTT now

afaik 12-PAK (1200 rounds) and maybe even 6-PAK (600 rounds) will come during EA. dont have the source to quote but i think it was in one of Wags videos. https://meggittdefense.com/product/apache-30mm-12-pak-magazine/?doing_wp_cron=1650467453.6491301059722900390625 K