Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F-14 AP engage 2pos #1017

Open
1 task done
Biggus22 opened this issue Dec 2, 2024 · 4 comments
Open
1 task done

F-14 AP engage 2pos #1017

Biggus22 opened this issue Dec 2, 2024 · 4 comments
Assignees

Comments

@Biggus22
Copy link

Biggus22 commented Dec 2, 2024

Version

  • I am using the latest version

Aircraft

F-14

Control

PLT_AUTOPLT_ENGAGE

Description

Right now the only option for input on this control is to increment or decrement. It's normally a magnetically held switch, and after modifying a two pole switch to be held by a magnet, I'm only left with two pins on my toggle switch, common and the input pin. A two position switch option would be great! :)

Screenshots

No response

Additional context

No response

@Biggus22 Biggus22 added enhancement needs triage The issue has yet to be reviewed by a maintainer labels Dec 2, 2024
@charliefoxtwo
Copy link
Member

This switch is really weird for some reason. It'll take a bit of time for me to work something up to support toggle actions for this switch, since we don't have toggle support for any other controls like this (as far as how heatblur has written the module) to my knowledge.

@charliefoxtwo charliefoxtwo removed the needs triage The issue has yet to be reviewed by a maintainer label Dec 12, 2024
@Jar72ok
Copy link

Jar72ok commented Feb 22, 2025

Hello,

I found a way around that works for me.

In the F-14.lua file, in the DCS-BIOS script, just add the following line :
defineToggleSwitch("PLT_AUTOPLT_ENGAGE", 22, 3041, 2112, "Autopilot", "Engage autopilot")

PS : Great stuff, I love it.

@Biggus22
Copy link
Author

Given Jar72ok's post here, should I close this issue?

@charliefoxtwo
Copy link
Member

No need to close this issue - I'll close it once code is merged to officially support it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants