• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

Updated my AAO autopilot control template

Scheduled Pinned Locked Moved Piston & Turbine Dukes
4 Posts 2 Posters 231 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • RandolfR Offline
    RandolfR Offline
    Randolf
    wrote on last edited by
    #1

    If anyone is using my AAO templates for the Duke, I updated the CWS button to now work with the new CWS implementation in Duke v1.1 update.

    Also note that when using AP pitch reference control from my template, the tablet option for hardware events has to be turned off.

    Any feedback welcome.

    https://gitlab.com/randolf.lemmont/fs-bksq-duke-mods/-/releases

    M 1 Reply Last reply
    2
  • RandolfR Offline
    RandolfR Offline
    Randolf
    wrote on last edited by
    #2

    And forgot to mention, that from a quick test, the new CWS button in the updated Duke works very well!

    1 Reply Last reply
    2
  • M Offline
    M Offline
    mysticfm
    replied to Randolf on last edited by
    #3

    @Randolf said in Updated my AAO autopilot control template:

    If anyone is using my AAO templates for the Duke, I updated the CWS button to now work with the new CWS implementation in Duke v1.1 update.

    By any chance do you also have revised FSUIPC macros for CWS? (Or perhaps there isn’t that much complexity to them anymore?)

    RandolfR 1 Reply Last reply
    0
  • RandolfR Offline
    RandolfR Offline
    Randolf
    replied to mysticfm on last edited by
    #4

    @mysticfm ofc, these should work in FSUIPC.
    You need to replace the expression after the # sign with the following (before # is name of the macro).

    press:
    1 (>L:var_PilotCws_IsDown, Bool)
    release:
    0 (>L:var_PilotCws_IsDown, Bool)

    But with the newly implemented HW events support, you could try using the newly supported event K:SYNC_FLIGHT_DIRECTOR_PITCH together with the HW events option on the tablet. Then you wouldn't need to define macros in the events file. Though I haven't tried it and not sure how to use it, if you need to give it parameter 1 and 0 for press and release?  ¯\_(ツ)_/¯

    1 Reply Last reply
    1

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users