[V1.3] Magic Wand Selection Tool

Nov 28 Update: Fixed potential camera lag

Magic Wand Selector
image

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 :slight_smile:

To enable, you can click the button
image

or alternative set up a hotkey!

image

image

139 Likes

That looks pretty useful… nice job on creating it.

6 Likes

Awesome stuff! This will definitely come in handy during large projects.

5 Likes

I could see the Magic Wand Selection Tool becoming really useful in many aspects of game development. Great job on making this! :+1:

4 Likes

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.

3 Likes

The amount of complexity that goes into this is sure to be unappreciated! Mad respect for doing this!

3 Likes

TYSM, this is gonna be super super useful.

2 Likes

really good, an idea if you ever add to it would be an option to only select parts touching on a specific model

4 Likes

You mean appreciated, right?

Besides that, I can see this speeding up work flow. Thank you for the contribution. I’ll test it out later today.

2 Likes

Really nice, I am using it right away!

2 Likes

Updated this plugin with two new features:

  • 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

5 Likes

This plugin lags my studio super hard - even when it’s only installed and not in use.

When installed and not in use it shouldn’t be doing anything, you can read the source

Thanks, this will be awesome to use!

Can you add option to select parts that have same names?
I’ll see it as very helpful.

3 Likes

Sure, just added that feature now

1 Like

Holy… Not gonna lie, I need this so much! Thank you very much for this great plugin/tool. :slightly_smiling_face:

1 Like

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

I really like the look of this! Definitely will be having a look at it.

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)

1 Like