You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the project you are working on: Projects that use AnimationPlayer node a lot.
Describe the problem or limitation you are having in your project:
I was on the fence submitting the track visualization as bug, because it leads to false judgement and shows stuff that is not actually happening:
When you change alpha or color between two keys, the track accurately visualizes the change (see alpha -> white -> alpha -> red transition below). However, when you change Update Mode, Interpolation Mode or Easing, the track visualization dos not reflect the setting, which makes it very easy to oversee a mistake, or simply confuse people. This makes the track visualization imho more harmful than helpful:
Describe how this feature / enhancement will help you overcome this problem or limitation:
Make the track reflect the Update Mode, Interpolation Mode or Easing setting as well, or remove the track visualization all together.
Show a mock up screenshots/video or a flow diagram explaining how your proposal will work:
See above how it currently works. If the track visualization would also reflect Update Mode, Interpolation Mode or Easing setting, we would not see a gradient between keys on the track once I changed the setting from "linear" to "Nearest" (Interpolation Mode), or "Linear" to "Zero" (Easing)
Describe implementation detail for your proposal (in code), if possible:
Impossible.
If this enhancement will not be used often, can it be worked around with a few lines of script?:
Not that I would know.
Is there a reason why this should be core and not an add-on in the asset library?:
It would lead to less confusion and potential error for all users of the AnimationPlayer. Don't download anti-confusion medicine in the library, people!
The text was updated successfully, but these errors were encountered:
golddotasksquestions
changed the title
AnimationPlayer track: track previsualisation should also visualise Update Mode, Interpolation Mode or Easing
AnimationPlayer track: track visualisation should also visualise Update Mode, Interpolation Mode or Easing
Dec 7, 2019
golddotasksquestions
changed the title
AnimationPlayer track: track visualisation should also visualise Update Mode, Interpolation Mode or Easing
AnimationPlayer track: track visualisation should also visualize Update Mode, Interpolation Mode or Easing
Dec 7, 2019
Describe the project you are working on: Projects that use AnimationPlayer node a lot.
Describe the problem or limitation you are having in your project:
I was on the fence submitting the track visualization as bug, because it leads to false judgement and shows stuff that is not actually happening:
When you change alpha or color between two keys, the track accurately visualizes the change (see alpha -> white -> alpha -> red transition below). However, when you change Update Mode, Interpolation Mode or Easing, the track visualization dos not reflect the setting, which makes it very easy to oversee a mistake, or simply confuse people. This makes the track visualization imho more harmful than helpful:
Describe how this feature / enhancement will help you overcome this problem or limitation:
Make the track reflect the Update Mode, Interpolation Mode or Easing setting as well, or remove the track visualization all together.
Show a mock up screenshots/video or a flow diagram explaining how your proposal will work:
See above how it currently works. If the track visualization would also reflect Update Mode, Interpolation Mode or Easing setting, we would not see a gradient between keys on the track once I changed the setting from "linear" to "Nearest" (Interpolation Mode), or "Linear" to "Zero" (Easing)
Describe implementation detail for your proposal (in code), if possible:
Impossible.
If this enhancement will not be used often, can it be worked around with a few lines of script?:
Not that I would know.
Is there a reason why this should be core and not an add-on in the asset library?:
It would lead to less confusion and potential error for all users of the AnimationPlayer. Don't download anti-confusion medicine in the library, people!
The text was updated successfully, but these errors were encountered: