Floyd1212

You put your mouse over them and click and drag up. If they move at all, they weren’t all the way up.

Throttle levers should be set to FLY and left there. Verify in the cockpit with your mouse if they are all the way to 100% when your HOTAS is pushed all the way to your FLY setting. I couldn't find the exact thread where this was discussed, but if memory serves, there is some anticipation logic in the onboard computers that bumps the RPM when it expects a lot of drag on the rotor system. Bring the collective up more slowly and smoothly to avoid this when lifting off.

As a work-around, you can switch George to No Weapon mode and command him to lase a target, then as you get within range, switch him back to Guns and let him engage the target.

What was the symbology showing on the ASE page, and in what direction was it coming from? Maybe one of the ships? PrtScrn is the default button for taking screenshots in DCS. They end up in the C:\Users\<username>\Saved Games\DCS.openbeta\ScreenShots folder.

Yes, we have seen this, too. Joining a different aircraft as pilot, then joining on the original Apache as CPG seems to work for us as well.

Nice work!

Actually, I take that back. They aren't following the road properly at all. They are all over the place, loosely following the road, but cutting corners and going off road quite a lot. So maybe the real question is how to you task a group to go from Point A to Point B while staying on the road using scripting?

Ah, good to know. I'm definitely in over my head here, but this is my understanding of the problem: The mission that was originally mentioned in this post uses a route assignment to get convoys from one zone to another on the map. The convoy starts on the side of the road, and 3 points are determined; a point on a road closest to the starting point, a point on a road closest to the final destination within the destination zone, and the final destination point off the side of the road in the destination zone. The convoy is then assigned a mission with a route using the three points. WP1 is type = AI.Task.WaypointType.TURNING_POINT with action = AI.Task.VehicleFormation.ON_ROAD WP2 is type= AI.Task.WaypointType.TURNING_POINT with action = AI.Task.VehicleFormation.ON_ROAD WP3 is type= AI.Task.WaypointType.TURNING_POINT with action = AI.Task.VehicleFormation.OFF_ROAD The convoys seem to stay on the road for the main leg of the journey between WP1 and WP2, but will sometimes come to a stop before or on a bridge. We were attempting to demonstrate the problem without using scripting, but I don't see any way around it.

Maybe post a track to show us what you mean by "nothing changes" when trimming vs. not trimming. Include a mix of cruising and hovering, with ATT Hold engaged and disengaged, with the Controls Indicator up, first without trimming then with trimming. Could it be something is borked with your install? As Raptor9 explained in his post, "The Controls Indicator represents the cyclic's force trim reference location with the red X. If the cyclic is not within roughly 2% of this position, you can toggle Attitude Hold all day and display the box around the TAS readout, but it will have no effect on the flight controls."

Now I think we are getting somewhere. I think the distinction that @wowbagger pointed out in his screenshot is the failure happens when a Task is assigned to Go To Waypoint, which is the way you would tell a group to go somewhere through scripting. With a heavily scripted mission, you would spawn a group, find a point on the map, then task the group to go to that point. Here is my test, performed at a different location with different units, on a different map, without scripting, but using the Perform Task method of routing the vehicles. The Bradley group coming from the north moves to WP1 on their own, then when they reach WP1 they are tasked with going to WP2. At this point they depart the road and cut the corner toward the bridge, then the first unit stops before crossing the bridge. The truck group coming from the south follows the road properly, and if the bridge weren't blocked, would arrive at their destination. (You will note, however that the trucks in the truck group initially spawn facing their WP1 instead of aligned with the road, as the heading would indicate when viewing the group details.) @NineLine Track and mission files attached. Bridge Test.trk Bridge Test.miz

For example, this thread (with a very similar title) where Raptor9 provided a great response: The bottom line is, the systems assume that moving the cyclic around without trimming is just a temporary change in attitude, while trimming to the new position tells the systems this is the new attitude I want you to assist me with.

Yes, a track file here would be most helpful to understand what is going on. Based on your comments, there may be some confusion as to when the TADS will be an option as an ACQ Source. The ACQ Source cannot be the same as your active Sight. So, when you are in the CPG seat and have the TADS selected as the active Sight, you cannot also have it available as the ACQ Source, so it does not show up on ACQ subpage as an option. In order for the CPG to slave to what the PLT is currently looking at out the window, the ACQ needs to be set to PHS for the pilot's helmet sight.

Yeah, I meant to come back in here and update. I did run into a situation where waiting 5 seconds seems to have been too long, and a shorter delay of like 1 second did work. I’m not sure what’s happening under the hood, but maybe waiting 5 seconds allows the APU to spool down too much and you don’t maintain the air pressure needed for more extreme conditions.

What server is it? I haven’t had an issue with passing IC and playing on public servers while using The Way.

I replayed your track and saw the same thing you showed in the video, but when I took control and told George to lase different targets, the problem wasn't there for me. Could you have a faulty hat on your HOTAS that is triggering both up and right at the same time? What if you map the George controls to keyboard presses and see if it does the same thing? Maybe a slow repair?

Yep. There are many threads about possible reasons for Limas missing their targets. The going theory is INU alignment issues over time in MP servers, but apparently ED doesn't have anyone that plays in the servers we do. If you have a track file that you can share in this other thread, that would be helpful. https://forum.dcs.world/topic/333295-hellfire-limas-not-tracking-in-mp/

I also find it hard to see, in some situations. It looks like the crosshair image is a .png file that could probably be changed, and then the source code recompiled, but that is beyond my abilities... Maybe a future release might have a couple options to chose from? Or maybe it could cycle between a couple different contrasting colors so it shows up under different conditions?

According to the manual, the Missile Counter-Countermeasure Mode (MSL CCM) is "not implemented". It seems unlikely that this button had any effect on your success after that.

You can get BAL LIMIT warnings for any of the weapons systems. The manual says: "The required weapon aiming solution exceeds the ballistics processing capability." And to basically get closer. At what range were you seeing this with Hellfires?

Reset both? Reset one and then switch over to use that one?

You are talking about getting target data for a Lima prior to launch? Do you see the TARGET DATA? prompt at the bottom left? If not, de-WAS missiles and WAS again to start over. You may have data stored from a previous spot you were lasing. Your ACQ source doesn't matter in this situation. And whether they hit or not is a totally different question.

Thanks for this tip! Worked great. When ground air is not available (like at a FARP): Turn on the APU and wait for instruments to come to life Flip both engine start switches forward (nothing happens) Turn the APU off, wait 5 seconds, and turn the APU back on When the instruments come back to life the engines start spinning up and Ng starts to rise. Continue startup from here as usual.

@Lord Vader Can you clarify if ED is actively looking at this issue that has been described here, and in other threads? This thread is marked "cannot reproduce missing track file", but there have been many videos posted showing the issues, and many possible explanations described throughout the past couple months since the Lima was introduced. As you know, large MP track files taken from populated MP servers can be problematic. Please tell us what you need from us and we will be happy to assist. Even if a tester needs some MP seat time in the front of an aircraft in a MP server, I'm sure you would get plenty of volunteers that would fly someone out for some testing.

What you can do is have George pull up a list of targets, and then instead of stepping through the list with short-up and short-down, you can tell him to zoom in and out with long-up and long-down. Once zoomed in a bit, you can step through the list and he will move the TADS to each target. If you want George to use the TV camera instead of FLIR, you will have to swap to the front seat and change the TADS over to TV before swapping back to the PLT seat. Of course, this is all only helpful when you have the video feed from the TADS pulled up on one of your MPDs in the back.

Maybe post a screenshot so we can see what you see?