daemon1808

Hi It is exactly the same that happens on the Gazelle "maintain hover" or the "autopilot" cheat for the huey. If you retake the control of the helo, and the physical stick and throttle aren't in the same position than the virtual ones... welcome to the world of spining and puke. But in the Gazelle and Huey you have "ghost" indicators for each control (showing where the maintain hover "inputs" are). So you can match your physical inputs to the "ghost" ones, before take control again. This avoid the problem. In the Apache, can be partially avoided with Imacken's advice: take control of pilot again, DO NOT TOUCH ANYTHING and use trim. This will match the cyclic and rudder with the position where George left them. But as the collective can't be trimmed, once you move your throttle.... welcome to the world of spining and puke. For sure "ghost" indicators showing "George Pilot" inputs, when you are in the front seat, will be very useful to avoid problems when you return to the back seat (if auto-trim function when you return to back sit is not posible to be done)

"En dos semanas" XD XD XD No, seriously, not in a short term. Weekends are to short and I am focus on learning the Apache. I have to complete/debug many of the new options for the chopper DO_ESCORT and DO_SCOUT missions. So you will have to wait for my hollidays or so Hi Chicki, v2.0 will have some kind of documentation, because it will be more complex, but V1.0 has not many commands to learn. The current documentation for MEP v1.0 is the first video of this thread. There it is shown all the "DO_XXXX" commands and waht they actually do.

Same for me. Holding the trim is way worse, and I end in an uncontrolable spin, bouncing and falling from the sky. I prefer adjust stick/rudder, trim, adjust, trim, adjust.... And for all of you that continue anoying others with the "IRL you don´t have trim reset, IRL this, IRL that....nanananana": Please, next time you crash a plane in DCS, break your computer, go to your home roof and jump... "because IRL, when you crash a plane it is destroyed and pilot is killed most of the times"

....and propper ATC for FARPs. I love when you fly away from them and, when you come back, you only get the "cancel takeoff" option... or when you are calling them to request landing at night (in order to let them know that they must turn on the FARP lights) and they ignore your calls ^_^

Indeed is a great work and the team has made a great effort to make a great module. Congratulations ED team!

Yes, only one flight of each type at a time (1 SEAD + 1 Ground Attack + 1 sweep....). Once the SEAD (for example) is destroyed you can call another SEAD, but not before. You can use the original 'DO_TAKEOFF' and 'DO_RP' if you want, or you can use new ones. In fact you can: 1. create one 'DO_RP' for all the flights 2. Create a 'DO_TAKEOFF' in airfield 1 and call a SEAD. They will spawn at airfield 1, take of and rally at 'DO_RP' 3. Create a 'DO_TAKEOFF' in airfield 2 and call a Ground Attack. They will spawn at airfield 2, take of and rally at 'DO_RP' 4. Create a 'DO_TAKEOFF' in airfield 3 and call a Sweep. They will spawn at airfield 3, take of and rally at 'DO_RP' 5. join them at 'DO_RP' and push them all (or one of them at a time) Imagination is the limit. Each time you create a new mark, it will "overwrite" the last one of its type.

