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

Implement time-variant transforms #15

Open
hdamron17 opened this issue Aug 13, 2020 · 0 comments
Open

Implement time-variant transforms #15

hdamron17 opened this issue Aug 13, 2020 · 0 comments
Labels
enhancement New feature or request priority-low Low priority

Comments

@hdamron17
Copy link
Owner

Similarly to TF2, we want to add a second key for each transform which allows transforms to have different values over time. Some ideas for the implementation details:

  • We would still have the option to getLatestTransform which takes the most recent version in addition to a time-dependent version.
  • For specific times, we would take the nearest past transform and the nearest future transform then interpolate between the two. Possibly there is an optional threshold for how far away the transform can be.
  • We need to add exceptions for requests which are connected at some point but not at the time requested.
  • It may be helpful to allow range-based requests (e.g. less than 20 seconds ago)
  • We would need convenient deletion methods to help people not cause memory leaks. Also the option to automatically delete transforms which are a certain amount older than the newest frame (this is how TF2 does it).
  • Although caching probably wouldn't be very useful for older transforms, we could have it for the latest transform.
@hdamron17 hdamron17 added enhancement New feature or request priority-low Low priority labels Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low Low priority
Projects
None yet
Development

No branches or pull requests

1 participant