WedgePart creates an annoying amount of decimals, also causing super thin gaps between parts

[anon81993163]

This bug is freakin’ me out, it occurred today 16th May, 21:00 PM CEST. It makes super thin gaps, despite the numbers of size and position being whole numbers. Moving the WedgePart causes it to bump up decimals on position property of it.

I’m surprised that the bug happens rarely for me, however, it is inconsistent. Some other WedgeParts seems fine while some of them are affected. The reproduction is unknown, but I think resizing it into a specific size will make it occur.
Apparently there’s a temporary fix, it is by creating a new WedgePart and replace the old one. And I think using CFrame.new(0,0,0) fixes the problem temporarily.

This bug only occurs upon building. Yikes, I don’t really know how I exactly reproduced that. I have a Repro file here:

ReproBug.rbxl (14.6 KB)

And also a screenshot of it:

Just look close up on the edge, this bug also affects users who’re trying to make unions. The bug has been reportedly found by another user; [USERNAME NOT FOUND]. He spotted it by making unions out of the parts, then turned them negative. The faces between the parts were visible.

Thank you for reading!

TL;DR, bug makes odd decimals on WedgeParts.

[Veldaren]

I believe your issue is solely caused by Floating Point errors.

@anon81993163

It makes super thin gaps, despite the numbers of size and position being whole numbers

Whole numbers won’t guarantee a precise position/orientation/size. You can have it at (4, 5, 5) when in fact those numbers are (4.00058925, 5.0003747953, 5.0003994736), and Studio won’t display them as such because it only reaches to 1/1000th precision. Those imperfections are often caused by moving the part, resizing it or rotating it manually, via drag handles.

There is a way to fix those “fake numbers”, to make them more precise to what they appear to be in studio:

• Copy the number

• Type in 0,0,0 (or double “,” for short; this is just to make the original number different than itself, it could as easily be just 5, 6, 6 [referring to the previous 4, 5, 5])

• Paste the number back

This should fix all numbers to be as precise as possible. It should also fix your WedgePart issues.

[anon81993163]

As I suspected, there were annoying decimals hidden within those whole numbers(rounded).

Thanks!