Added GetRigDependencies() method, which returns an array of the root instances of the animation rig
Added new parameter to Destroy(), which allows for the destruction of renderer instances without removing the model
Removed Stop() method
Added getActiveAnimation(), which returns the current Visulie animation playing on an instance, if it exists
Removed the rigDependencies argument for new()
Added loadAnimation(), which loads an animation onto the specified rigDependencies. If an animation is already playing on the rig, that animation will be overridden.
I’m loving the plugin so far, it’s really polished and well worth the money. Amazingly done.
I found a visual bug with dragging keyframes. On an animation longer than 60 keyframes it seems to still snap and clamp to 60 keyframes, which is really hard to work with.
This looks really cool, I always wonder why roblox doesn’t have some kind of animator for VFX or anything in general, I mean are we supposed to manually animate everything via code?
I wonder of moonlite can be used to play moon2 files for VFX similar to this resource.
I cannot say that there are no alternatives to Visulie. However, Visulie is fully integrated with itself and is the only plugin (that I know of) that intentionally supports this kind of playback in a live game.
There are multiple resources that allow you to play MoonAnimator files. Here are some that I see are more prominent:
I’m not too experienced with any of these, as I’ve never used them before. However, from the looks of it, using alternatives like Moonlite is likely to be much less performant. Since your models need to be loaded in advance to play, it might also feel a bit clunky to work with.
That being said, if you prefer to animate using MoonAnimator, these alternatives could be a better fit for you. I created Visulie to improve my own workflow, as I prefer a streamlined experience that doesn’t rely on external workarounds.
Fixed a bug where dragging a keyframe onto another keyframe in a keyframe strip with only two keyframes would cause the strip to disappear and trigger an error (as shown below).
Deleting keyframes used now immediately updates the animation state. It used to only update after you manually render the animation (such as playing or dragging the marker, shown below).
Loving your plugin a HUGE lot so far. Its much better than the standard animation editor.
Just, uhh, having some troubles.
So, I used animation:Play(true) hoping it would break the parts created for the animtaion but thats clearly not happening. I also used animation.Completed:Destroy(), hoping to achieve a similar effect, but to no success.
Can I play the animation on an already exisiting rig? That way I could skip the deletion all together.
Thanks for making such an awesome plugin tho
EDIT: Now I understand it. The :Play(true) destroys the animation, not the rig. Instead, you have to wait for the animation to end and then :Destroy(false) it. Still, I can’t figure out how to animate a rig instead of making one
Also a recomendation: Add function details to the renderer functions by adding comments right above them
Essentially, you provide the Visulie data, where you want to play it, as well as the rig you want to play it on. If your rig has multiple distinct sections, you load it as:
local Animation = Visulie.loadAnimation(data, origin, {RigPart1, RigPart2})
But I’m assuming (from the video provided) that you’re animating a hammer, which is contained under a model. In which case, something like this should work:
local Animation = Visulie.loadAnimation(data, origin, {HammerModel})
I dont really know any of the terminology but I assume that by “Constructor” you mean the comment under the function? It has to be above the function in order to be displayed in code snippets
Constructor basically means something that “creates” something. new() and loadAnimation() are constructors because they “create” an animation object that you can interact with. Instance.new() is a constructor, because it creates an instance. A function like math.min() is not a constructor, because it’s not creating anything.
The comments are there to try to explain what the function itself does, which I hope is clear enough for users to understand!
I’m just now seeing this, and the improvement on the plugin as a whole AND the ability to update old modules to the newer version makes me super happy.
There is however a single issue I’m having with Models inside the animation. Anything outside the model is correctly put in whatever CFrame position it’s scripted to do, but Models always default to 0,0,0.
Example video, it’s set origin is the green part, and 0,0,0 is the red part.
Here’s the old module and updated module if that’s necessary. BothVersions.rbxm (4.5 KB)
It seems like I forgot to mark WorldPivot as a relative value, causing it to not be updated correctly! The issue should be fixed in the new Visulie Renderer (make sure to replace the old module!). Let me know if there is still a problem.
Visulie 1.1.5
Bug Fixes
Visulie Renderer version 0.x.x now has correct version checking
Like I’ve said OFTEN before, this plugin is absolute
However there are some things that could work more uhh, smoothly? Which is why I’ll post some suggestions here. I’ll add/remove some as I discover new things or you actually add some of these :3
Suggestions
Add multi-selection: Its a pain to have to animate every single child's transparency when working with larger anounts of parts. (or just add union support >:( )
Keyframe optimisation: self explanatory. Make it so that practically un-animated properties can get their tracks removed (optimised) using the press of a singular button :) Bossman said this has already been considered (w.i.p.)
List of things that have changed / that have been considered since I made the list:
Proper window scaling (fixed/added)
Union support (technical issues, can't be added)
Replace functions with methods (suggestion wasn't a real suggestion after all)
PascalCase instead of camelCase (camelCase is the norm, I was wrong once more)
Code snippet support (somewhat added, a lot better than before)
Documentation (already present)
Animation priority (won't be added, as it is not really needed. Instead, handle the playing animations by yourself)
Thats enough yapping from me :)
I really enjoy using this plugin and using it has been really fun. Thanks for this awesome resource!
Also a personal note: As a fellow developer I know that these suggestions are just… annoying. Like I understand that this WILL take time, so just know that I don’t want to pressure you into doing all of this in like a day. They are suggestions, not commands
When adding a rig, Parts get not only their own properties, but also those of all of their descendants and siblings.
You can see that multiple parts have multiple CFrame properties as displayed in this video.
Never seen this before, maybe the latest update bugged it?
If this is a bug and not me messing up it requires immediate fixing because it makes Visulie unusable
Additional Debug info:
The 100 different properties are displayed even if not a single object is selected. Selecting objects ADDS the objects’ property until it is swapped away from again
Only happens when inserting large rigs (many parts)
Is unaffected by the part names
Has nothing to do with the present UIs
Another thing to take note of: Pressing “Select all keyframes” in the prompt menu only selects those that belong to the selected Part, implying that the plugin knows which it should show.
.
