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

Campath time smoother™ #223

Closed
z8editing opened this issue Sep 9, 2019 · 1 comment
Closed

Campath time smoother™ #223

z8editing opened this issue Sep 9, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@z8editing
Copy link

I have a feature request that would help alot when using campaths.
Let's say you place four keys with great camera angles but the demo has to be played with a low timescale to get a specific shot.
Most of the time, one of these four keys will have a significant time difference between the n-1 and n+1 key, causing the campath to abruptly stop or going to a different direction. One 'simple' fix for us movie makers, is to re-make the campath trying to separate the keys nicely in time to have a better interpolation.
So my request is this: is it possible to enter a command that would not necessarily make the keys at even time difference, but at least smooth that difference ?
Its basically a matter of moving the keys in time.
That's my idea. No idea if it's possible to achieve but it would be a huge help.

@z8editing z8editing added the enhancement New feature or request label Sep 9, 2019
@dtugend dtugend added this to the HLAE 4 milestone Sep 17, 2019
@dtugend dtugend removed this from the v3.x milestone Feb 13, 2021
@dtugend dtugend closed this as completed Feb 13, 2021
@advancedfx advancedfx locked and limited conversation to collaborators Feb 13, 2021
@advancedfx advancedfx unlocked this conversation Jul 5, 2021
@dtugend dtugend reopened this Jul 5, 2021
@dtugend dtugend closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2022
@dtugend dtugend reopened this Oct 9, 2022
@dtugend
Copy link
Member

dtugend commented May 19, 2024

Hi. Thank you for your suggestion. The implementation of this feature in a reasonable time-frame is currently not realistic for me. After considering that together with issue #896 I am closing this request as not planned for now, since it would block other things I would like to still get done before that. Sorry for the copy pasta.

@dtugend dtugend closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants