Kharrn

First of all: in this thread there is wrong info about own-lase or buddy-lase/JTAC-lase. It wont matter how your laser (LRFD) is set up (FIRST or LAST) when you shoot Hellfires on a REMOTE laser. Now on the topic of laser detection: As far as i can tell from the last 2 month of flying the AH64D, the Hellfire seems to have a kinda small seeker - speaking of "looking" radius and reflection detection. if this is realistic or not, i dont know. But my results in usage have been around 80%, meaning the target was at least disabled on the first hit (lots of time in SP, not much in MP sadly). Imho you cant compare the AGM65 to an AGM114 like the OP did. Also the attack profile of a Hornet is not really like the attack profile of the Apache - if you are not deliberately trying to reproduce that ofcourse. For remote laser usage you dont really need to be 100% in line with the remote laser on the target BUT you also dont want to be 180° opposite to it. So yes, you surely should know from which direction the JTAC (or lets say "remote laser platform") is lasing the target and the best position to get the missile seeker on the laser is: in the line to the target - but always getting into that position does not seem tactical sound to me. You can also test this by flying around the target at around 3-5 km for example and WAS/de-WAS the missiles as pilot when having set up the "remote laser platform" laser frequency. If you get the LOBL box on the remote laser, the actuated missile has "eyes on target" (laser spot). Remember that height also makes a big difference for detection cause of pylon articulation when WASed. I dont know how deeply the laser reflection is simulated, but i was able to shoot and hit most targets (LOAL and LOBL) in a 120-160° arc to the target, when "remote laser platform" is in the middle (so 60-80° each side). 180-220° can get tuff depending on the target size and angle. Im not saying the laser spot by AI (vanilla) could not be chosen better (e.g. tank turret top) to give the seeker better chance to detect, but we just have to change our tactics in this case i guess. IRL the laser detection at low heights and high angels (from gun platform to laser spot) is even worse afaik. Also IRL you would/could get a BP and final heading or laser-to-target-line for a good approach on target - or you could at least ask for it K

i dont know, but my guess would be that the deep integraton of the ASE into the TSD page (threat overlay, autopaging, etc) hase something to do with this !?!? K

well, we could shout out wild guesses now (like: Laser On? ARMed? WPN? George switched Hellfires to RF bug? Line of sight?) OR you could maybe provide a short track with the issue and/or video!? thank you K

Yeah there are a lot of "issues" that have to be adressed to make George a better Pilot and a smoother "transition" between handover etc. But George is really just learning to walk, though he was born crawling, which is great IMHO. The rest will come during early access i assume I will not go into deep on the topic of flying the AH64D "single seated" (like the KA-50), just one thing: go into multiplayer and look for someone who wants to fly with you, either as CP/G or Pilot. Trust me, that experience is the tip of flight simulation! Maybe you even buddy up and can fly "coop" missions, which also a lot more fun then flying SP. This bird is a 2-seater build from the beginning just like that. It is NOT intended to be flown single-seat. A big thanks to ED that they give us AI like George, Jester and Petro(something ^^ sry)... they could just drop a 2-seater without AI and say "live with it"..... Ok longer then intended but these are my 2 cents on this topic and i wont elaborate on it. Great that you personally found a working way/tactic to use the AH64D ins SP from a "single" seat and good to hear that EA is also making progress for you personally. We will see if we will get "special options" to make it more "single-seat-friendly" but i think that is a topic for the end of EA when Flight Model, SCAS and George are finalized. AFAIK you cant operate the TADS on the TDU while IHADSS shows Flight Symbology. If you use the PNV Video Select Button (above TDU monitor) you will get the Symbology on the TDU but not on the IHADSS (i assume from the P-HMD but not sure). Maybe use MPD FLT page as a workaround? (i know it does not help as much as the sym in the IHADSS) Sry for bad english, i had to hurry ^^ K

@xmudrollerplease stop advertising VAICOM, as already stated in another thread. It is NOT on the topic! If you want to tell us about your oh-so-great software, i ask you to start a thread in a general forum and not in the AH64D specific. Thank you K

has been reported afaik. i like the idea of arm/safe with the George interface when George is the CP/G

seeing your last posts one could assume you might get credit for advertising VAICOM.... just a friendly hinthint

wrong. it does not alter yaw trim in that mode. else there is something wrong with your dcs install. I would encourage you to do as Resection said and watch RedKites video. Yes it will show the X trimmed position on the yaw axis but it wont trim the pedals in the aircraft. Be advised that you will "loose" your curve bc you wont start at the zero input point of the controller when trimming as on the other trim-modes (as intended in this mode but just for a heads-up stated). Be advised that flight model is still under development or at least "under observation for tweaks" But SCAS is very much WiP and there are voices in this forum stating that the yaw SCAS channel seems to be faulty.

Set rudder pedal trim to "pedals without spring and ffb" (or something like that) from the drop down. et voila note: the "trimmed cue" in the show controls overlay (rctrl + enter) will still jump to the position when you trimmed, but it will not effect the yaw.

thank you for the quick response

Sounds like "settling with power" or too much collective in a low torque moment. Maybe this can help: Then i would encourage you to do the Cold Start Training Lesson within DCS as a start K

good question. Noticed that too but forgot about it. @Raptor9 @kgillers3 @NineLine Can you give us a quick answer on this please? much appreciated thank you! K

Just to let you know: You can fly from CP/G in SP. (MP solution will take a while i guess but i hope for the best) Press 2, then C. You have to assign all controls in the AH64 CP/G control tab though, it wont "use" the Pilot setup controls (because it is strictly separated which is very good IMO) George is still very much WiP... Yes, the interface could be better, but: WiP Yaw to the right might occure because you have to yaw left during hover. So maybe overcompensation. IMHO George should not be "the best fu Pilot since Red Baron" (yeah i know different aircrafts ;)) and therefore should struggle like we do - sure he should not ground you during "normal" flight. And George follows the same "rules" DCS AI has for decades. e.g. seeing through trees. Just my 2 cent on this Dont get me wrong, there is A LOT they have to do/ change on this module, but the overall quality is already overwhelming. At least you enjoy it too K

I can takeoff, hover and fly with my T.FRPedals just fine. Sure they are no beauty and i have to "calibrate" them after each computer restart by doing a full pedal left/right and brakes. But after that they work as intended. Got a nice deadzone and curve setting in the software that came wirh them. For the low price they are great! Only thing i struggle with is a change of direction during hover (att hold on) and sometimes transition. But i know for the first that i do something wrong with the trimrelease (direction) and/or with the atthold and for the second that i do too much correction (input) on the collective without adjusting cyclic and pedals enough. So both are pilot errors and yes, they can get better with better hardware, but maybe they dont. Then pilot errors will still be pilot errors. IMHO the two most vital things at this stage of development for the AH64 are: 1) know what you are doing wrong 2) know that a patch can change everything (((and that Flightmodel and Flight-"Assistance" like SAS are still WiP))) K

maybe try a repair on your install !? could help or not but worth a shot (rhymes) best of luck K

......

can also confirm. MP scenario, RHG Polarity button will only switch from one mode to the other (e.g. WHOT to BHOT) for a second and switch back. Collective polarity button works as a workaround. K

@Raptor9this! Post should be stickied and put in bold on each first page of the forum. Thank you! Often limitations that are mostly not in a manual will dictate the tactical usage of equipment. That is my experience from different ground/recon vehicles at least ^^ @YoYoI advise against rounding of coordinates. It can get confusing, especially for players not fully understanding how MGRS works. I rather just drop the "not needed" numbers. e.g. 1234 5678 would be 123 567 and still be in a 100x100m square. For GPS bombing, only a 10digit coord should be used (unless you carpet bomb from a B52) K

Sry to be further "of topic" but my question fits to the last conversation: as far as i could read up, you can also not see IR Pointer in PNVS or TADS because both are infrared cameras (thermal imaging) with an other wavelenght then the near-infrared devices (like NODs/NVGs) which can see an IR Pointer. Am i correct? If yes, it really is a letdown for CCA missions, like when inf gets ambushed or something and you cant really tell who is who. I would really much like to either see their IR pointers in my TADS/PNVS while having the IHADSS up or having IHADSS-like symbology in the NVG. But i guess there are tactics and ways to overcome this "problem" or there are invetions in later models. Still, night missions in the AH64 in DCS are lovely

Raptor already explained it to the point, but to add onto it, i want to point again to the manual. It says "Table 3. Target/Threats" page 354. From my pov: Singular / Plural. So 1 type Target point (which is Ident: TG) and a lot of Threats. One single tank is not a threat to my Apache per se. And i dont want my map to be cluttered with single tank symbols. CM for me provide the measure of telling me "look here - possible tank company" (hence the symbology for Ident AE i assume). Or tank btl, depending on what my intel brief said If i know my mission is to engage a tank company, there could be CM AE points for each platoon, pre briefed as estimated by Intel. Then i would normally know what the doctrine and dispersion of said platoons is and can thereby guesstimate dislocation. Hope this might explain a little wihtout going into military detail. If i find a single tank sitting alone in the countryside, i could still give it a Target Point (Ident TG) to reference. On second thought i would ask myself if that tank has gone AWOL, if the intel brief was bullsh, or if i will find his "oh so few" friends soon... K

ADF is not maxed afaik. you can even see it in the above screenshot. It is like 2/3. hot start the same. But yes the wierd "mouse drag rotate" on some knobs not working is strange ^^

you cant "spot" the laser from the JTAC with the AH64 from the backseat at this time (or ever AFAIK). But when the JTAC gives you a target grid and a laser code, you can enter that grid as a target point via TSD and align the Helicopter to the target. Then be in range, WAS the hellfires and shoot at it. There are already roughly 3 threads about this topic... Default A code is always 1688 at this time and default AI JTAC (non scripted) laser code is 1688.

AFAIK ACM currently is "always on" and that is causing some issues. Reported in the linked thread. K

Afaik the AH64D uses MGRS (military grid reference system) or latitude/longitude (in format degree,minutes,minutes-decimal) in the TSD "moving map". example as per Wikipedia: 4Q FJ 12345 67890 4Q = grid zone designator FJ = 100.000 meter square indicator 12345 (like "easting" or "x coordinate") 67890 (like "northing" or "y coordinate") 10digit means it has a precision level of 1 meter. AH64D will only take 8digit inputs (so precision up to 10 meter). Example: 11SGQ52184911 Refer to page 198 in the quick start manual. If you add a point, normally the TSD will automatically put in the "default" coordinate which is the present position of the aircraft to the KU and the enter cursor to the first digit of the 8digit numericals. If you want to put in the point from scratch you need the first grid zone designator and square indicator as well. When they are missing in the kneeboard, try the "default" ones. K

i suggest to refer to this post: So from my guess i think we will have to fly with a lot more usage of the "force trim interrupt" (trim up).... but i have not tested it now and need to gather more info on this topic. K