This is a genuinely good plugin and I’ve started putting it to use.
However, could you please remove all these stars and credits everywhere? They are quite obnoxious and make the plugin feel like a cheap product in terms of quality.
One more request, could you save the user’s Selection before they press Play on the plugin and then restore it after clicking Stop? I’ve included a use case example in the video below. I’m trying to play with a ParticleEmitter’s properties but due to the way the plugin works it makes me deselect the ParticleEmitter when I click Play on the plugin and then I have to re-open the entire model hierarchy in the explorer again to select the ParticleEmitter.
Amazing plugin! Many things I do just wouldn’t be possible without it!
I’m making a little thing like this right now, and I must say testing the technicalities was far easier thanks to this!
I do have one issue though. I get prints in the output which causes a bunch of lag even though I have no print statements in my code. I reckon this could be a potential bug in the plugin.
Nonetheless, this is an amazing tool and I’m definitely going to use it for my projects from now on!
I believe the printed messages I get are old print statements I used to test that I removed.
They’re not present in the script, but I see them in the output. I notice they’re being printed 900-1000 times each time I use the effect. This mass output could potentially cause the lag, especially since it happens right when the prints fire, however, my visual is mediocrely optimized so it could just be an issue on my part.
I’m glad you noticed my problem, and I hope that if you attempt to fix it, the solution will be easy to find.
Thanks!
I am not sure. But this motivates me to make the plugin even more reliable and safer than before. I’ll be working on a technique to reduce memory leaks and such.
I have redone the “running code” part of this plugin by taking advantage of the new Plugin RunContext. This will hopefully fix a lot of memory leaks that could occur in your script. VspLib.AddInstance still might be necessary to do, but the plugin will try to do it for you if possible. AddConnection and AddThread will now be unnecessary. The plugin will give you warnings in the output if you’re still using them.
I also attempted to fix the whole requiring modules problem. For those who don’t know, when you require a ModuleScript in your code in this plugin (or any other code-based plugin for that matter) and decide to change the source code of that ModuleScript, the plugin won’t notice the changes you’ve done to that ModuleScript. This is something I cannot fix (with ease) and Roblox confirmed that this is intentional behavior. So I am sorry for that. If you really want your VSP Code to use your latest module versions, just readd those ModuleScripts to your game (so the engine knows that it’s a different ModuleScript).
Thanks for the feedback!
Please share anything cool you’ve made with this plugin!
Oh, then sorry. If you drag the slider all the way to the left or right, it becomes impossible to set the physics speed back to the default of 1x (closest you can get is 1.05x i think). Same for the iteration time.
VFX Scripter Pro v1.3.4
