Page MenuHome

Metaball family inherits wrong resolution by deleted metaobject, but new object don`t inherit settings by family
Closed, ResolvedPublic

Description

Broken: 2.8 24.02.2019

How to reproduce:
Add 2 metaballs, change resolution and threshold.

Deselect. Add another one meta. It will appear with default settings.
Change it`s settings a little. Delete it.
Setting will drop to family.

p.s. The same bug at 2.79b: new meta appears with default settings.
Metaballs is great and powerfull, but sadly bugged…

Here is videos:

Event Timeline

Jacques Lucke (JacquesLucke) triaged this task as Needs Information from User priority.Feb 25 2019, 10:46 AM

Can you upload the .blend file, please?

Maybe this is related to D4398.

Yes different resolution for core ball and new capsule saved:
2.79:


2.80:

Vyacheslav (hitrpr) renamed this task from Metaball family inherits wrong resolution by deleded metaobject, but new object do not inherit settings by family to Metaball family inherits wrong resolution by deleted metaobject, but new object don`t inherit settings by family.Feb 26 2019, 10:41 AM

Anything else i can do?

Jacques Lucke (JacquesLucke) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Mar 1 2019, 9:03 AM
Sebastian Parborg (zeddb) triaged this task as Normal priority.Mar 1 2019, 4:53 PM
Sebastian Parborg (zeddb) claimed this task.

I'll take a look at this as I already have worked on metaballs (D4398)

Sebastian Parborg (zeddb) raised the priority of this task from Normal to Confirmed, Medium.EditedMar 1 2019, 5:08 PM

The problem here is more obvious in 2.79. As soon as you change any value of a metaball, all other metaball objects with the same base name has their attributes updated to the same value.

In 2.8, this also happens but the actual update doesn't refresh the tessellation results in this case until a object is deleted.

@Vyacheslav (hitrpr) I'm guessing that the desired behavior is that new objects that share the same base name should copy the initial settings from the already existing metaballs?

The way the settings will not be out of sync.

@Sebastian Parborg (zeddb)
Yes, you are right. New metas should born with settings, inherited by family. It will prevent such problem in 2.8 and 2.79 too

This is now working as it did in 2.79, suggest to resolve the remaining glitches by not attempting to copy settings at all, see: D4456.

Although this is much lower priority since they're not new in 2.8x.