Floyd1212

I would like to setup a scenario where blue forces are scouting an enemy helo pad with a Hind sitting on the pad. Enemy ground units are spotted running to the Hind, and when they get there, the helo activates and begins starting up. If the infantry units don't get there, the helo doesn't start up. If the helo is destroyed before they get there, they are left standing on the pad without a ride. I'm not seeing an option for "Visible Before Activation" for air units like there is for ground units. I'm also not seeing a way to trigger "AI OFF" or "AI ON" to hold the startup from happening automatically. I could use Late Activation for the helo until the infantry arrives, but then the helo pops into existence in front of your eyes. Is there a way to accomplish what I am looking to do with simple triggers in the ME?

That's assuming the WP is included in the current route. To make any point your DIR you can select the POINT ? option at L1 and type in your point using the KDU. Or select the point with your cursor. Page 254 of the manual discusses all of these options in detail.

Ah, sorry. When you said you would try over and over again until it wouldn't drift, I figured it was drifting for the CPG, not just the desync issue seen by the PLT. Sounds like you are talking about the same bug then. Carry on.

This is now how the IHADSS works, which is more akin to the real thing. It does not have a "roll correction" component keep the symbology aligned with the horizon. There was some discussion about it when it was "corrected" in a patch last year. We had been spoiled with the incorrect behavior since the module launched. As mentioned here: https://forum.dcs.world/topic/353798-pnvs-and-tads-in-ihadss-are-roll-stabilized-again/

I think you are describing a different issue. The original post describes this bug perfectly. What you describe sounds like an analog drift in your MAN TRACK axis for the TADS. Are you using a joystick to slew the TADS, or an analog thumbstick? Check and make sure you don't have that axis double-bound to some unused controller, and try setting a deadzone of 5 on the axis to see if you can stop it from drifting off the target. In the meantime, I'm guessing there hasn't been much multi-crew action going on by the ED Devs...

I watched the CPG track and there it is, plain as can be. Thanks for taking the time to make it.

I don't remember seeing it in the patch notes as fixed. Are you sure? There was another bug fixed related to the TADS, but I don't think it was this one.

Yes, Dynamic Spawn pre-loadout screen.

I'm not seeing that for me...

You rarely ever want to reduce the power levers; keep them on FLY, unless shutting down the aircraft. Use the anti-torque pedals to balance out the thrust of the tail rotor when the tail wheel is unlocked. Like Corbu1 said, the wheel won't actually lock into position again until it is centered, like after you have started rolling forward in a straight line.

Typically, which aircraft can perform CSAR and how many troops they can carry is handled in scripting, and you could easily allow the Apache to carry 2 troops. And the scripts often add mass to the aircraft for each passenger, and luckily where they would sit as shown in the pic probably isn't that far off of the CG of the aircraft. As for dropping them, I bet they could hold on pretty good if their life depended on it.

Ok. It wasn’t clear, especially with the word “Logs” in the filename, but I get it. How far into the flight does this happen?

I think he is saying his computer crashed out of nowhere, and is asking (demanding?) for help interpreting the error logs? If indeed his engines cut out and his Apache crashed into the ground, then yes, a track file would probably be better.

Tinker at your own risk... https://forum.dcs.world/topic/301340-changing-tads-between-tv-and-flir/

This is true, but it also depends on how you mount the collective. If you mount it to your chair, this can be a problem as you describe. If you mount it to the floor this is less of an issue since the angle of the collective coming up from the floor makes the grip feel more natural. It is something to be aware of, though.

There are a couple threads that already discuss this in more detail if you need more help, but here are the commands you want: {cockpit_device_id = 51, down = 3092, value_down = 1.0, name = _('LHG TADS Sensor Select Switch - FLIR'), category = {_('TEDAC'), _('Custom')}}, {cockpit_device_id = 51, down = 3092, value_down = 0.0, name = _('LHG TADS Sensor Select Switch - TV'), category = {_('TEDAC'), _('Custom')}},

Understood, and thanks for asking. Looking forward to the upcoming improvements.

If there were a human CPG in the front seat, I would totally agree, and I would let them decide how they want to use the TADS. And I would have some level of confidence that they are doing what they should be, and hitting targets appropriately. But George often requires a little "babysitting" as he has a tendency to lase bumpers, antennas, gun barrels, etc. With DTV I can actually see what he is lasing, and avoid wasting a Hellfire when there is a high probability of a miss, and then get him to reacquire the track for another try. Please let us know what the devs say about the change. And if it was intentional, if they would consider changing it back to the way it was; at least until George has been refined with more advanced target acquisition capabilities.

I’ve noticed that since the latest patch (with the change to the George-as-CPG interface), he will actively switch the TADS back to FLIR when you command him to acquire and lase a target. As part of my startup routine, I will set the TADS to DTV so I can better see what targets he has found with the VID feed to the back seat. Once this was changed to DTV, he would not change it back. Have others noticed this new unwanted behavior? Is there a reason why he needs to be on FLIR now?

Thanks for the very detailed explanation. Understanding exactly how everything works is part of the enjoyment we all get out of this niche “hobby”.

Interesting. I didn't realize it did that. Pretty cool. Regardless, if you are firing LOAL on the laser from a JTAC (or a buddy) from the back seat, you don't need to have acquired the laser spot with the LST before you can rifle, or even point the TADS in the direction of the target. When the missile comes off the rail it looks for the laser energy along its flight path both to the left and right of center, correct? Or if my Sight is HMD, and I'm looking out the right window when I rifle the missile, and the target is off to the left of center, it will not see the target because the seeker is looking off to the right somewhere after launch?

This is not quite right. The Hellfire does not look in the direction the TADS is pointing like a Maverick, but instead has a fixed FOV. DIR is one of the three trajectories you can select when firing a HF in LOAL mode. It has a direct flight path toward the target, as opposed to a LO loft, or HI loft. If the missile seeker sees the laser energy matching its assigned code prior to launch, it will default back to LOBL mode and loft the missile appropriately for that specific target. You can launch a Hellfire in LOAL mode from the back seat with the trajectory set to DIR without getting the TADS involved. As long as you are facing the correct direction, there aren't any terrain obstructions, and the target is at an appropriate range, the missile will pick up the remote laser and track its target.

If you can get the JTAC to “sparkle” the target with his IR marker, you can still see that with NVGs. Otherwise, use the coordinates he provides and create a point, and set the point as your DIR TO or ACQ for aligning the aircraft.

I have the Virpil collective base and an Alpha left-handed grip. Works great.

Looking at your binds, you have the left half of your WH throttle setup for the collective, and the right half is your engine throttles? Then presumably you are only moving the left half when you want to pull on the collective? It may be easier to not control the engine throttles with your WH HOTAS, and instead move the throttles in the cockpit with your mouse during startup and shutdown, the only time you really need to mess with them. This way you can rest your hand on the HOTAS properly and access all the buttons with your fingers and thumb.