Spent a few hours today making a magic wand selection tool that works similarly to magic wand selection tools in photo editors, since we can perform faster collision/intersection queries now
This was made as a placeholder until roblox hopefully makes their own
It supports selecting only parts that intersect, or also parts that are touching but don’t intersect!
note - It won’t select invisible objects, but you can choose to make invisible objects considered while scanning if you’d like(I don’t know why you’d want to do this but you can :D)
Here’s me quickly recoloring a road and some parts of a building
I am in awe at how simple this is for you to explain and produce. This will be amazing for large, complex builds and such. I thank you very much for this.
a whitelist button where you can specify if you want to only select parts under a specific instance, select an instance and hit the SET button, to remove a whitelist click it again or select nothing
the ability to extend the collision check size to include parts that are nearby but not touching or intersecting
I took a cursory look at the source code, and while I have no knowledge of plugins I suspect the issue lies on line 120 of the plugin script, where you call the Plugin:SetSetting method on Camera.Changed. Every time I move the camera with your plugin installed (not enabled) I get huge spikes in my microprofiler. Deleting the camera seems to solve the issue, so while I don’t have the time to repackage your plugin and test my hypothesis, I’m pretty confident it’s this.
Here’s a link with an example of the microprofiler spikes, and them disappearing upon deletion of the camera: https://streamable.com/n8mi97
Yeah I figured, I had to do this to get when the viewport size changed. For whatever reason, GetPropertyChangedSignal on viewport size wasn’t working in studio(for either plugin mouse or camera)
