Kharrn

Last try with a shameless copy and paste from the QUICK START MANUAL: https://www.digitalcombatsimulator.com/upload/iblock/ae5/1gklim4idv5p6s46zmgduj55g4m47mlo/DCS_AH-64D_Quick_Start_Manual_EN.pdf See page 325-336 (yes you have to actually read them!) Also @admiki provided relevant information for you. Hope you will find a way (or your way) to get good... Else i would advise to look for an online teacher who can explain the AH64D to you. I know that eading manuals can be confusing at times - but it is the starting point for complex modules like this. (not mentioning all those very good youtube vids here...)

happens each time i as CP/G jump into a "flight ready" Apache in MP. Solution for us is to always have both Plyers in the Apache befor pushing ANY buttons (and before startup). Then it works pretty well, except for some bugs (CPG sometimes cant hear ASE calls/ target data in TSD is out of "sync"/ Show controls (RCtrl + Enter) is not accurately showing the Pilots controls for the CPG/...) K

nearly every thread you open starts with a complaint about the modul or "inconsistents" you describe. Though you nearly never provide enough "data" (written info; video; or better .trk file) from the start. So we cant even adequately help without putting out random guesses... Usage of Hellfires (with George as CPG firing or with George as CPG lasing and Pilot firing) has been explained in verious threads - where you have been aktive in too. From my experience George works pretty well with Hellfires be it LOBL or LOAL. Yes sometimes there is a bug when George lases the ground instead of a target or (most anoying) when George switches MSL type to RF instead of SAL. But if it wont launch, in 90% of the cases when i tried it or when i looked at ppls videos, it has been a pilot error. Greetings K

if seen you have "force feedback" enabled in your game options (Misc). Afaik this can also produce some issues with the Apache (i read it some time ago but couldnt find the thread atm). If you dont have an FB stick i suggest disabling it. Hope this might help

Initial question has been answered in post number 2 by Raptor. Rest is a discussion you Falco might better shift to ED directly if you really want to talk on it further. But please dont elaborate in an off-topic conversation. Thank you. One rhetorical question from me: ever heard of licences!? Grüße

hmm schade. Wäre ja eine schnelle Lösung gewesen XD Also wenn das in den Optionen ohne Probleme funktioniert und in der Simulation auch funktioniert bei anderen Eingaben, dann weiß ich echt nicht warum es mit der KU spinnt. Sonst hätte ich noch gesagt ggf USB Problem oder zu viel "Input" (ggf durch andere tasten/achsen/...), so dass der Expertkey Input nicht immer registriert wird. Hängt die Expertkey Tastatur denn direkt am Rechner oder über ein USB-Hub ? Sonst ggf das mal testen... Aber wie gesagt, wenn sich sonst MFD/MPD in der Sim im AH64 bedienen lassen ist es mir leider auch ein Rätsel..... _____________________________________________________________________________________ Sry for all that german. At the moment i could not find a solution to the problem. K

Moin, denk dran dass die KU solange sie im "stand-by" ist, also nicht aktiv eine Option die eine KU Eingabe zulässt angeklickt wurde (wie z.B. MFD WPN page -> MANRNG ), einen Tastendruck nicht direkt annimmt. Dazu muss man die KU erst mit einem Tastendruck quasi "wecken". Also einmal drücken -> KU "blinkt" und wartet auf Eingaben. Sollte dies nicht das Problem sein, am besten einen kurzen ingame track (.trk) machen. Ohne Mods bitte sonst kann ED den nicht auswerten. Gruß K

i think i would rather have the IAT (Image Auto Tracker) and the MTT (multi-target tracker), but i guess this is the first step in that direction! Hope they can quickly fix the current LMC+Laser bug. Looking forward to those implementations

here is bug-report on the "not saving" issue: and a wish list item fro the whole problem:

afaik Heading Hold engages when you press "Force Trim Release" (UP). i will try to test later, but some observations from my humble opinion and my assumptions: 0:25 SCAS YAW is to the left because it wants to tell you "add anti torque pedal left to keep this attitude at current collective setting"; 0:41 SCAS YAW and your pedal input match up (nearly no difference in heading, only 2-3° left); 0:46 i assume SCAS heading hold kicks in wanting to "steer" back right; 0:47/0:48 heading hold gets on "hold"/disabled (as kgillers3 mentioned), just afterwards you let slightly go of your left pedal input and i assume SCAS YAW is applying left pedal again to aply anti torque for the current colelctive setting; 0:58 SCAS YAW is again left (see 0:25). I hope this might be of help!? If i turn when having "ATT HOLD" enabled at 0 knots, i do minor pedal input and then "trim" (FTR UP) - and again - and again. It kinda works. Will re-try later! K

because of this problem it currently is nearly impossible to lase and track moving targets or if you are moving yourself, especially when you have a new/inexperienced pilot. Please fix this asap, thank you! K

