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

Request: turbine spindown table or property support #1039

Open
1 of 3 tasks
Octal450 opened this issue Feb 12, 2024 · 2 comments
Open
1 of 3 tasks

Request: turbine spindown table or property support #1039

Octal450 opened this issue Feb 12, 2024 · 2 comments

Comments

@Octal450
Copy link

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

Current behavior

In the current implementation, the value of n1spindown or n2spindown can only be set in the XML. When realistic values are used.

Requested behavior?

Ability to edit the spindown value at runtime by using either fgfunction or property.

What is the motivation / use case for changing the behavior?
I have a panel state system which quickly sets the aircraft into various states. For startup, set-running + modified spool tables work great, but shutdown takes way too long when realistic values are set into spindown. These changes would allow modification of the spindown value at runtime.

Please tell us about your environment:

  • Windows 11 x64
  • FlightGear 2020.4 (next)

Other information

@gallonmate
Copy link
Contributor

Just a quick note until someone addresses the request: In the meanwhile you could set n1 and n2 directly. I'm not too familiar with scripts, so I'm only assuming an advanced xml script could be written if you still wanted to manually force a faster spinup/down. I do know setting any value from 0 to 100 for n1 and n2 works instantly. And it doesn't break the spinup/down, it just continues from the new values.

@Octal450
Copy link
Author

Octal450 commented Feb 19, 2024 via email

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

No branches or pull requests

2 participants