Open SamuelAsherRivello opened 3 months ago
In my opinion such bool
things looks ugly without better inspector which should hide array if UseSameDuration == true
and show single input field instead, still under the hood having same array of durations as long as those SOs are just authoring in-editor only data.
As I mentioned in other issues I've implemented NSprites-Foundation as minimal example of how NSprites could be used. Though I was thinking about to do what you suggest to do numerous of times, so I will do this eventually, after more important changes I have plans to do.
I have a Unity 6 project with this setup...
... and I pulled ...
... into my project with success. Great work!
PROBLEM:
I notice that the length of
FrameDurations
on theSpriteAnimation
object must match the number of sprites resulting from theFrameCount
values of theSpriteAnimation
object.This is manageable to manually keep in sync.
WORKAROUND:
One solution would be to support the current workflow AND support having exactly one value (and perhaps a boolean of 'UseSameDuration=true') for the
FrameDurations
on theSpriteAnimation
object. The system would reuse that one value across all frames, which by the way is probably the primary use case.RESULTING CONSOLE LOG