-
Notifications
You must be signed in to change notification settings - Fork 13
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
User request: lower gravity range minimum #263
Comments
The lower the gravity limit, the lower the terminal velocity can be. I think we ran into performance issues because there are lots of dots that need to be drawn on the path. I tried to find a paper trail for this, but I couldn't. I'll test things locally with a lower gravity limit and see how it goes. |
@arouinfar, pinging you again on this since it is a high priority for our client again. |
From design meeting today with @arouinfar, @kathy-phet, and myself, we decided to try out a minimum of 1m/s^2. Committed above. This, in correlation to a variety of UI changes we will do to support a max initial speed of 100m/s over in #153, should cover the usability concerns and the feature. |
Projectile Motion is an "if-time" quarterly goal, so marking as on-hold. |
We are working on Projectile Motion as part of the data fluency grants, marking this off hold since we can address it as part of that work. |
Unassigning myself until work on this flavor of Projectile Motion resumes. |
The text was updated successfully, but these errors were encountered: