Question mostly addressed to Brecht, but maybe somebody else could explain me why motherball's scale should have such behaviour
Avoiding out of memory error wasn't the main reason of making polygins size independent from motherball scale: why metasurface is changing when i'm scaling one of metaballs but not changing when i'm scaling anothers. Maybe it's established behaviour of metaballs for artsis, but i haven't heard about motherballs before finding out how mballs works in Blender, so such behaviour confused me. And also the behaviour confused Matt Ebb. And not sure which type of instanciating you're talking about. This behaviour is totally unusable for particle systems, i.e. Brecht Van Lommel wrote: > Revision: 30031 > > http://projects.blender.org/plugins/scmsvn/viewcvs.php?view=rev&root=bf-blender&revision=30031 > Author: blendix > Date: 2010-07-06 13:44:45 +0200 (Tue, 06 Jul 2010) > > Log Message: > ----------- > Revert revision 29735: > > Fix #22051: crash when scaling parent metaball. Keep the constant resolution > for any motherball's scale. > > This avoids running out of memory when scaling the metaball down, but there's > a reason it depends on this scaling, for example for instancing it's more > useful to have this. It also doesn't really solve the problem but only moves > it, > it's still possible to run out of memory with different setups/scales. > > Revision Links: > -------------- > > http://projects.blender.org/plugins/scmsvn/viewcvs.php?view=rev&root=bf-blender&revision=29735 > > Modified Paths: > -------------- > trunk/blender/source/blender/blenkernel/BKE_mball.h > trunk/blender/source/blender/blenkernel/intern/mball.c > > _______________________________________________ > Bf-blender-cvs mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-blender-cv -- With best regards, Sergey I. Sharybin _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
