-
Notifications
You must be signed in to change notification settings - Fork 427
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
Comments
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. |
I didn’t realize that worked. I’ll give it a try. Thanks!
Kind Regards,
Josh
On Feb 19, 2024, at 16:53, gallonmate ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub<#1039 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGDJVDCDELN4YWCL665SESDYUPJVNAVCNFSM6AAAAABDFDUFO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGI2DQMRQGQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ...
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:
Other information
The text was updated successfully, but these errors were encountered: