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.
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
-
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
@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?)
-
@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?)
@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_PITCHtogether 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? ¯\_(ツ)_/¯