@Dagobert666The OP already started or "has been active in" multiple threads about rudder pedals (hardware), AH64D anti torque pedals or AH64D flight model (FM). And i was and will be always willing to try to help. I was merely pointing to the fact that there are enough threads about it and that it is better to not mix up multiple issues, especially when the topics description is on a total different (in this case not FM related) topic. Dont take it personally, but in this case your post is the perfect example of "cluttering" thread. That is just my opinion WASed??? (weapon action switch) edit: @AstonMartinDBSalready stated it perfectly in better words than i can

again as stated in all those other threads, there are people having no or at least not many issues with the TM or other pedals adn there are ppl struggling with the flight system. Please try not to throw multiple "issues" into one thread - this might get confusing fast. I for one, can fly easily with my TFRP, be it KA-50, Huey or the Apache. So imho there is nothing to be "fixed". @DmitriKozlowsky It is still work in progress so please finally understand that! (as stated in oh so many other threads....) I rather think your pedals are broke - or at least the calibration is. btt: TADS can only be used by the CP/G and not by the pilot (well you can kind of "workaround" with the VID page...but thats another topic). If you want to use the weapons as the Pilot, do as admiki already said or please check the corresponding section in the manual. A lot of stuff is explained rather good in there. K

press "C" to request controls. An other idea is to mimic roughly the correct axis movement George has, by looking at the "axis overlay" (right ctrl + enter) and then switch seat. Though i think the "request control" variant is the smoother one. K

as of now: Either a) slew TADS constantly while lasing or b) use LMC and fine input to stay on the moving target. When IAT (image auto track) is implemented, automatic follow of a hot or cold target can be accomplished (if the IAT can "filter" the target from the background and establish auto tracking). But there is no "lock on" ability per se. In all honesty, i think for most aircraft in DCS, the auto tracking is far too good compared to real life autotracker. But after all its a simulation of real world features. So im totally ok with it K

I wasnt talking about MFD exports and tbh i wasnt even thinking about that. So thank you for the point out on that! Referring to the OPs question about "CP/G gunner seat view in PIP window" though, i was thinking of a full 3d rendered PiP - even as an "export" to a second monitor that would meen a lot of extra (or doubled) rendering. It would be like rendering your main view for a second time and that would definately put a strain on your FPS. that is my opinion.

looks like another case of George switching MSL TYPE to RF. Screenshot a little lower and we might see "MSL TYPE?" in the TADS VIDEO. Has been eported in numerous threads. @OP good that it wasnt a permanent bug.

that would kill your computer unless you have NASA hardware.... and also: why!? As Pilot you can put TADS via VIDEO on your MPDs. As CP/G you can put FLT page on your MPD to see flight stuff. TSD is kind of mirrored so you would see each others input. ENG and PERF anyway. I cant imagine any benefit from a PiP - and it WILL be a strain on your FPS. K

Watch from 03:07. He even says "now its time to start the engines". Dont skip stuff when you try to learn something new. Maybe next time as reference use this one: or this: Have fun

I will be highly off topic here, but i was just remembered on one day during an exercise. For emergency extraction 2 guys were hooked under a german (eurocopter) Tiger. At the "front wheels", so to say. That looked fun Though the helo would just hover for some meter, staying at "jump-able" height. After all it was just an exer. We had a saying, roughly translated: Where there is need - one will find a way. Thank you for bringing back memories @Raptor9 K

i can move them smoothly, even with spring attached. No hardware changes done so far, only in the software (T.RJ12 USB_TPR_Calibration). People tend to forget that TM has software for products. In older hardware software (not drivers) will not automatically install.... But well, everybody can have an opinion i guess

doable, but sometimes George stops lasing (maybe cause of LoS) or "looses" the target and your missile will go awol

George switched Missile TYPE to RF even though there are no RF Hellfires on board and FCR is not implemented. It is a known and reported bug - and there are around 3-4 threads already about it - but you did provide a very good and short .trk file! Thank you Only workaround atm (which is only working in SP): swtich to the CP/G seat by pressing 2 on your keyboard, go to WPN page and switch the Hellfires back to SAL (semi active laser). Not working in MP cause seat switch is not possible in MP, though ED is working on it they said K edit: just a small tip. dont "overwhelm" George by too many commands. give him time between commands and wait for his response. also when he WASes the Hellfires, missile needs some time (4-6sec afaik) to spool up. So you cant fire immediately after slaving on target and lasing. Also George tends to de-WAS the Hellfires after destroying a target - which is also inconvenient and has been reported. Always keep in mind this time for the missile spool up. Use the VID screen and then right side TADS and then upper right side again TADS to see Georges TADS symbology on your vid screen. there is a lot of usefull information for the pilot (like YAW LIMIT, PYLON LIMIT and also the MSL NOT RDY indicating spool up)

just having 1:100.000 or even 1:50.000 map charts for each map would be an awsome step...