Jump to content

Bearfoot

Members
  • Posts

    1647
  • Joined

  • Last visited

Posts posted by Bearfoot

  1. I have my CPG flight control axes mapped/mirrored to my pilot's. Cyclic, collective, and pedals. When in the CPG seat, I request controls from pilot (as CPG), start moving the helo to where I want to go and only *then* switch to pilot seat. It's then a seamless transition. All this is before the SAS saturation thing, so no idea how it's going to hold up with trim etc.

  2. 12 minutes ago, Crashdown2 said:

    Sorry, have not seen the notification on the reply...I have had multiple crashes before and sent the crash dump to ED each time, I hope this helps.  Since I got a tool to trim memory, after the trim I can run Syria within 9GB, which is amazing.

    What do you use to trim the memory?

  3. 1 hour ago, Raptor9 said:

    To clarify a few terms and their correct usage to avoid confusion...there is only one "Trim" command, and that is pressing the Force Trim Release button.  So any time someone mentions "re-trim" or "interrupt the force trim", it means pressing this 4-way Force Trim/Hold Mode switch to the 12 o'clock.  So there isn't really a "trim up", "trim left", "trim right" or "trim down" command in the Apache, it's simply a four-way switch where one direction is the Force Trim Release, and the other three are Hold mode commands.  I say this to prevent confusion with those coming from fixed wing modules or the Mi-24 Hind where they expect the trim control to behave like a 4-way hat with 4x different trim directions.

    Not to be confused with "put the aircraft into aerodynamic trim"/"NOE trim"/"nose-to-tail trim".  These are referring to the alignment of the fuselage with regards to the airflow and/or flight direction, based on the skid/slip indicator, which is also called the "trim ball".

    Yep, so if I am in a level flight attitude with Attitude hold engaged and I interrupt the force trim, put the aircraft into a 10 degree banking turn, and then let go of the force trim, the aircraft will attempt to maintain that 10 degree banking turn.

    If I am flying forward at 30 knots ground speed in Velocity Hold, interrupt the force trim, decelerate to 25 knots ground speed, and then let go of the force trim, it will now attempt to maintain 25 knots ground speed.

    If I decelerate below 5 knots ground speed, it should automatically switch to Position hold even without touching the FTR switch; but if I am decelerating to a hover, I'm typically going to interrupt the force trim anyway while I maneuver the aircraft, and then once set I'll let go of the FTR and the aircraft will establish that position as the reference point to hover over. If I want to reposition to another hover location, I interrupt the force trim, re-position, and then let go of the FTR switch and the aircraft will hover at that new reference position.

    Unlike the Ka-50, there are specific breakout values that the hold modes will stop fighting the pilot inputs because the FMC recognizes these are deliberate inputs, and will not reestablish new references until back within certain criteria. This is done independently of the force trim usage to allow the pilot to fly through the hold modes without needing to disengage them first.

    The AH-64D FMC shouldn't be fighting the pilot inputs outside of its rate damping SAS function, but at the risk of sounding like a broken record, it is all work in progress.

     

    Thanks Raptor9 -- these examples really help pull it together! 

    • Like 1
  4. Thanks! Appreciate the insight. Things are beginning to become slightly less fuzzy!

    So we use the FTR to update the FMC what the reference is regardless of the hold mode, but the hold mode determines what gets "held" with respect to the reference. 

    As you come in for a hover then, would you typically engage the hold mode while at speed and then action the FTR as you slow down to 5 knots? Or just engage the hold mode after stabilized in a hover (and then maybe use the FTR to sweeten or fine tune the hover/heading etc)?

     

  5. 7 minutes ago, kgillers3 said:

    So if you think of it this way. You turn on ATT hold and you're going 70kts ground.  It will kick you into Attitude hold, you "talk" to the FMC through the force trim release, so you start walking it back and when it's finally <30 kts ground (decelerating) it will transfer to velocity hold, the entire time you have attitude hold on, it's never changed, but the way you communicate to the fmc is through retrimming via the ftr.  If you are moving the cyclic and not retrimming with attitude or velocity hold it will attempt to reassume it's previously assigned attitude / velocity once you recenter the stick to it's previously trimmed position unless it's beyond the realm of capability at which point it'll drop off. 

    So in the above example, you engage ATT hold at 70kts, and then pull the stick back to decelerate, actioning the FTR every now and then to recenter to new reference locations as you slow down? E.g, as you pass through 60, 40, 30 etc. knots (not exactly at those numbers) you would be constantly retrimming to the new speed, all the while the hold mode on?

  6. 6 minutes ago, kgillers3 said:

    When you hit att you’re not retrimming you’re turning the mode on and off, force trim up or force trim release is what I was referring to, sorry for the miscommunication. 

     

    Right now there’s no position hold that I’m aware of in game, velocity and attitude hold are in their beginning phases. While you have an indication that the hold mode is active it’s not doing anything for you at those speeds but idk just a guess and they haven’t released anything official yet. 

    If you have your control indicator on and you press and hold you can see the green line (sas authority) realign with your control inputs and remain there while force trim is pressed. I bump trim in game, if the sas authority maxes out I press and hold to recenter then back to bump trim. 

    Right now there’s no position hold that I’m aware of in game, velocity and attitude hold are in their beginning phases. While you have an indication that the hold mode is active it’s not doing anything for you at those speeds but idk just a guess and they haven’t released anything official yet. 

    Really?? Hah. It fooled me. LOL. Placebo effect is strong. I was thinking, look how easy it is to hold a hover with this position subhold ... when it was me all this time 😉

    So, whether eventually with the position hold or currently with the other hold submodes, adjusting/interrupting/actioning FTR does not change or disengage the hold mode?


     

  7. The manual says that activating the FTR starts to "decay" the SCAS:

    Quote

    When the force trim release is actioned it causes the SAS command to decay or “washout” at a one second rate. Actioning or “bumping” the force trim release for only a fraction of a second resets the mechanical portion of the force trim to a zero force state, but does not provide enough time to re- center the SAS.

    Does this effect the hold modes in any way? E.g., if I have engaged attitude hold < 5 knots, and then I action the FTR for > 3 seconds to recenter the SAS, in DCS at least I remain in position hold. Is that how it's supposed to work? 

  8. 14 minutes ago, Raptor9 said:

    Hopefully an update to the Quick Start manual will include a detailed description of such a topic.

    No doubt!

    After reading the referenced manual section above, I think I now see how the "philosophy" of the system is quite different from how I imagined it. The figure is also useful in showing what submodes kick in at different speed/altitude combinations. 

  9. 1 hour ago, kgillers3 said:

    The way the system works is by breakout values, so you would have to re trim so the game/program understands your pedals are at the new "center" position. This should only affect your heading hold, the rest of the sas functions will remain in operation. Unless they tweak it in software for your specific use case, you would need the x to match your pedal inputs, and when you start your turn you would have to remember where that new neutral position is. However, I'm assuming without springs you don't necessarily worry about heading hold unless you're specifically retrimming.  If you do I don't know maybe they have something to bridge the gap for a person like yourself and the logic of what they're trying to recreate. 

    to be clear this is referencing the heading hold only, not the overall stability system. 

    That was really helpful, thanks!

    SME Content Creators: It would be great to have a "The Dummies Guide to Understanding and Making the SCAS Work for You" 🙂 

    I'm finding figuring it out like putting together a puzzle with made up mostly of pieces of wisdom dropped in various forums and discords etc. by SME's . I just found TM 1-1520-251-10 has a discussion on the SCAS in pages 95-99, so hope that fills out the understanding more.

    • Like 2
  10. 11 hours ago, admiki said:

    Use CAQ and store when you move away and have more time.

    And if you select TADS as acquisition source, you don't need CPG cursor  (does it even show with George?).

    (1) I guess that makes it slightly faster -- still have to fuss about to line up cursor with the target. It's probably relatively less tedious in the real thing, but I have no curves set up on my cursor control input, so small adjustments requires some finesse. 

    (2) Ah, you're right. I've been seeing the TADS cross not George's, I think

  11. When flying as pilot and George as CPG, and George finds a target (e.g., you have commanded him to search an area and he gives you list and you select a target), what workflow do you use to store the point?

    What I do now is:

    1. "Point>"

    2. "Add>"

    3. Move the MFD cursor so that it overlays the CPG cursor and depress

    4. When maneuvering aggressively (e.g. when the "target" is very enthusiastically trying to untarget itself by shooting back!), it's a pain because your cursor is static with respect to the MPD frame, but the relative position of the target in the MPD frame is moving around as YOU are moving around. So it might be good to hit "FRZ>" as step 0 in this case. 

    For this approach to work, we have to have the CPG cursor show up on the MPD, of course ("Show>" etc. in your setup) The above works, but is a bit of a song a dance. Especially if you forget to hit "FRZ>" and you find yourself need to twist and turn in a hurry.

    Does anyone else have better approach?

  12. On 4/4/2022 at 4:10 PM, Sandman1330 said:

    I’m trying to figure this myself. So, as pilot, I can set my ACQ to TADS and see where the CPG is looking with the TADS. However, in the CPG seat, I can’t have TADS set as both sight and ACQ. The reason I want to do this is so I also get the dashed cross on my HMD where the TADS is currently looking, it would help to identify visually something I’m looking at with the TADS.

    Am I correct reading above that the only way I could do this would be to deselect TADS as sight, so that I can select it as ACQ? I feel like there should be a more streamlined way for me to quickly look outside the cockpit and know where my TADS is looking…?

    Hi Sandman, 

    I'm fumbling through the fog here myself, and barely touched the CPG seat ... but as a human CPG, would one approach be to drop a target point at where the TADs is looking at then reference that as an ACQ?

     

  13. Caveat that all the following applies to the GAME and any resemblance to real life is purely coincidental.

     

    In this game, SA-10 alone -- no problem. Same with SA-11, SA-6, SA-3, and (when we get them), SA-5's. Because they have a minimum engagement zone that you can fit the Ever Given through (60 feet is the lowest, for the SA-10).

     

    I've taken out SA-10's, solo, with: LMAVs, rockets, Mk-82's, Mk-82Y's, JDAMs, etc. etc. In fact, you don't even need the boom-boom stuff: your guns do the trick just as well (and can be easier to put the thing on the thing as well) As long as you hit the tracking radar, you can then waltz out any way you please. JDAMs are the easiest, of course: you don't even need to be pointing at them or even know where they are. But where's the fun in that? Most fun is the rockets and 82Y's.  

     

    The attack profile is the same for all: come in at <60ft and pop up around 2-3 nm. No need for terrain masking. In fact, works best on flat ground -- forests, cities, low hills etc. that force you to fly >60feet for your approach put you in the SA-10's kill zone.

     

    I have no idea how your server sets the SA-10 up, but if the SA-10 is defended by SHORAD/MERAD (= "layered defense"), then the story is different. 

    • AAA makes thing s a little spicy, especially on with 82Y's. But most of the time I seem to get by OK?
    • MANPADS/IR missiles definitely bring up the pucker factor. I have my counter-measures set to pop a flare every 1/2 second on my attack run and that and a couple of jinks/rolls seem to get me by.
    • SA-15 or SA-19? Fuggedaboutit. I mean, really. With a minimum altitude of 0, it doesn't matter if you are literally in the weeds or going Mach 1, jinking or janking. They'll take you out, probably twice, the moment you come within their range ... which will be long before they come within your range.

    If you server's SA-10 sites are undefended, or defended only by AA/MANPADS, go forth and conquer!

     

    Now, if they have some nasty SA-15's or -19's in the mix (which would, as far as I can tell, pretty much in line with doctrine), then the only approach is saturation.

     

    Which means Lone Wolf Solo needs to rethink his life choices. 

     

    For a saturation attack, you need to figure 1 x Harm per missile tube, then +1 HARM per radar. The point of all this is suppression and distraction. While you close in with your gifts to do the DEAD. Obviously, it takes multiple aircraft and coordination. If your server runs Skynet (and I hiighly recommend that they do -- completely changes the dynamics/tactics), then this coordination needs to be in time as well as space, because the radars will shut down when they see the HARMs, and they will neither deplete the launchers nor hit the radars. So your attack run has to be within a few minutes of the HARMs TOT, absolutely no earlier and not much later, to coincide with the time the radars are down.

     

    The other approach is with TALDs. This one is fool-proof, and needs way less coordination. And you can easily set up the AI to do it. The AI SAM's just cannot control themselves when they see a flight of these puppies, and let fly with everything they have. Right now, only the Tomcats carry TALDs, and they are usually the centerpiece of my approach in SP. A flight of 4 tomcats, launching 4 TALDs each, will deplete an entire SA-10 site defended by 2-3 SA-15's/19's in seconds: the moment they see the TALD's the AI dumps their load, with 2-3 missiles per TALD. In minutes they are done, and ready for a cigarette, cuddles, and just want to talk. Then you can come strutting in, pretty much at any height and speed you please to pick them off one-by-one, using whatever you please. This is why next to our GBU-24 actually doing the fancy low-level flying it's famous for, the Hornet TALD is the ordnance I'm looking forward to the most.

     

    • Like 1
  14. 27 minutes ago, ultrablue2258 said:

    I believe you are confusing the Attack Radar or SA page with the AZ/EL page, ED confirmed AZ/EL wouldn't be getting datalink contacts.

     

     

     

    Do you have a source for "ED confirmed AZ/EL wouldn't be getting datalink contacts"?

     

    Because, if anything, it seems that while ED has indicated that we will not be able to bug/lock donor MSI tracks (for better or worse, erroneously or not), it seems like they plan to do something  with donor MSI tracks and the AZ/EL) 

    unknown.png

×
×
  • Create New...