Floyd1212

Can you post a track?

He has to lase the target for a few seconds to establish the TARGET DATA for the missile seeker, so don’t even bother telling him to engage until after he says “laser off”.

To add further, it has been acknowledged that the .2 KM radius for auto-advancing to the next WP should be greater than that. Not sure when we might see this updated to be more forgiving when flying near your waypoint.

I don’t think you can put that on George. The Limas seem to have lots of issues, whether George is firing them, or a human CPG. If you are watching the TADS and you see George lock on a target with IAT, then lase and hand off the target data, the rest is up to the missile. we haven’t really seen a statement from ED saying they are working properly or not. Some SMEs have commented on how how they aren’t the best solution for all applications, but what I’m seeing are instances where there is no reason the missile shouldn’t be able to track a target, and it ends up hitting the ground instead.

And when you apply left or right pedal it never moves? When you adjust your collective or throttle does it move? Once you get to 100ft altitude all of a sudden it starts moving with your pedals? You should be able to sit on the ground and give it left and right pedal input, and watch the controls indicator for that channel moving left and right accordingly.

I'm not entirely following the description of your problem, but I would check your axis assignments and make sure you don't have some other hardware double-assigned to the pedal axis. When you pull up the controls indicator, before giving any collective for taking off, can you use your pedals and see the diamond position moving?

Here's a video of the repeat waypoint entry after deletion bug, in case it helps. https://youtu.be/CnU7sGBpwPA

When you select a unit from the target list, he doesn't lase that unit and lases a different one instead? Ir you are saying he lases one unit and a 114K missile strikes a different target than the one he is lasing? When he lases, is he engaging IAT? I have seen situations where he locks onto the very tip of a vehicle which may result in an overshoot of the missile to the terrain beyond. Also, missile and terrain collisions are not George's fault. You will need to maneuver the aircraft so he has a clean shot. He has no control over how the missile reaches the target. Do you have a track file?

The ATT Hold and ALT Hold have been working for me just fine as well. I think the problem is with players that have FFB or sloppy joysticks that tend to drift. Any little force on the stick can induce the aircraft to drift out of the position hold. Only someone with a setup that was suffering from this before can tell you if it has improved at all. On a side note, I recorded a short track before applying the patch, and then played it back after patching, and it does appear that more collective is needed to hold an OGE hover. (Not the most scientific testing method, but it's all we've got.) When I established an OGE hover pre-patch, on the replay I slowly settled to an IGE hover, indicating a little more collective was needed to keep my altitude.

@Comrade Doge Thanks so much for this awesome utility. I was using the older version in the Apache for a long time and finally upgraded to the current release so I can use it from the CPG seat as well. I am having one issue that I haven't seen mentioned here: After loading a few waypoints into the aircraft, if I then clear out the previous points (with the trashcan icon) and add new ones, and then transfer them to the aircraft, it transfers the ones I had deleted as well. Am I not clearing the old ones out properly? Thanks!

Setup one of your MPDs to display the video feed from the TADS and you can see exactly what he can see.

Can't wait for the integration with Longbow Net, and the Kiowa. Then the full dream will be realized... I'm probably not the only one, but every time I watch a video from Waggs now, and he introduces himself at the beginning of the video, I get a rush of anticipation like I felt when watching the pre-release videos he was putting out before the module was released. I would watch them a few times in a row when they were released, trying to absorb as much information as I could as we waited patiently.

@giullep What hardware are you using for your cyclic, collective, and pedals? I think having pedals without springs helps tremendously as they are still in the correct position when you need to return to the PLT seat and resume control. The key with swapping seats at a hover is to get yourself in a stable hover before handing off to George. If you are only slowing down to 10 knots, and then let George come to a stop and establish the hover for you, your controls are not in the correct position for when you take back control from him. He has added in a lot more collective and left pedal than you left him with. This is where having the pedals without springs helps as they are right where you left them, and presumably the collective as well.

I wish someone would make a controller "caddy" or "frame" that a standard controller would snap into, and provide more buttons and hats off to the sides and in the space between the grips. Something 3D printed with a Leo Bodnar wired USB interface would work. Sell it as a kit with the switches and let the user buy the LB interface and solder the thing together. I modified my controller to add 8 additional buttons on the front, and rewired the 4 paddle switches on the bottom (the ones that normally just allow you to remap other buttons to them) and buried a LB board inside the controller. It wasn't that hard, but I would have dropped $50 for a well designed kit instead. Anyone? (If no one has taken the idea and run with it, I'll look into it when I get my hands on a printer some day.)

Again, it looks like you are messing with both the throttle (power) and the collective. Leave the throttles at FLY and only use the collective. If you enter VRS and the helo starts to shudder and shake as you drop out of the sky, you need to use the cyclic to fly out of your vortex; forward, sideways, backward, whatever. Just adding in more collective will often not allow you to recover. If you are in a hover and you want to descend, lower the collective slightly and take your time on the descent. Once you get your vertical speed dropping too fast, VRS is likely to follow.

There is. That's what the FLY position is for. Once you bring it from IDLE to FLY during your startup, don't touch it again. You just need to be slow on the collective to let the engines keep up and not let the rotor system over-/under-speed.

You are keeping your throttles at FLY and only adjusting the collective, right? Sounds like maybe you are reducing power on the throttles and l causing a low RPM situation?

I only use George in the back seat to hover for me when I want to swap to the front and plink some targets faster than it would take George to do it up front. Before swapping seats, I get the aircraft into the hover, trim, and enable both ALT and ATT hold modes, then swap to the front. There is a brief wobble when George takes the controls but then he gets it sorted out and stable again. When I want to switch back to the PLT seat, I tap "1" on the keyboard, followed by "T" which I have mapped to FTR, and as long as I don't touch my controls, this will re-establish the trim where it needs to be to maintain the hover, then I enable ATT and ALT Hold modes again. This is all within a second or two, so fairly quick. This works most of the time, or at least enough to where I can make some fine adjustments to stabilize. This only works if you haven't told George to go anywhere for you while he is flying.

Yes, until the ground AI is "adjusted" to be a little more realistic, your best strategy is to engage those threats with Hellfires between 5-7km. Keep your head on a swivel for unexpected units, and pay attention to your RWR. If you hear a "Gun" warning from the RWR, you want to take immediate action to break the lock as it doesn't take long for a Shilka to start putting rounds in the air. Unfortunately, those BTRs won't give you much warning, though.

It sounds like you are describing the benefits of adding a curve to your axis in the first place. The same benefit is gained when adding an extension: you can be more precise with your inputs around that zero point If the goal were to thrash the stick back and forth to a 3% deflection as fast as you can, yes having a linear response without a curve would get you there faster. But with the curve/extension you can be more precise and smooth with micro adjustments, to more easily input the 0.50 percent deflection you need that moment, or then another smaller correction to only 0.47 percent deflection. I run a curve of 15 with a 20cm extension on a Virpil base with very light springs and the least-aggressive cam available, and I am still amazed at how little I need to move my controls to get her to do what I want.

This is in the Options > Special > AH-64D menu. (You can only access this from the DCS Main Menu, not while in-flight.) In Central Position Trimmer Mode, after you release the FTR button on your controller, DCS will ignore any changes to the cyclic axis until you have allowed your physical controls to return to their natural "sprung" center. Then you can use the cyclic like normal to add roll and pitch to the currently' trimmed position. I highly recommend removing the springs on your pedals and using the Pedals Without Springs mode. It sounds like you are using the MFG pedals (from Croatia), so removing the spring is not a major chore. Kind of a pain to swap back and forth if you hop between fixed-wing and helos in the same session, but your pedal work while flying the Apache will be a lot more intuitive with them unsprung.

Try the "Central Position Trimmer Mode" for the cyclic to eliminate the "doubling" of the inputs altogether. You mention a damper kit on your pedals, but not if you have removed the spring or not. If you have no spring on the pedals, then you should be using the "Pedals Without Springs and FFB" mode for those.

This is where the “cursor select” function on your analog stick comes into play. When you have the circles lined up and centered, just press select on your analog stick and you are done. You don’t have to take your eyes off the boresight reticle.

When you go into boresight calibration the cursor on the MPD will jump to the BS NOW button (L5 maybe?) and be ready for you to simply press “cursor select” on the MPD when you’re head is in position.

It’s almost like the inputs from the cyclic, collective, and pedals, all relate to each other, and always need to be adjusted as a cohesive system. And that’s what we call “flying a helicopter”.