Floyd1212

You can go to the M > UTIL page and disable the SCAS for the yaw channel (or any of them), and try it yourself. I think you will find it even more of a struggle to keep the aircraft aligned how you want with it totally disabled. In the real aircraft, the pilot would use the FTR button while doing this maneuvering, which changes the behavior of the SCAS to stop fighting you, or at least fight you less. But how it is currently modeled in DCS, pressing FTR disables the channels completely, which drastically changes how the aircraft handles. I think having pedals without springs could make a big difference. It is ingrained in my muscle memory at this point that every little adjustment to the collective is accompanied by matching adjustments to the pedals, but like my collective, they will stay put when I relax my feet again. This means I don't have to trim nearly as often as I imagine someone with springy pedals does. When I am coming in for a landing, or coming to a stop to a hover, I reset my trim and fly it "direct" all the way to the ground, or until I am in a stable hover (at which point I trim and enable ATT Hold).

You need to make sure the "Hidden on MFD" is unchecked for the group in the ME, then they will show up in the threat database at the mission start. Some units, like SAMS and AA will show up as TGTs, where other units, like armor will show up as Control Measures. To see the CMs on the TSD, make sure you go to TSD > SHOW > COORD SHOW and enable ENEMY UNITS.

When the FTR is not being held, the SCAS is always trying to "help you" keep a stable heading. It will counter your slight pedal inputs with opposite controls to maintain your heading, up to a point where you are providing more input on the pedals than it is programmed to try and counter. This is the "break-out" force that was mentioned above, and is something that has been adjusted over time with tweaks to the FM. If you gently give it more and more pedal, you will find the point where the SCAS stops trying to correct your heading and lets you override it and change the orientation of the aircraft. It just takes practice to know how much pedal it takes. Alternatively, as long as you are holding the FTR button down, it stops trying to make those counter corrections for you in all channels: pitch, roll, yaw, collective, etc. I personally find that holding the FTR creates more problems for me than it helps, since I am not used to handling the aircraft without the SCAS assistance engaged. It is a very different animal when unassisted. So I just know that to get the aircraft to actually change heading to the left, I need to give it 1 inch of left pedal, because if I only give it .5 inch, it will counter it.

Do you have springs on your pedals, or spring-less?

Thanks for this tip. I tried it last night and it did seem to work well.

Looks like he is trimmed "nose-to-tail", as opposed to "aerodynamic" trim. In aerodynamic trim, with "the ball centered" you will notice some crabbing to the right. When trimmed nose-to-tail, you need to give it some right pedal, and then some left stick to counter that. From inside the cockpit, your bank angle will be a few degrees to the left.

Maybe there was a miscommunication between BN and the dev team as to what was "correct as is"? The main rotor system looks fine. The suggestion as that the same treatment be applied to the tail rotor, which it currently is not.

I think he is looking for a way to predict the exact time a hellfire will hit the target. Like if you wanted to coordinate a strike on an SA-15 from two different directions at once, but one helo is 9km away and the other is only 6km away. I suppose if there isn't a "mode" for this, some testing at the range could produce a chart with flight times for various distances.

At what distance are you engaging these targets when they miss?

I'm tempted to DL the track just to see how you managed to sheer off the gun flying like a crazy person, lol

I got similar results as BN when taking over this track, and the original track posted at the top of the thread. I can see it isn't working for the user, then when I take over the track it works fine for me. I can reproduce similar behavior to what the posters are experiencing when I set my special options for cyclic to FFB without springs, as it is expecting the FFB mechanism in the hardware to keep the stick positioned at the trimmed position. But when I switch back to Central Position Trim mode for the cyclic, my controls work as expected again. Perhaps the users with the issue are still stuck in FFB trim mode, regardless of what the UI is showing them in the Special tab?

There have been other instances of trim not seeming to work for some people. In both cases, a reinstall was needed to correct the issue, but maybe there is still another solution out there? https://forum.dcs.world/topic/311239-force-trim-not-holding-for-cyclic/

That sounds like a lot of work. I can change the scale manually after zooming in and out.

