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

Input should be able to have a "speed" applied to it before output #61

Open
JimAnkrom opened this issue Nov 11, 2014 · 0 comments
Open
Labels

Comments

@JimAnkrom
Copy link
Owner

Please pardon my lack of knowledge of terminology for these concepts.

When a user is controlling a physical object's position, the control input should be able to have a 'speed limit' as a transform included with scale/constrain. For some uses of the system, user should not be able to move an object from coordinate A to coordinate B instantaneously, and should have a constraint that limits delta between any given control interval.

A speed limit constraint should be in terms of points-per-second, which is scaled down to the control interval throttle and applied. For any given x/y/z coordinate value, the next value can only be n distance away in 3D space.

This can also be applied as a transformation of orientation-vector-input-to-position-coordinate-output, for use in systems where a vector is not necessarily appropriate.

This feature may later be enhanced with physics concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant