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

Value curves set to random don't honor the set number of points selected #4803

Open
fone626 opened this issue Sep 10, 2024 · 4 comments
Open

Comments

@fone626
Copy link

fone626 commented Sep 10, 2024

When you set a value curve to random and the number of points to a low number, in my case, 1, the graph shows a randomly chosen flat line, so I expect the value to be randomly chose but stay flat for the length of the effect, but what you actually get is a new random number per frame so your effect jumps around violently.
This appears to affect all the value curves for all the effects (at least all the ones I've tested).

Steps to reproduce the behavior:
Create a new sequence
select any effect, but in my case single strand
set Chase types to static left-right
Then set the value curve on offset to random and then number of points to 1. the graph will show a flat line.
after clicking OK the preview will show a line randomly jumping all over the model, instead of just picking a random location and not moving for the duration of the effect.

@derwin12
Copy link
Collaborator

it recalcs a random number on each frame. Not saying that is right, but that appears to be what the code does.

@fone626
Copy link
Author

fone626 commented Sep 11, 2024

That's what I was guessing, but it doesn't do what it visually says it will do, and if it's going to recalculate at every frame there is no point in having the points setting.
It appears to be working incorrectly to what was intended but if it is then can a setting be added to not recalculate every frame, because it would make it a lot more useful to everyone.

@kylegrymonprez
Copy link
Contributor

I added #4858 which should be something that can be used here. Generate a new timing track and mess with the values to 'look' random. Then this can be pointed to using the timing track in the value curve setting.

@fone626
Copy link
Author

fone626 commented Oct 5, 2024

I added #4858 which should be something that can be used here. Generate a new timing track and mess with the values to 'look' random. Then this can be pointed to using the timing track in the value curve setting.

While useful, a randomized timing track doesn't accomplish what I need for my use case.

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

No branches or pull requests

4 participants