Page MenuHome

MetaBall mesh convert to mesh leaves original metaball as filled empty behind.
Closed, ArchivedPublic

Description

System Information
Windows 10 Nvidea 630M (i render on CPU)

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
2.77

Short description of error

Exact steps for others to reproduce the error
I create something using many metaballs, i'm using CTRL+Shif+D to draw a 3d volume shape

(like spray cream volume , ...hey that would be nice for a new sculpting tool !! ).

Next i convert the metaball to a Mesh, then i assign a simple cycles material to this mesh object.
One would think the shape would get that single collor right ?.
It became a weird patern mixing up background color and the assigned color.
And this pattern differes in viewport and rendererd image.

  • on seccond observation however.

it seams that with mesh convert the metaballs dont get destroyed, and leave a ghost object behind.
This object doesnt contain the metaball like mess in edit mode, but still the outliner and the filled material.
Strangly these ghostballs cannt be assigned different materials either.

I think deletion of the ghost balls would solve this.

Details

Type
Bug

Event Timeline

Peter Boos (PGTART) set Type to Bug.
Peter Boos (PGTART) created this task.
Peter Boos (PGTART) raised the priority of this task from to Needs Triage by Developer.

can confirm this.
metaballs have the concept of 'families' (see the manual)
prior to rB9794facab393e486cc7bb3ad77b0ee70cd39e890, all metas in a scene (not only the ones in the same family) would be removed on conversion (which was a bug), now only the selected metas plus the 'basis' /'motherball' are removed, leading to the unexpected behaviour described in the report [happening if not all members of a family are selected].
I guess the solution would be to flag all members of a metaball-family for removal (cause all of them contribute to the resulting converted mesh)
Will see if I can post a patch in a bit...

Bastien Montagne (mont29) triaged this task as Confirmed, Medium priority.

Tsst, not regression actually, this is a one year old commit :P

Checked logic here and think its quite OK as-is.

  • Select all meta's and convert, will remove and convert to mesh.
  • Select mother-ball and convert will give you the mesh., and leave meta's.

The reason for this is unselected metas may be on other layer, hidden... or for what ever reason an object you dont want to delete.

Think its best if we don't delete objects outside the selection.