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:
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.