[Plugin] Edge Bevel - Easily bevel the edges & corners of parts!

What I meant is that you can’t edit the individual bevel wedge components. With real-time CSG, you’re essentially “cutting out” portions from an existing part rather than creating entirely new parts (which you could then edit and change the color, material, etc… of).

Yeah, if that ever comes out I will consider it. Sounds cool!

Are there any known issues with detecting corners? Using it seems to sometimes detect them other times it doesn’t, it mostly doesn’t, though.

https://gyazo.com/cef4848cfd523b7f3cfcb61bc1e90bdd

https://gyazo.com/767232600a805ece94b025afbb18b8f8

Edit: I’m guessing it’s the scale? At a larger scale it works perfectly

1 Like

Hey there, sorry for the late reply

Looks like it’s the scale? Might be an issue with the raycasting, I will take a look!

2 Likes

I’ve not got around to contributing my fixes, but from memory, yes it’s the scale. The way the raycast positions are calculated isn’t quite right and so at small scales it misses the corners.

1 Like

Why??? , Where you live Roblox developer?

If you modify the Check function inside the DetectCornerOnSide function in the EdgeBevel script, this ought to fix it:

local params = RaycastParams.new()
params.FilterDescendantsInstances = filterObjects
params.FilterType = Enum.RaycastFilterType.Exclude
	
local direction = math.sign(sideOffset)
local offsetDistance = radius + 0.1
local startCF = cf + cf.RightVector * (sideOffset + direction * offsetDistance) + cf.LookVector * radius / 4 + cf.UpVector * radius / 4

-- Adjust the direction to cover the original distance plus the offset
local direction = cf.RightVector * -(direction * (radius + offsetDistance))

	
-- Perform the blockcast from the adjusted starting position
local result = workspace:Blockcast(
	startCF,
	Vector3.new(radius / 2, radius / 2, radius / 2),
	direction,
	params
)

if result and result.Instance then

There are two changes:

  • Sizing the block of the block cast based on the size of the radius (previously hard coded at 0.5, so I think this is the crux of why it broke before - corners smaller than 0.5 will normally be missed as the block often hits something else before the corner).
  • Dividing the radius by 4 rather than 2 when calculating startCF (I’m not 100% sure if this is required)

Unrelated to this, I’ve also done other changes locally that add support for generating the curved corner edges with UnionParts rather than meshes (which then allows the object with the beveled corners to be unioned and used for subtraction etc). I personally find this much more useful than the meshes, though it is a little more complex.

1 Like

Hi everyone, I have released a fix for corners at small scales. Thank you to @Ed_Win5000 for contributing to the changes.

Please update to 1.4.1 to see the fix in action! @Kiriixer

2 Likes

If you want to share them with me feel free to DM me!

1 Like