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

Execute Planned Maneuver at less than full throttle #42

Open
Starstrider42 opened this issue May 26, 2014 · 1 comment
Open

Execute Planned Maneuver at less than full throttle #42

Starstrider42 opened this issue May 26, 2014 · 1 comment

Comments

@Starstrider42
Copy link
Contributor

Original issue at Cilph/RemoteTech2#240.

TerrorBite wrote:

The EXEC instruction should take the throttle slider into account, and set the throttle to that value when executing the maveuver node (with consequent increase in time before cutting off the throttle).

erendrake pushed a commit that referenced this issue May 30, 2014
-Fixed issue #42
-Fixed issue #44
-Fixed issue with SPUs not passing control source test when flight
launched directly from launchpad/runway
ghost pushed a commit that referenced this issue May 30, 2014
Rewrote AntennaManager;
ghost pushed a commit that referenced this issue May 30, 2014
Rewrote AntennaManager;
Peppie84 referenced this issue in Peppie84/RemoteTech May 31, 2014
Thrustlimiter can now changed and the burn/maneuver time calculation are
now right
@wms wms mentioned this issue Jun 2, 2014
@Starstrider42
Copy link
Contributor Author

This issue was incorrectly marked as closed from recent commits; it will need to be reopened once they are merged. Added wontfix tag as a reminder.

@Starstrider42 Starstrider42 reopened this Jun 16, 2014
@Peppie84 Peppie84 added this to the 1.7.0 milestone Oct 31, 2015
@tomekpiotrowski tomekpiotrowski removed this from the 1.7.0 milestone Apr 23, 2016
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