Kharrn

1200 rounds total is nothing for a Copter? ooookay.... What? totally on the wrong topic here? And thanks @Raptor9 and @BIGNEWY for the explanations. Can be closed i guess !?

afaik there are modern system in use or in development to get symbology inside NVGs (in other helos). But not for the DCS AH64D in the modelled time. Also you can use PNVS or TADS inside the IHADSS which is a great tool in "low light" conditions when NVGs struggle (cause there is not enough light or some weather etc for a good amplification). edit: Avro was faster

get some friends and play MP with CA. Some can control n shoot the arti or do JTAC or whatever, while you fly/gun. Use radio mods or inbuild VOIP for voice transfer of "data". hf

“Do not spoil what you have by desiring what you have not; remember that what you now have was once among the things you only hoped for.” (Epicurus) Not saying "do not wish for" stuff that may not be on the key features list so far. But this module will be a simulation as close to the real thing as it can be made. It wont be 100% exact to the real aircraft cause of (what i call) real world restraints/constraints. So give ED some time do flesh this out. thy K

wierd, i just tried the instant action Mariana Cold Start and without changing anything, helo was pretty light. Rockets, 4 Hellfires (2 on each inner pylon) and 60% fuel. about 30°C (FAT). no problems during hover

afaik yes they are spring-loaded to center position but will "remember" last setting. It has been discussed that it would also be realistic that in DCS AH64 squelch will be set to "always on". maybe we will see an special settings option for it or an ME option for each aircraft. Maybe it will stay the way it is K

as told to you several times already: George is really WiP (work in progress) and therefor functions are not all working as intended (that is my take on it). My guess is that George is answering "engaging" when you "consent to fire", but the check if the helicopter is in-constraints for a shot is done afterwards. -> early access/ beta / WiP (pick one) Though firing and hitting with Hellfires (LOBL and LOAL), rockets (in coop) and gun is working for me most of the time. that is why i wrote "get LOS and (be) in constraints" [for a Hellfire first detent launch]. Elevation below lased target can lead to a Pylon Limit (in articulation) in LOBL afaik. And yes you do see the target but not the weapon symbology which George is "seeing" (in TEDAC/ IHADSS) which will give you all the information you need. So remember in VID page to go for TADS and TADS again (upper right on MPD) when you want to get that info. K

as an example: if you set ACQ to a Point (like where the target is provided by JTAC or buddy or else) you well get the N range to that point and AFAIK that will give you a TOF when launching LOAL for that range. see below

watched the two posted tracks (this and the "rockets thread") and majoritiy of the time your LOS is off; the Apache is not "stable" (by George's standards for in-constraints without using 2nd detent); or your have a pylon limit. Pick target -> get LOS and in constraints -> tell George to engage via consent to fire (if you have trouble with key-/button-presses while maintaining a stable firing platform, i suggest using VoiceAttack or similar software) -> dont spam George with consent to fire oh and get your VID page to TADS and TADS symbology (upper right) so that you see the CP/G symbology (like pylon limit, range to laser, etc)

And strangely it works for 99,9% of the players.... But yeah the module is really messed up when one does not understand how things work...

Rogue likes to troll....dont feed it on the topic: lets just hope that we get FCR attach/deattach option for the armament (ground crew) menu at some point, so we can choose for ourself "in mission" (yes i know it would take time, but game wise im ok with some minutes). and if a mission creator wants to make it not deattachable i hope we will see an option in the MD for it. everything else is to the mission creater (e.g. attached or deattached FCR on British AH64).... my2cent K

@GrowltygerWrong module good Sir. You are in the AH64D section of the forum gl with your question! K

not correct. Currently you can switch MSL Type between SAL and RF (even if it should not be 'switchable' as far as i understand Raptor9's post). SAL (semi active laser) is the only usable mode at this time because FCR (radar) and corresponding Hellfires are not implemented (yet).

as far as i understand the Channels can theoretically have any combination from A A A A, A B C D or C C D D. But IMHO the first and the third would not make much sense cause you want to tell the missile by PRI (standard using Channel 1) to look for that laser code (laser code preset assigned to channel) and on ALT (standard using Channel 2) want to have a different code for Hellfire rippel fire mode (not going into detail here). Channels 3 and 4 are like 1 and 2 just like "favourites". So you put four different laser code presets on the four Channels to have the most variability. For example: own ship LRFD code; buddy Apache laser code; JTAC laser code; A10 FAC(A) laser code. You can set laser code preset to Channel via the CHAN subpage in the WPN page -> MSL (top left then) but still no solution to your problem i know.... Did you maybe got shot at? sometimes missiles are shown even though the wing is empty (shot to sh* ;)). Workaround would be to switch to MAN mode and select the next Hellfire via TEDAC RHG 'advance missile key' i guess....but atm i cant test if that works... K

adding on this (even though i have enough controls with 2 sticks, 1 throttle and an extra G13 keyboard): i hope and wish to see those 'up/down' keybindings like we have in other modules (just example). The NVS mode switch (a 3 position) already features that: up down off norm fixed E.g. for LHG TADS Sensor Select Switch: FLIR DTV DVO up down FLIR/TV (toggle) Thy K

from the screenshot i see that both laser channels PRI and ALT are on A code. maybe that causes the issues? Also the selected missile shows 'LS' which means (per manual): Missile standby, not set to a laser code. While others show 'AR' = Missile ready, seeker is in scanning for laser matching A code. And the active missile should be in 'AT' = Missile seeker in track mode, detecting laser matching A code. Did you fire as CP/G? Did you wait some seconds to check if the missile just needed time to "arm"? Hope that might help. K

My "solution": Button 1 = Jettison stations Modifier X plus Button 1 = flip Jettison Cover Even if i hit the button 1 out of slippery fingers from a ham-sandwich ( @Wags;)) while flying VR it wont do any harm. Works well for me and for every covered switch i know that modifier plus button is to "un-cover". Just my 2 cent K

AFAIK: IHADSS 'movement' is coupled to the DCS "head" movement (or better say: in-cockpit camera). TrackIR and other head- or eye-tracker (e.g. Tobii) just move the in-cockpit camera of DCS by axis-commands. It does sound more like an issue with multi monitor usage. Sry that i couldnt be more of a help

@-skarden-nailed it for me too. Apache is just sooo much fun in coop gameplay. I can sip coffee while my friend chauffeures me to the action

*facepalm myself* My bad! I totally overlooked that it is only one generic symbol... Shouldn't drink and type. +1 for friendly "AD" automatically put to CM instead of Target/Threats as an 'interim solution' Thy for clarifying!

Think you understood me wrong. I did not want to say that these topics shouldn't be touched by us cause of some classified/sensitive info that "could be" in there. We can surely discuss this as long as the forum rules are applied. What i wanted to say, is that i think that ED and the SMEs will be very 'sensitive' in touching these topics (in my posted case: ASE, RFI and Radar IFF) and have a lot of back-and-forth with military and industry to give us the best possible sim of an AH64D. And i do, believe me. But as i already stated "not really... in this case" = meaning the case of colored symbology in the TSD. After all i trust in ED and the SMEs to develop it 'as close to the real thing as it can be'. If there is a difference in coloring some symbols from real live cause of NATO classification or something.... well you should get the point now Again as stated by myself earlier: then you wont get threat rings from a friendly or neutral AD! IMHO its okay in the target/threats category (if that is true to rl). For gaming reasons i would rather have blue/yellow AD symbols in the target/threat category then have it moved to CM category. And yes, from my point of view, an eager Gepard Crew can be a f* lethal threat to my helicopter if i stumble into their detection and engagement range cause of bad situational awareness... Also AvroLanc had a good point. It is a 'clash' of the game-ness of DCS "missions" (e.g. MP dynamic/ foothold/ etc) and real world limitations of a module. Guess we will have to wait and see how ED copes with it Best way i guess is to present ideas, what we surely did in this thread. K

Can confirm that and thanks for the hint to it @S. Low Flying with a friend with me as CP/G. Waypoints from the ME work without problem to do an RTE DIR to. As soon as i enter e.g. a BP and do an DIR to: It takes a lot of time to switch to that point in the IHADSS of the Pilot (if it switches at all); It sometimes shows wrong range info in IHADSS of Pilot. So i did put the point into the active ROUTE and that did work or the Pilot did his own DIR to. Cant provide track cause of large MP missions, sorry. K

For George Hellfire LOBL/LOAL: Right Short = switch between LOBL and LOAL. Be advised that currently LOBL can only be switched to if trajectory is set to DIR (direct) Right Long = change trajectory (DIR, LO, HI) if LOAL is selected. For George not firing, help can only be given if we would see a track of your flight(s) - which will never happen i assume. My guess is that weapons are not in constraints or aligned as they should and that is why George is not firing. I am using George Hellfire, Gun and Rockets without *problems. Can provide track if need occures. There has been a lot of advise/help already. e.g. the tip of putting VID -> TADS on one of the MPDs (i use the right one cause of ENG page overwriting the left... yeah pilot skills i know ). Last thing: ED has put George AI control to another "category" (next to CPG and Pilot) for a reason! If you activate George AI interface it should overwrite every other setting. Example: POV Up for "View up" and POV Up also for "George AI up" command. Press it and it uses "View up". Activate George AI interface then press it and it should use "George AI Up" ("short" if you only tap it once or "long" if you hold it). Could not test it though. This was from end of march flying. Currently i personally use one modifier key for George commands. K * edit: "without problems" meaning that around 80% of the time when something does not work, it is my pilot error.

a) please dont mix NATO coloring and DCS AH64D TSD coloring. NATO unknown color is definately not red. For the TSD afaik friendly CM are blue, enemy CM are red and all Target/Threats are red - no matter their "origin". Hazards are the only yellow symbols. If this is close to real life or not, i do not really care in this case. It is how ED simulates it. b) i dont think that friendly AD will simply not be plotted into the database just because it is "friendly". Remember that you only get threat rings in the Target/Threats category of the TSD. And ASE wont tell you if it is a friendly radar or not, it will just tell you "radar searching" for instance. If it detects e.g. a Roland radar, it might tell you there is a Roland radar and if you then know that all Rolands on the map are friendly, you know you are in the clear. But if you dont get all that info and you are in an AD rich environment, i have a look on the TSD after getting "radar searching" and see that i am in a threat ring of an AD and then know that the position of that AD is a friendly position. So i rather like to have friendly AD on the TSD. c) I would like to say that i dont have something against pre plotted blue AD symbols instead of the red, i am just not fond of the idea of blue AD as CM. After all it is all about situational awareness and pre-briefed info and a good look at the F10 map - especially with "dynamic" missions where you often have no clear front line or battle area even though it is a symmetric conflict depicted. d) Said all that, i think that ASE, radar IFF and RFI are topics that are still pretty sensitive to touch. At this point i like it that ED gives us the tools (ASE and TSD currently) and the rest is for the player to work out. I dont want an rwr system simulated that drops out all "friendly" radar just to make our lives easier - if it is not so in the real aircraft. e) currently i dont have many ideas on how to "de-clutter" the target/threats category especially on big missions with a lot of pre-placed AD. Maybe it would be an idea to give the player another TSD database category for creating target/threats without touching the pre-placed ones. Even though this seems not to be like in the real Apache, i think this could be a small alteration for a greater benefit without touching other systems. Greetings K

@jonsky7Hard to tell without a track file or video. Syria is pretty hard on FPS, especially during low level flight. So there could be something coming in view that has to be rendered or dropping out of view etc... Maybe some pre-load or LoD related stuff. Just guesswork here. Paired with the Apache cockpit it can drop frames even with good hardware. A track file or video with parallel resource manager (to see strain on GPU, GRAM, CPU, etc) plus your ingame settings could be a start for ED to look for errors/problems... i think. @Floyd1212Maybe take a look at your RAM and/or GRAM usage when the problem occurs. Sounds to me like something is cluttering up (or getting flushed out in the second case) when "switching" helos. Hope that is a start! gl K