Jump to content

Chic

Members
  • Posts

    1278
  • Joined

  • Last visited

Posts posted by Chic

  1. On 1/3/2024 at 11:17 AM, Longiron said:

    I have noticed that unlike the other helo's when the force trim is pressed(momentary) the ah64 does not ignore inputs like the other helo's until the stick is centered.

    with the ah64 you can continue to apply inputs to cyclic after a FT press, other helo's implementation of "central positions trim" the cyclic goes dead until you "pick it up" again at center.

    I would like to know if this is intentional, a issue with FT in ah64 or this could be a bug?

    The pitch and roll axis are trimmed independently.  You might be observing movement of one axis while the other is waiting to be “centered”.

  2. On 10/27/2023 at 12:59 PM, Raptor9 said:

    In the 2.9 update last week, the Heading Hold "breakout" values were implemented for when Attitude Hold is also engaged, so that the Heading Hold can still be overridden with the appropriate magnitude of pedal input. Prior to 2.9, the Heading Hold "breakout" values were only present if Attitude Hold was disengaged.

    Yah, very nice!

  3. Yah, same here.  Bitsum's Highest Perormance Mode solved it for me, chiefly by disabling core parking I assume.

    I use Process Lasso to implement it, but Park Control works also as Outlaw pointed out.

    Smooth Flying on max settings since 2.9 with this fix.  Very happy.

     

     Win 10    i7 8700K    RTX 3090   4k 2-D

  4. The  "Give Me Controls"  command works well when you are in the CPG seat a want to take the controls.

    When you are in the CPG seat and want to switch to the Pilot seat, the "Pilot"  command will switch your seat and instantly re-trim to your centered cyclic position before the control indicator diamond jumps.  

    GMC va.PNG

    P va.PNG

  5. On 3/14/2023 at 12:38 PM, Clyber said:

    It could be me or maybe the style how this manual was written but its very cumbersome 

    Take for example the Chapter Aircraft Controle, section Hold Modes page 206 and 207.  If i read Modes and Sub modes i think of some kind of hierarchical structure. Iam used to having the hierarchy broken down in pieces from the top down or visa versa first to understand how the system works. In this manual the modes are mentioned in processes without first explaining how the system is structured

    At page 207 Suddenly Submodes Heading hold and Turn coordination  are beeing mentioned how they work without explaining the total hierarchical tree of the modes meaning you have not explained yet what the primary mode is or to which  primary mode these submodes belong to.  It would be helpful to first know the  Primary mode and their  Submodes maybe a scheme illustrating the Modes and Submodes ?  

    Same goes for page 208.  If attitude hold ( in Position or Velocity sub-mode) is on, Heading hold is engaged. Here Position and Velocity are beeing thrown in the mix without a proper explaination  of where these submodes belong in the hierarchy. 

     Also at page 208   .Heading hold will be engaged when a few conditions are met. Why is the second point even  mentioned  in the list ?  .The Helicopter is off the weight on wheels ("squad") switch.  If the helicopter must meet a ground speed of at least 40knots and must be trimmed, obviously that means the aircraft must be flying or taxiing and is out of squad position.  Wouldnt this fit better in the general Hold modes overview.

    Maybe i missed something or maybe i should get used to the style of how it written but can you keep it simple please ? 

    Yah, that section is a word salad.  I found converting it to a schematic helpful.  

    C46E3441-94A9-46BD-A212-00211BA9A6BA.png

    • Like 2
    • Thanks 2
  6. 19 hours ago, Floyd1212 said:

    In your example, George is not pressing FTR before handing over controls; rather, your macro is pressing FTR right after receiving controls.  (You could also just press the "T" key on your keyboard and do this without VA, of course.)

    The problem is for someone without a dead zone configured for their controls, any bit of drift in the axis will register after you take controls and before you activate FTR.  With my setup, this technique works fine, but I could see how it may not work for others.

    For those with a slight drift (or no dead zone), you could probably use something like Joystick Gremlin (or similar) to temporarily disable your inputs until FTR has been pressed.

    1. "Disconnect" joystick/pedal axis from DCS
    2. Request control
    3. pause .5 sec
    4. Press FTR
    5. "Reconnect" joystick/pedal axis to DCS

    Our sequencing practically identical.  In actuality, self centering controllers should see negligible drift.

    Yours looks like a preferable solution for non centering controllers.

    Thanks for the constructive feedback.

     

  7. On 5/3/2023 at 3:46 AM, Loophole said:

    George just needs to press that "Trim" button before handing back control.

    He will, in effect, if you use the VA command shown below.

    I remapped REQUEST AIRCRAFT CONTROL UP  to "LAlt+LShft+C"  (can't remember why).

    Also mapped FORCE TRIM/HOLD MODE to "T"  (incidentally also mapped to Hat switch).

    See my update post later in this thread.

     

    GMC va.PNG

    • Thanks 1
×
×
  • Create New...