If I get the helo into a hover before handing it over to George, my collective and (spring-less) pedals are in the general spot they need to be when coming back to the rear seat, and it's just a matter of getting the cyclic into the correct position. Yes, there is a wobble, but no, I am not falling out of the sky. I can see how this might be tricky for someone new to the Apache, though. To those I would say keep flying, and eventually the comfort level will be there to recover from lots of unexpected situations. Edit: If you are in full forward flight when you switch back to the PLT seat, yes, the nose will pitch up. Move your controls to the general position first, then switch seats, or request control.

This is assuming only friendlies are enabled for the F10 map? You can always have George search for them. His eagle eyes are a little over-powered, but it works. If you don't want him to actually engage the enemy for you, use him to find the enemies, then mark enemy positions with user marks on the F10 map, then come back to them later. (It would be nice if he would actually lase and store, but that functionality isn't in the module yet.) You can enable Fog of War for the mission, then use Cockpit Recon Mode to spot them yourself and only the ones you have spotted will show on the F10 map. Does Liberation have support options for JTAC drones, or popping smoke on enemy positions in the zones? The Foothold missions have this and it makes them quite playable solo. If you are trying to avoid any of those "assists" mentioned above, it's all about scanning the battle space with a combination of TV and FLIR to find them. I don't know if Liberation places units is completely random, and you are looking for units in the trees and in the middle of towns/cities? If so, you might be better off flying something where you know the units are at least going to be located in the clearings. Also, I'm not sure if it is setup to keep the enemy units in a "red" alarm state, to keep their engines running, and thus more visible on FLIR?

Are you guys using Snap Views for this kind of thing? You can setup a camera position and save it to a Snap View "slot" that can be activated for the duration of a button press, then when you release the button, it goes back to the default view. This works well with a hat switch on your HOTAS so that you can hold LEFT on the hat to snap to a view of the left MPD and grip, then manipulate the cockpit buttons with the mouse, then release the hat. Maybe holding the hat DOWN snaps to the KDU for keyboard input, then release. Even with head tracking this is quite handy, as the snap view does not wander with your head, so the buttons you are aiming for with the mouse aren't drifting around while you try to click them.

I just hopped in to check it out in external view, and there is a slight coning effect of the rotor system when pulling pitch while still on the ground, but I'm still skeptical that the Coriolis effect on the rotor system exceeds the drag on the blades and causes them to over-speed. Maybe I am underestimating the Coriolis effect in my mental analysis of these forces in my head, but we aren't talking about a figure skater tucking their arms and legs in tight to their body, we are talking bout raising the tips of their outstretched arms by 2 inches. How much over-speed is necessary to induce the warning?

Is that a lot of work, or just re-saving what you have done differently in some way? It works fine to manually change the scale back to one of the two you have done already. If there was an easy way to force all the zoom levels to use one of your two versions, that would work.

Thanks for this great mod! I do have a question, though: When flying the Apache, zooming in and out will change the charts to different a different scale, which reverts back to the standard charts. Is there a way to prevent this from happening, or maybe rename/copy your charts into all the other folders?

Not that it helps you much to complete those missions you mention above, but this is where buddy lasing can be very helpful. A drone in the sky, or JTAC on the ground, or another Apache, or (in the future) the Kiowa can all help you get the job done from a safe position. For the mission with the mountain cover, I would use an LOAL trajectory from behind the mountain, and then pop up at the right time to lase the target but not stay exposed the entire time. You can also go for the SA-11's search radar and take it out, but the launchers can still track targets autonomously, if they are already pointing in the right direction.

You may not have read the entire thread to fully understand the conversation, but the OP was looking to eliminate some of the information on the IHADSS display, not all of it.

There have been discussions in other threads about how unstable the aircraft is when side-slipping at high speed, especially when combined with aggressive pedal inputs. Any chance you were doing something crazy trying to avoid an incoming missile? That's when it seems to happen to me at least.

nullA screenshot of what you are seeing on the IHADSS and your TSD page when this happens would be helpful. Like mentioned above, you want to make sure the Acquisition Source is set to TADS in order to see where the CPG is currently pointing the laser. If the TADS is looking 90 degrees off to the right, you won't see the dashed reticle unless you look off to the right for it. The little dots around the LOS reticle will tell you where to look for it in relation to your current head position.

It seems to happen when quickly pulling pitch from 0 to just to the point where you go light on wheels, and then stop.

Enabling LMC before making the position adjustment often helps. This lets you make small adjustments without having to manually track the target while moving again.