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

Lock states persist through power cycling unit, become default for unlocked state #172

Closed
mileshatem opened this issue Jun 29, 2014 · 1 comment
Assignees
Labels
bug Weird outcome is probably not what the mod programmer expected.

Comments

@mileshatem
Copy link

For example, if you lock the throttle to 1, then toggle the kOS unit power off the throttle will remain on full (which by it self is fine in my opinion). However, then if you toggle the power back on the engine still remains on full (again, still fine), but the lock state seems to be reset to thinking it's 0, but not 0....

If you do an unlock all in that state, the engine is still on. If you lock throttle to 0 it shuts the engine off, but then if you unlock all the engine goes back to full on.

Only way I've found to fix it is to lock it to 0, then cycle the power again.

@erendrake
Copy link
Member

Thank you for the report. ill have to check it out!

@erendrake erendrake added the bug label Jun 30, 2014
@erendrake erendrake self-assigned this Jun 30, 2014
@erendrake erendrake modified the milestones: 0.16 Feature list, v0.15.1 Punch List Nov 17, 2014
@erendrake erendrake removed their assignment Nov 17, 2014
@erendrake erendrake self-assigned this Feb 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Weird outcome is probably not what the mod programmer expected.
Projects
None yet
Development

No branches or pull requests

3 participants