Adding Metaball when unit scale is smaller than 0.01 seemingly hangs Blender #36438

New Issue

Vincent Akkermans · 2013-08-11T20:58:36+02:00

Vincent Akkermans commented

2013-08-11 20:58:36 +02:00

%%%--- Operating System, Graphics card ---
OSX 10.8, Geforce 650M

- Blender version with error, and version that worked ---

Happens in Blender 2.68a

- Short description of error ---

Blender seems to hang indefinitely in the while loop in polygonize(...) in mball.c
I suspect it doesn't actually hang indefinitely, but that it adds so many cubes that it just takes very long before it is done processing them.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Open any blend file
In the properties window set the unit scale to Metric and the Scale to 0.01 or smaller
Add any type of Metaball
%%%

%%%--- Operating System, Graphics card --- OSX 10.8, Geforce 650M - Blender version with error, and version that worked --- Happens in Blender 2.68a - Short description of error --- Blender seems to hang indefinitely in the while loop in polygonize(...) in mball.c I suspect it doesn't actually hang indefinitely, but that it adds so many cubes that it just takes very long before it is done processing them. - Steps for others to reproduce the error (preferably based on attached .blend file) --- * Open any blend file * In the properties window set the unit scale to Metric and the Scale to 0.01 or smaller * Add any type of Metaball %%%

Vincent Akkermans commented

2013-08-11 20:58:36 +02:00

Changed status to: 'Open'

Jeffrey commented

2013-08-13 02:44:51 +02:00

%%%I managed to generate a metaball using the specified settings by waiting a few minutes. However, viewport performance is awful and it's taking forever to load edit mode. I ended up terminating the process because it just took too long. It looks like it's hanging simply because of the density and sheer size of the object.

Win7 x64 on an AMD Phenom II x6 OCed to 3.6 GHz
Blender also took up about 600 MB of ram during generation of a single default metaball. %%%

%%%I managed to generate a metaball using the specified settings by waiting a few minutes. However, viewport performance is awful and it's taking forever to load edit mode. I ended up terminating the process because it just took too long. It looks like it's hanging simply because of the density and sheer size of the object. Win7 x64 on an AMD Phenom II x6 OCed to 3.6 GHz Blender also took up about 600 MB of ram during generation of a single default metaball. %%%

Bastien Montagne commented

2013-08-19 19:59:18 +02:00

%%%Fixed in r59307, thanks for the report! :)%%%

Bastien Montagne commented

2013-08-19 19:59:18 +02:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2013-08-19 19:59:18 +02:00

Danrae Pray commented

2017-05-03 04:25:09 +02:00

Added subscriber: @spockTheGray-4

Danrae Pray commented

2017-05-03 04:25:09 +02:00

Hi,

I am seeing this happening on a much larger scale in Blender 2.78c. I'm running 2.78c on a box w/ an i7 & gtx 1070.

All you have to do to reproduce is add a metaball, tab on over into edit mode and add another metaball and reduce it's radius to less than 0.150... my box is a beast and it's wigging out hard on this... completely unresponsive and eating up 1.5 GB of memory (I have plenty of RAM so it's not swapping that's causing this)...

Any ideas?

Thanks

Hi, I am seeing this happening on a much larger scale in Blender 2.78c. I'm running 2.78c on a box w/ an i7 & gtx 1070. All you have to do to reproduce is add a metaball, tab on over into edit mode and add another metaball and reduce it's radius to less than 0.150... my box is a beast and it's wigging out hard on this... completely unresponsive and eating up 1.5 GB of memory (I have plenty of RAM so it's not swapping that's causing this)... Any ideas? Thanks

Danrae Pray commented

2017-05-05 01:50:46 +02:00

Just another update in case it helps - I tested and again and noticed that, after you add the second metaball, if you adjust the "radius" param in the left panel to something like say 0.05, it works super snappy. It's only if you "grab" the radius value w/ your mouse and slide left to reduce the value that I see this issue... and even turning off "continous grab" in the Input settings tab in User Prefs does not fix this.

Cheers,
Danrae

Just another update in case it helps - I tested and again and noticed that, after you add the second metaball, if you adjust the "radius" param in the left panel to something like say 0.05, it works super snappy. It's only if you "grab" the radius value w/ your mouse and slide left to reduce the value that I see this issue... and even turning off "continous grab" in the Input settings tab in User Prefs does not fix this. Cheers, Danrae

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

Adding Metaball when unit scale is smaller than 0.01 seemingly hangs Blender #36438