After some trial and error, I have found that this behaviour is caused by the quick movement of the controls returning to the central position. Sometimes, the time span between the click for the trim and the release of the control is so tiny, that the game doesn't notice it. So, sometimes the user inputs are ignored because the game doesn't realize that the controls have been recentered. Another times the trim is done after the release of the controls (in this cases the trim doesn't change the position of the detent) The "workarround" is lengthening the time between the "trim click" and the release of the controls, but is a pain most of the times. It's a pity because in flight forward the apache is very nice to fly (good work ED), but trying to stop into a hover sometimes is suicidal. Curious thing is that the huey have a similar trim system, but this doesn't happen to it. Should it be possible to match more closely the trim system to the one in the huey? ^_^

Yes, completely recentered and calibrated (checked in windows configuration). And yes, I have tried with a deadzone of 3-5 (for the laughs, because up today they doesn't need to) ^_^

You mean recenter physically the stick/rudders? I'm releasing the controls after every trim (what makes the controls to recenter, thanks to the springs) Check my steps. Rudder left, trim, release controls (they recenter by themselves), left again(not working), right, left again(now it works) Same for the stick: forward, trim, release controls (recenter by itself), forward (not working), backward, forward again (now it works) Maybe the auto-recentering is so quick that the game does not take it?

Hi, I have figure out why it is very hard to use the trim in this helo, and maybe the reason that other players have similar problems. Sorry, but I can't share a track because it needs "user" inputs to reproduce this behaviour and it happens only sometimes. - Using VR, Hotas X and "Central position trimmer mode" both for strick and rudders - After a short flight trying to stop and hover again. - Move the rudder to the left one cm or so (example) - Click on trim hold mode R/Up to trim that position, and release the rudder. - The rudder is now locked in that point, as the X show in the "control indicator" diagram (as expected) - Try to move the rudder again in the same direction (left) - It doesn't adknowledge user left input, no matter how far you go left with the rudder. Until you input right with the rudder, it seems to ignore the left inputs. -It happen the same with the stick: ie: you trim stick forward, release stick. Try to go forward again with the stick, but it ignore your forward input, until you input backward and then forward again. Very weird and hard to tell under what circunstances it happens.

Hi, I have adapted the random daily mission of the A.R.E.A 18 campaign to be used with the Apache too. In fact now you can select the exact mission you want to play, not only the general type of mission. And this time no installation is required! Although it is not a AH-64D mission "per se", it is very enjoyable with all kind of helos, and particulary with the Apache (attacking enemy comboys, protecting ally comboys...). If you have no clue on how to use the Apache weapons yet, you can play the "Radio menu --> F10 Other --> Attack Helo (A2G) --> JTAC" mission to act as a JTAC with your apache as a good practice on your "hide and seek" techniques ^_^ Campaign intro video: https://www.youtube.com/watch?v=isDh6sr_h7A Campaign link: https://www.digitalcombatsimulator.com/en/files/3321123/ - No instalation required, but some mods are required for better inmersion. - In-mission audio messages and music for better inmersion. - You can choose the type of mission you want to play (A2A, A2G, cargo, etc.). Now you can also choose the particular mission, once you have choosen the mission type - Each time you play the mission, the events during the flight, possition of targets, enemy forces location, etc will be different for a great replayability. - Instructions to play the mission: 1. Once the mission is loaded, choose the VNAO READY ROOM slot. 2. After entering the Ready Room, open the radio menu and select "F10 other" option 3. Select the type of mission and the particular mission, or just choose "Random mission type" to let the game choose for you If you want to fly an Apache Mission, select the type F10 Other --> "Attack Helo (A2G)" --> whatever mission you want (like comboy escort, or comboy attack, etc) 4. Read the mission briefing 5. Click on ESC --> CHOOSE SLOT and select the aircraft you want to play during the mission (AH-64D Apache have cold and hot slots) 6. Play the mission and don't forget to use radio menu "F10 others" for better inmersion and get information. Enjoy!

you have installed the clickable mod for FC3, isn't it? You are seen a SU-25T cockpit inside AH-64D cockpit. Remove the mod, because is not working for the apache until the developer of the mod fix it.

Hi, I was pretty sure that DCS has some kind of memory leak somewhere, and the Apache has come to confirm it to me. I fly a mission with many objects on the field, with my personal settings and I get 25-30 FPS (5 PFS less than other choopers, as expected). I exit the mission. I load the same mission just seconds after (Button "fly again") Now I get 5-15 PFS with luck. Also sometimes DCS hijacks all my CPU/GPU usage, and I have to kill DCS from task manager. Any of you are having this kind of behaviour? I think that for those of you that have high rigs this is not a problem, because the memory leak is freed after some time. But for those of us that play with "just enough" rigs, is a killer.

And THAT is a perfect reason to delay the release a day, a week or a couple of months. Thanks for sharing it Bignewy. "We dont want to release a module and ruin the whole game in the process" seem very wise to me, opposite to the mantra that some people has been repeating like zombies these 3 months: "I want a complete, perfect, golden, godlike, supercalifragilisticexpialidocious, EA Apache and I don't mind to wait a lifetime for it. And you MUST want it too, otherwise I will call you impatient and criticize your point fo view and preferences" (because I have the "moral" high ground, Anakin)

You can call a "strike from the sky" using the STRIKE option in the "enhance" F10 menu. It is pretty similar to calling an artillery strike, but MEP "pretents" to call an AC-130 that will obliterate the marked area. In fact in MEP v2.0 you will have 2 options instead of 1: 1. Use DO_STRIKE that will obliterate the area where the mark is placed (current functionality) 2. Use DO_STRIKE;Lat_Long that will obliterate the given Lat/Lon coordinates given If you are interested in use MEP with apache, check the last video on my youtube channel, with the ESCORT option for MEP v2.0 in fact, in the "How to use" video, you have the "strike" option right at the end...

Hi, it is already planned in M.E.P v2.0 a way to dismiss support units Muchas gracias majo!!!

Ey guys! Check a glimpse on the MEP v2.0 (WIP) new AH-64 Apache ESCORT option. It fits perfectly with the UH-60L community mod, and will be great to be used in a mission with any chopper (including the AH-64D Apache module when it is released) MEP v2.0 will have some great improvements as well, and an easier "installation", thanks to Deadlyfishes advice. Hope you enjoy it

Thanks Draken! it did the trick. I was missing to DESG in the EHSD One could think that will designate the current WP. But no, it designates where the DMT is looking. Not much intuitive ^_^

I've tried that in the first place (it make sense), but it doesn't work The LSS find the laser spot, and the DMT lock on the target. But the bomb release cue line doesn't appear (and of course, the GBU doesn't drop) ^_^

Sorry, but I'm growing tired of repeating myself about the DEMO vs EA concept. EA: A not completed product that is in process to be complete at some point in the future. It is expected to be updated regularly until it is complete and the bugs fixed in a reasonable period. DEMO (As we know from the old days when all this EA, Betas, Alphas stuff doesn't exists): a DEMOstration of the product that shows some functionalities of the whole product, maybe stage-1 of a multi stage game, etc... to let the players know what to expect when the whole product is released. It is a one-shoot launch and it is not updated or fixed ever. You call the F-18 or the F-16 a DEMO? no, isn't it? That because F-18/F-16 are in EA yet, but are not a DEMO. The point of my proposal is not "just sound like impatience". It was to offer an alternative to the "I'm happy to wait a couple of months... blablabla". For me is just the opposite: "I'm happy to not having all the planned functionalities, as long at it is playable and enjoyable". And this approach is as legitimate as yours. If there are more people than me that prefer the DEMO approach, I was just asking ED to take it in consideration, if they think that it is doable without much efford. In any case, provided ED considered it a plan B if the delays needed are more than expected, it will not we an inconvenience for those that prefer the "waiting mode". Just do not download de DEMO and keep waiting. ...And said that, ED had decided that the DEMO is not an option, and seems that people is happy waiting or complaining about the delays. So for me the thread can be close.

Thanks Wisky, But I said"buddy lase", not own TPOD lase ^_^ AUTO mode is how CCRP mode is called in the Harrier, oposite to CCIP or AGM (a mix between CCPI and AUTO)

Hi, I've been trying to launch GBUs and guide them using buddy lase on the harrier in AUTO mode, but I am not able. The only way to launch and guide GBUs using buddy lase is in AGM mode, but I remember doing it in AUTO time ago. This have been changed or I'm doing something wrong? If it is possible, what is the correct procedure? Thanks

So, you said that the 2 complaining people are complaining less for the delay than they will complain for a demo version? I disagree. And proof of that is the offtopic in this same threat ^_^ Ok, thanks Bignewy. It's a pity

10 people are customers. 5 people are happy waiting because they want "100% quality". 3 people are unhappy waiting, and don´t care if they have "50% quality" at this stage. 2 people will complain anyway ED release a demo 5 people do not download the demo and keep waiting happily. 3 people are happy with the demo. 2 people will complain 2 is less than 5 Again, ok if ED have their own reasons to do not deploy a demo version meanwhile we keep on waiting a couple of months. But do not use the "people will complain anyway", because it is not true for all of us

Again, please: Do not kidnap this thread for another "I have pay for this and I want what I have paid for" vs "you have no right to complain because this is a EA" This is a sugestion that can release some of the pressure on the Apache deadline. I´m pretty sure that it will not worse the current situation (i think)