Floyd1212

I would second (third?) the recommendation of replacing the Warthog base with something with cams and springs, and re-use the Warthog grip. I personally like a lighter spring and a smooth cam, but any of the quality bases are better than the Warthog base for fine control around the centered position. The Warthog throttle can work fine for the collective, though I recommend the mod to replace the cursor nub with a better analog stick. There has been some good feedback in another thread for the Flight1 Falcon S1 pedals, which seem to be a pretty good bang for the buck. When flying in the front seat, an Xbox controller will give you most of the controls you need to manage the TEDAC and sensors, at least until the FCR is added.

It isn't that the SCAS doesn't have enough authority to counter the small amount of drift on your stick, it just isn't doing it. I just flew another test thinking I would try removing my curves and even try the FFB mode to see if I could reproduce the results you were seeing, but even without any changes to my axis settings, if I move my stick so that the white diamond moves off of the red X by a similar amount to what your track shows, I start drifting off and it doesn't hold position. Interestingly, if I slowly add some pedal I can get all the way to the edge of the light gray SAS authority box before it finally breaks free and can't keep the heading. It seems like with the current way ATT Hold is working, it is super strong in the yaw channel to maintain the heading, but super weak in the pitch and roll channels, and it doesn't take much movement of the cyclic to get it to drift. This is probably a change in the FM from before, when you weren't having an issue.

Yeah, I could see how the settings I am using wouldn't be compatible with a FFB setup. Regardless, it appears the drift when you take your hand off the stick is what is causing the issue. In the past, the hold modes were rock steady, but as they have made changes to the flight model it has changed. Hopefully they will get things dialed in and it won't be so sensitive.

I played back the track and saw what you were experiencing. I then took control of the track and was able to get it to settle into a stable hover with ATT hold. In your post above you state that you have no curves, deadzone, or saturation. I think your issues are a combination of your hardware, and your current trim and axis settings. Or more specifically, not having a curve or deadzone on your axis for your given hardware, which looks like it wants to drift a bit. After you trim for the final time before engaging ATT Hold, I can see your inputs on the cyclic jump slightly (as a result of the Instant Trim) and then when you release your stick the white diamond does not stay centered on the red X, but instead drifts forward on the first attempt, and forward/right slightly on the second attempt. I think without any deadzone, or curve, this tiny bit of input is enough to cause the aircraft to drift. I fly with an extension on my stick, a curve of 15, saturation of 90% and a deadzone of 2. I also fly with Center Trim mode. When I trim for the final time, then enable ATT hold, there is no jump of the inputs, and with the deadzone and curve on the axis, when I take my hands off the stick, there is no deviation between the red X and the white diamond, so I am not influencing the aircraft at all. I would definitely play with a curve and especially apply a deadzone for your stick axis. And maybe check the calibration of the stick to make sure it is as centered as it can be. If you can't get rid of the drift in the hardware, a curve will help reduce the amount of influence the input has on the aircraft, and a bit of deadzone would eliminate it completely.

Not sure if you are exaggerating here, or if it literally isn't doing anything for you. When I get into a stable hover and trim the aircraft with less than 3 knots maintained ground speed, then enable ATT Hold, the helo will maintain that position and heading while I adjust the collective to come up over the trees, etc. When I launch a missile, the aircraft will buck slightly, but will recover and maintain position.

Ah, you mean while using ATT Hold during forward flight. I only use it to help hold a hover, which it seems to do okay.

The Stability and Control Augmentation System (SCAS) is always providing a little bit of assist to keep the aircraft stable. And in this case, the yaw channel is adding a little bit of left pedal for you to keep the heading stable. You can display the flight controls overlay and see the system working (the green markings) to adjust your inputs.

For me, it will hold the heading fine (in reasonable wind) as I make small and gentle adjustments to the collective. When I want to adjust the heading of the aircraft with the pedals, I disengage ATT hold, change my heading, settle the aircraft, and apply ATT hold again. I'm using pedals without springs.

I posted some instructions in another thread here: https://forum.dcs.world/topic/298935-cpg-vr-view-is-off-center-to-the-l-side/?do=findComment&comment=5029995 I'm not sure how it works in VR; this may only work for flat-screen.

