You can easily control the type of waypoint interpolation (Linear, Bezier, Hermite), the springs properties (Speed, Dampening, Force, Mass), length, framerate, and point count.
The focus of this project of mine was to implement splines into cutscenes while retaining every feature that has a genuine impact on a scene. The last feature I was going to implement was Shake control for individual keys but I decided against it as the size of the plugin was becoming too much for my own Studio to properly hide within the confines of the app and the feature was always going to be an integration of someone else’s code.
tldr it is easier, fits in with your studio theme much nicer, has unique features every other plugin doesn’t have, and will probably be a crowd favorite among animators (considering i took the time to rewrite the timeline & keyframe system)
Looks cool but the minimal size is way too big, I really hate it when stuff like this obstructs 80% of my screen.
Also the way of making keyframes is a bit weird imo, Rather than choosing a type then making the keyframe, I’d rather be able to right click keyframes to change their settings after.
Also there doesn’t seem to be any keyboard binds so i have to manually move my mouse and click for a new keyframe. (Unless i just can’t find the bind)
Also it’s kind of annoying that i can’t create keyframes when one is selected, So i have to click somewhere in the timeline just to create a new keyframe every time i make a new keyframe.
The interface looks really good though, Settings could use a drop-down menu if you don’t want a right click settings menu, And the cutscene creation at the top can be hidden as we don’t use it during cutscene creation.
Thanks for the reply and the criticism however I have some of mine to your points that I think you’ll enjoy reading about.
Plugins have no control over the right click menu unfortunately so I cannot actually implement that, especially since it would have to be inside the GUI the plugin already uses and would look clunky if I did that.
Choosing a type and then making a keyframe is essential to UI as I found there were a couple of issues with letting the type be freeroam:
without it locking the type the difference between selecting and unselecting a keyframe would have the GUI essentially be the same between both possibilities and caused me to have more accidents than I wanted
by letting you change the type I would have to clear out all previous point data because the types require different amounts of points to function, aka more accidents.
I am willing to add keyboard binds and will likely do so in the following days when I have free time, they were an oversight on my part and you are entirely right in wanting them built into the plugin.
…And the idea of a dropdown style settings system isn’t a bad one but I don’t really see how I could implement that while retaining the absolute seamless nature of the plugin’s current GUI. An alternative idea is that I shrink the size of the features as a whole, besides a few that need to be a certain size, so that it doesn’t require such a large minimum plugin size.
Why would having your own right click menu be clunky? Either way a keybind leading to seperate menu with settings would work too, I just think the plugin looks really messy and cluttered right now.
With this i can only assume you mean my point where i told you about having to click in an empty spot in the timeline before it let me create another keyframe, If so you could just fix this by only allowing you to place a keyframe on your timeline cursor when it isnt on another keyframe.
I think having something like the roblox dropdown, With categories such as “Keyframe Data” (Holding the type and points.), “Keyframe Animation” (Used for the tweening.), Could work just fine
It could look something like this
(Great artist)
And for convience +/- could swap between the categories without having to click anything.
It would still feel like roblox and look good, Yet imo be a lot cleaner and easier for the eyes.
This looks really good! I’m probably still going to use Code Otaku Cutscenes plugin for a lot of stuff since I’ve already gotten used to how it works but I can’t wait to start using this too! I really like the design, I love plugins that just look built-into Roblox lol.
EDIT: @len_ny are there gonna be any future updates? Just noticed it was last updated in September last year. And is it ever going to be open source? I always like to peek at the source code of plugins before buying and installing them (if they’re open source) to see how it’s structured and all that. But even if not, good job making this!
To answer your first question, it will receive updates, and I have plans to update it when I’ve released my current project. It does need some basic bug fixes, which won’t impact your cutscene development, and it could use some feature additions. I feel the visualization of the cutscene is still too simplistic, and ugly. I hope to fix this in the future, but only when I need the plugin. Unfortunately, I don’t currently have any specific ideas for improvement because, as you mentioned, it has been quite some time since I’ve visited this plugin’s source. Expect to see more updates sometime this year, that’s a promise!
To answer your second question, I’m torn because on the one hand, I want this to be a product of my own creation but on the other, it likely wouldn’t hurt sales and would open the door for better plugins to be made from it. I’ll need the rest of the day to think about this, you really struck a chord with me!
I’ll most likely add CameraShake to the plugin but it will require a secondary timeline, and different options (more in like with the CameraShake module itself). I’d plan on making it possible to switch between a Cutscene development mode (the mode that’s already released) and a Shake development mode (the theoretical future mode designed exclusively for CameraShake). Both modes would operate on the same scene, and timeline, but unlike the Cutscene mode the Shake mode would operate like you were emitting Shake at the keyframe.
I just wanted to make it aware that I plan on improving this plugin with time and love the support everyone’s given me!
