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

Stages of Success #1

Closed
ad1217 opened this issue Jul 30, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@ad1217
Copy link

commented Jul 30, 2014

One of the things that DebRefund has that this doesn't is stages of success (e.x. Green is < 6 m/s and gives 90%, Yellow is < 10 m/s and gives 75%, Red is > 10 m/s and gives 0%). A configurable version of this would be nice.

I was working on it, but I don't know C#, so it could take a while.

@magico13

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2014

I have concerns about adding too many features that are the same as DebRefund, so I'm not quite saying no to this, just a bit wary of it. DebRefund's speeds appear to be configurable in the settings.txt file, however. Adding similar functionality would not be difficult, but if I do it will have to be sufficiently different to not just be a copy. (ie, a return percent between 100% for a slow landing of 3 or 4 m/s, to a 25% for 12 m/s or something along those lines, with the return directly proportional to the landing speed.)

@ad1217

This comment has been minimized.

Copy link
Author

commented Jul 30, 2014

I was thinking about that earlier and kind of like it better. It just seems
that "damage" (terminal velocity) should affect the return more than just
success/failure.

On Wed, Jul 30, 2014 at 11:21 AM, magico13 notifications@github.com wrote:

I have concerns about adding too many features that are the same as
DebRefund, so I'm not quite saying no to this, just a bit wary of it.
DebRefund's speeds appear to be configurable in the settings.txt file,
however. Adding similar functionality would not be difficult, but if I do
it will have to be sufficiently different to not just be a copy. (ie, a
return percent between 100% for a slow landing of 3 or 4 m/s, to a 25% for
12 m/s or something along those lines, with the return directly
proportional to the landing speed.)


Reply to this email directly or view it on GitHub
#1 (comment)
.

"There has grown up in the minds of certain groups in this country the
notion that because a man or corporation has made a profit out of the
public for a number of years, the government and the courts are charged
with the duty of guaranteeing such profit in the future, even in the face
of changing circumstances and contrary to public interest. This strange
doctrine is not supported by statute or common law. Neither individuals nor
corporations have any right to come into court and ask that the clock of
history be stopped, or turned back." -Robert A. Heinlein

magico13 added a commit that referenced this issue Aug 2, 2014

1.2.0.0: Implemented Variable Recovery Rate, updated API, made non-ab…
…lative shielding act as 400 ablative shield, blizzy toolbar support. This closes issue #1.
@magico13

This comment has been minimized.

Copy link
Owner

commented Aug 2, 2014

Implemented as a second recovery model (Variable Recovery Rate) where if the velocity is between two cutoffs then the recovery percentage is determined by a quadratic following (where x0 is the low velocit cutoff and x1 is the high velocity cutoff) av^2+bv+c = recovery with a = (-100)/(x1^2-2_x0_x1+x0^2), b = -2_a_x0, and c = a*x0^2+100 (giving 100% return at v=x0 and 0 return at v=x1). The default uses cutoffs of 6m/s and 12 m/s resulting in this curve:
sr-recoverycurve

With that, I'd say this issue can be closed :)

@magico13 magico13 closed this Aug 2, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.