This is dependent on your saved default camera position for the front seat. When I load your track, and immediately after you switch to the front seat, my view looks like this. After you move your camera to the left, my view looks like this. You can modify and save your default view to correct this. I had fixed my view when it was too far to the left, and then when the patch was released that moved it to the right, I had to go in and move mine to the left, back to center.

Rockets are primarily the domain of the pilot. Because they are not guided, the PLT needs to maneuver the aircraft to get the proper alignment before firing. Theoretically, the CPG can pull the trigger when the PLT has alignment, but normally it is the PLT with rockets WASed. (COOP mode for rockets helps the PLT with the alignment and ranging, but the PLT would still pull the trigger.) Guns can be handled by either seat. With the active Sight set to the pilot's helmet display, it is very easy for him to aim the gun where he is looking, and pull the trigger. With PNVS active, you can even look "through" the cockpit to targets on the ground below you. This work well for close-range engagements. The CPG can use the gun more effectively at longer ranges using the TADS. Zoom in and set your man range with ranging data from the LRFD and take out targets at 2500m+ Be patient, as the gun is not a laser beam at that range.

Ah, I think I know what's going on there. My buddy asked me to throw some in there for him, and I used the wrong F-16 unit. Try changing them out to F-16CM bl.50 and see if that works.

No, not a this point. He does not use LMC or IAT. Your best bet is to provide a stable hover, but he can also track okay while moving, if you aren't flying erratically. Fly in a straight line and he can mostly keep the laser on target. If he starts drifting right at the end, like less than 3 second til impact, you can nose up or down a bit to get him to correct. If he is drifting high, nose up (which is counter-intuitive) and he will respond by moving his track back down onto the target.

These two statements seem to contradict one another, no? "Flying" from the front seat while the aircraft is hovering, and you have your head down in the TEDAC plinking targets is one thing, but actually flying the aircraft, NOE, while a Tor is tracking you, and you are evading missiles while your human CPG is trying to get a shot off and maintain a track is where it's at. You're not going to be able to do both of those things at once, and give each of them 100% of your concentration. How does that scenario work in the Shark by yourself? I don't own that module.

George won't fire over 8km. When you give him consent to fire beyond 8km he will say no (though you can still fire the missile yourself), then when you get within 7999 he will indicate the target is in range.

Bradmick posted a great video on how to use the PERF page to calculate the performance of the aircraft at given weights/altitudes/temps.

That isn't the behavior I am seeing. X-axis works fine for me, but I inverted the Y-axis for moving the cursor up and down. When I inverted the Y-axis, it had no impact on the X-axis. Make sure that when you go to look at your binds you are selecting the correct "seat" in the Apache, as it doesn't intuitively default to the controls for the seat you are in. Maybe you adjusted it for the PLT the first time, and then the CPG the second time? I'm using a Virpil Alpha L grip on my collective and an Xbox controller for the TEDAC.

Not that I am aware of. Do you see a persistence file having been created? It is placed in the C:\Users\<username>\Saved Games\DCS.openbeta_server folder, not in the "Saves" folder that some of the newer releases are putting in in.

Check all your controls and make sure there isn't something else bound to your cyclic axis. Sometimes binds get messed up after a patch. Nothing has changed recently to where custom curves are needed just to achieve forward flight.

There are some explanations in this related thread, but the short answer is you won't get the same dashed reticle indicating where the TADS is looking from the front seat, like you do from the back seat.

I think he's talking about the cursor on the MPDs. To keep that from sticking on the edges, apply a dead zone of 3 to that axis.

Very strange. It is working for us on my dedicated server. Anyone else not seeing these assets at the Northern FOB, or have any suggestions?

In the Apache, if you are in NAV Mode, it will add the points as waypoints. Switch the TSD over to ATTACK Mode and it will add your points as generic TGT points.

Sorry, I just checked and I do have them on my dedicated server: C:\Users\<username>\Saved Games\DCS.openbeta_server\\Mods\Tech\SAMSitesAssetPack Is that where you have them on the server?

I think those assets need to be present on each client's machine, not the server