Floyd1212

This sounds like LMC got enabled. And since you didn't mention it in your troubleshooting above, perhaps you aren't familiar with it? When LMC is enabled, instead of the TADS slewing with your input and coming to a dead stop when you release your controls, it behaves like it has momentum, and your inputs on the thumbstick are like applying vector forces to modify its current slew rate and direction. So tap it to the right a few times and it builds up speed slewing to the right, then to slow it down again tap it to the left a few times to scrub off the speed.

In hindsight, another use-case of LST giving you the direction cues before firing the missile, is if you are in close to the target and expose yourself just long enough to launch, but then bug out and find cover again while your buddy continues to lase from a safe distance. Essentially making your Kilo a fire-and-forget missile, but with better reliability than the Lima.

Buddy lasing can be quite fun, but I find it less useful in a public server unless there is good communication going on, which often there isn't. I can't even get other Apaches to call their rifles on the radio when they are working the same AO as me. But in general, you need to 1) coordinate with the other player you are working with as to what laser code to use (you can either change the code on the missile to match the person lasing, or they can change the code they are lasing to match the code of your missile), and 2) communicate a general location of where the targets are located. Ideally, the person lasing would store the target and give you the coordinates for you to type in and get a specific location to orient your shot. Or even better, setup datalink between the two of you, and they can send the stored target to you directly. For me, if you are in a position where you can pick up his targets with LST, you might as well lase the target yourself. The fun comes in being able to lob missiles from behind cover and never even see the target, and more importantly, the target never sees you.

I disagree. In the Apache I have one 5-way hat setup for managing George. In the Kiowa, there's like 12 commands I need bound to get the same level of functionality I would out of George. Ideally, there would be a UI with a simple U/D/L/R/S interface available, with discrete commands available to those that want them.

My only complaint so far is how it continues to "settle" quite a bit when coming to a hover, and even at 100% torque it still continues to lose altitude until it reaches IGE and establishes a hover. Then after a few moments, it will start to climb at an alarming rate and before you know it you are 200 ft in the air. Maybe I'm drooping the rotor system and don't have the audible clues (and even warnings) I am used to in the Apache? Edit: Just noticed another thread where this was acknowledged and is being looked into...

For one thing, when you want to engage the Altitude and Attitude Hold modes, you need to trim out the aircraft before enabling them.

What I would like to see from ED, as an official solution, would be a special variant of the aircraft that is setup as a Fat Cow. (Or make the proper equipment available as a "loadout" on the rearm dialog.) A player can spawn into a Fat Cow Chinook (or arm it with the Fat Cow equipment) and take off to the front lines. They land and "deploy" the FARP equipment and shut down the aircraft. The FARP is now functional. The player can reslot in another aircraft and go do something productive while the FARP remains functional. Later, when it is time to relocate the FC, slot back in and start it up and fly to a new location and re-deploy the equipment in the new location. I think it is asking too much for a player to sit in the aircraft on the ground for it to be functional for 2 hours while his buddies come and go to rearm/refuel. Add in some warehousing aspects to limit the amount of fuel and ammo available and you can get two Chinooks in rotation to keep an area functional.

I also watched the track, and see you using the Trim Reset function, which causes the nose to dive. (This is odd to me, as I am used to the nose pitching up dramatically when the Trim Reset is used.) You probably don't ever want to use the Trim Reset with a springless joystick with friction brake anyway. That function is designed for people with sprung joysticks to immediately return the trimmed state of the aircraft back to zero to match the neutral state of their centered joystick; mostly to get them out of trouble if their currently trimmed state is unmanageable. You should be holding Force Trim Release (FTR) while moving your cyclic, then release FTR when you have your desired attitude. Your stick should stay in place because of the friction brake, and the red cross in the controls indicator should be centered over the white diamond.

If you cannot land within 30 seconds, you are flying too high.

Take a screenshot of your trim options in the Special Settings tab.

For anyone not aware, Grimm released a script he originally developed for his RotorOps generator that includes Fat Cow functionality. It will be nice when ED has native support for this, but this script will work on launch day to give us a functioning Fat Cow. We use it all the time with a UH-60L as a stand-in for the Chinook for now.

The TSE is described in detail on page 317 of the official Early Access Guide that comes with the module: The Guide is well worth the read for someone that is new to the module, and who hasn't been here from the beginning. The TSE was not yet modeled when the Apache was first released into EA, so Casmo was talking about how much better the gun works after the TSE was added to the module. Another recommendation would be to go back and watch the catalog of Wags' videos that he releases every time a new feature is added in a patch update. He discusses the TSE in this video from roughly 2 years ago. There are 46 videos in the AH-64D playlist so far.

What you describe sounds like the natural effect of added torque on the system when the main rotor is spinning counter-clockwise. When you increase the collective you will need to apply some left pedal to counter the torque to maintain the same heading. If you pull up the controls indicator and you actually see the pedal axis moving as you move the collective up and down, then you have some other problem.

Page 99 of the User Guide has some info on the different IHADSS Symbology Modes you might find useful. Try Cruise or Transition modes for flying in low visibility situations. Transition mode has an artificial horizon, and Cruise mode even has a pitch ladder. null null

ED is well aware of what the desync issues are, as the patch notes even say to expect them. The real question is, when can we expect a fix? What does “ASAP” mean in the patch notes? Is there a hot fix coming, or are we going to be waiting for weeks? Your most passionate users, members of virtual squadrons that train and fly together as a PLT and CPG team, are essentially grounded right now with a completely unusable module.

Just to clarify, Joystick Gremlin doesn't determine how the triggers are "seen" as being one axis or two by the OS. It is the driver you use in Windows for the controller that determines this. The XINPUT driver treats the triggers as a single axis, the standard HID Device driver treats them as two axis. https://www.reddit.com/r/xbox/comments/qer8pv/xbox_controller_right_and_left_trigger_merged/

I replayed your track file and saw the knobs for brightness and video rotating as you manipulated them, but I did not see the WPN, or FCR buttons (etc.) on the MPDs being depressed when you were switching between pages. What device do you have the MPD bezel buttons mapped to?

You are setting up the cursor controls as an axis, yes? Sounds like you are trying to bind an analog stick on your hardware to a set of 4 digital button presses in DCS.

I'm not seeing this issue happening for me either. In a cold and dark aircraft, if I use my touchscreens running Helios to adjust the knobs they do animate in the cockpit to match. And if I use my keyboard bindings to type something out on the KDU, I see the buttons being pressed in the cockpit accordingly.

It sure would be nice if there was a button to "save the previous 60 seconds as a track file" that you could press at any time to get a track snip to share.

Do you have the FCR as the active Sight? Are you in the back seat or front? Maybe post a screenshot of your displays so we can see what's going on. Or, even better, post a track file.

I had the wiper desync the other day. The CPG could turn them on and off for him up front, but they stayed on permanently for me in the PLT seat.

Nicely done. Keep up the practice with hovering and it will come. There are lots of virtual Apache pilots out there that have tamed the beast, and can execute delicate and precise maneuvers while hovering around buildings and treetops, not to mention the helipads. I know having higher-end hardware can be an advantage. What worked best for me was very light springs, a 20cm extension, and a curve of 15 on the cyclic. If flying the Apache is your dream, consider saving up for some good hardware and it will be a night and day difference.

This will get easier over time as you develop the muscle memory. Don't give up and let George do it for you or you will never get there!

Yeah, he isn’t great with managing his zoom to properly lock onto a vehicle. I have seen on many occasions that if I am flying along and want him to acquire a target off to my side, he will get close to the target and zoom in, then not have enough “slew” available to get the crosshair over the target and zoom out again, then slew over and get close and zoom in again, then the cycle repeats over and over and can never lock on. Then there is the problem of him locking with IAT on the bumper of the vehicle and the missile misses the target. If I’m watching him and he is slowly slewing the TADS onto the target, possibly because I am moving in the opposite direction that he is trying to slew, you can sense that as soon as any part of the crosshair is on target he will IAT and then you have to start him over again. I will sometimes jostle the cyclic just before he gets on target in the hopes that it will help him get a better lock. It would be nice if he understood to aim for the center of mass of the target, especially on an enemy helo where if the aircraft changes direction now the laser might be missing the target entirely. Or maybe he can establish a lock and then fire, then make an adjustment more toward the center of mass while the missile is in the air.