Cone Mesh Offset bug

  1. What issue are you having? Describe what is happening when the bug occurs. Describe what you would normally expect to occur. The cone mesh offsets itself into a different position.

  2. Does the bug happen 100% of the time? Yes

  3. If so, are there steps that reproduce the bug? Please list them in very high detail. Provide example places that exhibit the bug and provide description of what you believe should be the behavior.

Insert Brick

Insert Cone mesh

Offset the mesh

Move block around.

GIF: http://gyazo.com/1d52b29c41aa32351db2ce3dcc2e8b88
It also happens when you rotate the brick.
GIF: https://gyazo.com/5f49dfca0419ef15e6d8c008ff238a9b
Place File:

  1. Where does the bug happen: Everywhere
  2. Is it level-specific? No
  3. Would a screenshot or video help describe it to someone? Provided above.
  4. When did the bug start happening? I don’t have any idea.
  5. Anything else that you would want to know about the bug if it were your job to find and fix it. When the scale/offset are changing, it stays in the correct position, then offsets into a weird position.

I was having this issue using offset with sword meshes too. After setting the offset to some value, then moving and rotating caused the mesh to jump around.

Here’s a gif I recorded like 2 weeks ago http://i.imgur.com/YF0OPg1.gif
I was going to report, but never got around to it and then forgot. :stuck_out_tongue:

After more testing, it happens to ALL special meshes. This is slightly aggravating.

kisa your two gif links are a duplicate link

also before anyone asks, this is a special mesh from this hat (but yeah it happens with all meshes):

(mesh id http://www.roblox.com/asset/?id=1033714)

the bug started happening exactly at the release of specialmesh offset

also the bug was reported 2 months ago by ripull

Thanks Mael! Fixed that.

Yeah, this puts my whole project on hold until it is fixed. I hope they can fix this.

This is still happening, and it is preventing me from finishing my project. I would appreciate this being fixed quickly. :slight_smile:

Thanks!