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

New Issue

Vyacheslav Kobozev · 2019-02-25T01:20:03+01:00

2019-02-25 01:20:03 +01:00

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:
2019-02-25_03-09-42.mp4
2019-02-25_03-16-23.mp4

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: [2019-02-25_03-09-42.mp4](https://archive.blender.org/developer/F6707647/2019-02-25_03-09-42.mp4) [2019-02-25_03-16-23.mp4](https://archive.blender.org/developer/F6707668/2019-02-25_03-16-23.mp4)

Vyacheslav Kobozev commented

2019-02-25 01:20:04 +01:00

Added subscriber: @Vyach

Jacques Lucke commented

2019-02-25 10:46:46 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-02-25 10:46:46 +01:00

Can you upload the .blend file, please?

Maybe this is related to D4398.

Can you upload the .blend file, please? Maybe this is related to [D4398](https://archive.blender.org/developer/D4398).

Vyacheslav Kobozev commented

2019-02-26 10:41:12 +01:00

Yes different resolution for core ball and new capsule saved:
2.79: Metaball 279.blend
2.80: Metaball 280.blend

Yes different resolution for core ball and new capsule saved: 2.79: [Metaball 279.blend](https://archive.blender.org/developer/F6716198/Metaball__279.blend) 2.80: [Metaball 280.blend](https://archive.blender.org/developer/F6716199/Metaball__280.blend)

Vyacheslav Kobozev changed title 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

2019-02-26 10:41:39 +01:00

Vyacheslav Kobozev commented

2019-03-01 02:56:16 +01:00

Anything else i can do?

Sebastian Parborg commented

2019-03-01 16:53:21 +01:00

Added subscriber: @ZedDB

Sebastian Parborg self-assigned this 2019-03-01 16:53:21 +01:00

Sebastian Parborg commented

2019-03-01 16:53:21 +01:00

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

I'll take a look at this as I already have worked on metaballs ([D4398](https://archive.blender.org/developer/D4398))

Sebastian Parborg commented

2019-03-01 17:08:55 +01:00

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.

@Vyach 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.

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. @Vyach 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.

Vyacheslav Kobozev commented

2019-03-02 02:34:06 +01:00

Removed subscriber: @Vyach

Vyacheslav Kobozev commented

2019-03-04 06:12:54 +01:00

Added subscriber: @sebastian-4

Vyacheslav Kobozev commented

2019-03-04 06:12:54 +01:00

@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

@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

Sebastian Parborg commented

2019-03-05 21:02:47 +01:00

I've uploaded a fix: D4453

I've uploaded a fix: [D4453](https://archive.blender.org/developer/D4453)

blender-admin commented

2019-03-06 03:16:48 +01:00

This issue was referenced by b2889c7cf1

This issue was referenced by b2889c7cf122a5bc6b028470c3c3800637e780ab

Campbell Barton commented

2019-03-06 03:41:22 +01:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2019-03-06 03:41:22 +01:00

Campbell Barton commented

2019-03-06 04:14:05 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2019-03-06 04:14:05 +01:00

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.

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](https://archive.blender.org/developer/D4456). Although this is much lower priority since they're not new in 2.8x.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

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