Scene with 71K LEGO parts to support improving Blender 2.80 performance +++ will freeze Blender 2.79 when using Outliner #56902

New Issue

Michael Klein · 2018-09-24T17:52:06+02:00

Michael Klein commented

2018-09-24 17:52:06 +02:00

System Information
DELL XPS 15 9560 GTX 1050 16 GB RAM
Ryzen Threadripper GTX 1080Ti 32 GB RAM
Latest Win10

Blender Version
Broken: blender-2.79.0-git.0a968510bf6-windows64
Worked: (optional)

Short description of error
The attached 2.79 scene shows an import of Collada LEGO data created with the online LEGO editor Mecabricks using 71K bricks (parts). Mecabricks is using a special addon to import Collada data, create instances, assign LEGO shaders with textures. This can be done in 2.79 only actually.

The import of the massive model takes insane 13 hours. This just works when using a layout WITHOUT the Outliner. Just without the Outliner I can save the scene without issues. I also can render the scene even on a GTX 1080Ti with 11 GB VRAM. In 2.79 the rendering starts nearly immediately.

When I import the data with an opened Outliner Blender will be trapped in a heavy delay and you can't do anything anymore. Blender is completely frozen. I assume the reason is a refresh of the Outliner everytime you click the mouse. There is no change to do anything. Even switching to the Compositing layout by CTRL-left arrow will not work.

Loading the scene into 2.80 shows that the actual 2.80 build has fixed this issue due to the new Outliner using Collections. The overall performance is good for such a big model. Even my XPS 15 with 16 GB RAM can deal with it. The difference now is that switching between viewport modes will take longer than in Blender 2.79 and rendering needs a very long pre-calculation what doesn't happen in the Blender 2.79 preview. But this is totally fine.

When I turn off Collections in the filter of the new Outliner I will experience the same issue again. Blender is not responding (blue mouse pointer wheel) and becoming useless. Same happens when I try to switch the layout.

Attached you'll receive both scenes. I hope this helps to identify issues and maybe fix a serious bottleneck of Blender compared to other 3d apps: Complexity.

To compare this with MODO. I have also a workflow to render LEGO in MODO. The Collada Importer of MODO is extremely fast. The whole model in importeted in da few minutes incl. instances. I tried the Collada Importer of Blender and had to kill the process after half an hour. I assume it will take as along as the Mecabricks addon.

In MODO the overall performance is really good. Fast import. No heavy delays. Good viewport performance.

If you have further questions or need a hand just feel free to contact me: lego@renderbricks.com.

Keep up the brilliant work. We love Blender. My studio has replaced Softimage with Blender in 2016 after taking a look into other 3d apps. ;-)

Exact steps for others to reproduce the error
Load the Blender 2.79 scene into 2.79 and open the Outliner. Bad idea.
Load the Blender 2.80 scene into 2.80 and turn off Collection in the Outliner filter. Bad idea.

RB0009_Super_Star_Destroyer_v01_71K_Models_for_Blender_Dev.zip

**System Information** DELL XPS 15 9560 GTX 1050 16 GB RAM Ryzen Threadripper GTX 1080Ti 32 GB RAM Latest Win10 **Blender Version** Broken: blender-2.79.0-git.0a968510bf6-windows64 Worked: (optional) **Short description of error** The attached 2.79 scene shows an import of Collada LEGO data created with the online LEGO editor Mecabricks using 71K bricks (parts). Mecabricks is using a special addon to import Collada data, create instances, assign LEGO shaders with textures. This can be done in 2.79 only actually. The import of the massive model takes insane 13 hours. This just works when using a layout WITHOUT the Outliner. Just without the Outliner I can save the scene without issues. I also can render the scene even on a GTX 1080Ti with 11 GB VRAM. In 2.79 the rendering starts nearly immediately. When I import the data with an opened Outliner Blender will be trapped in a heavy delay and you can't do anything anymore. Blender is completely frozen. I assume the reason is a refresh of the Outliner everytime you click the mouse. There is no change to do anything. Even switching to the Compositing layout by CTRL-left arrow will not work. Loading the scene into 2.80 shows that the actual 2.80 build has fixed this issue due to the new Outliner using Collections. The overall performance is good for such a big model. Even my XPS 15 with 16 GB RAM can deal with it. The difference now is that switching between viewport modes will take longer than in Blender 2.79 and rendering needs a very long pre-calculation what doesn't happen in the Blender 2.79 preview. But this is totally fine. When I turn off Collections in the filter of the new Outliner I will experience the same issue again. Blender is not responding (blue mouse pointer wheel) and becoming useless. Same happens when I try to switch the layout. Attached you'll receive both scenes. I hope this helps to identify issues and maybe fix a serious bottleneck of Blender compared to other 3d apps: Complexity. To compare this with MODO. I have also a workflow to render LEGO in MODO. The Collada Importer of MODO is extremely fast. The whole model in importeted in da few minutes incl. instances. I tried the Collada Importer of Blender and had to kill the process after half an hour. I assume it will take as along as the Mecabricks addon. In MODO the overall performance is really good. Fast import. No heavy delays. Good viewport performance. If you have further questions or need a hand just feel free to contact me: lego@renderbricks.com. Keep up the brilliant work. We love Blender. My studio has replaced Softimage with Blender in 2016 after taking a look into other 3d apps. ;-) **Exact steps for others to reproduce the error** Load the Blender 2.79 scene into 2.79 and open the Outliner. Bad idea. Load the Blender 2.80 scene into 2.80 and turn off Collection in the Outliner filter. Bad idea. [RB0009_Super_Star_Destroyer_v01_71K_Models_for_Blender_Dev.zip](https://archive.blender.org/developer/F4807456/RB0009_Super_Star_Destroyer_v01_71K_Models_for_Blender_Dev.zip)

Michael Klein commented

2018-09-24 17:52:06 +02:00

Added subscriber: @Renderbicks

Michael Klein commented

2018-09-24 21:03:54 +02:00

Here's a workaround to bring back performance after using "Make Dupli-Face". In case I would like to animate all bricks this is not a solution but to build massive static objects and environments like a city. I would love to see an overall better handling of my attacked scenes of course ... in the future.

RB0009_LEGO_MOC_Super_Star_Destroyer_71K_Bricks_Optimzed.mp4

Here's a workaround to bring back performance after using "Make Dupli-Face". In case I would like to animate all bricks this is not a solution but to build massive static objects and environments like a city. I would love to see an overall better handling of my attacked scenes of course ... in the future. [RB0009_LEGO_MOC_Super_Star_Destroyer_71K_Bricks_Optimzed.mp4](https://archive.blender.org/developer/F4808643/RB0009_LEGO_MOC_Super_Star_Destroyer_71K_Bricks_Optimzed.mp4)

Bastien Montagne commented

2018-09-30 18:20:10 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2018-09-30 18:20:10 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2018-09-30 18:20:10 +02:00

Bastien Montagne self-assigned this 2018-09-30 18:20:10 +02:00

Bastien Montagne commented

2018-09-30 18:20:10 +02:00

Thanks for the report, but this is a bug tracker, not a feature request service. Blender is not designed to handle well tens of thousands of objects, that’s a known limitation. Improvements are always possible, but that’s TODO, no bug. :)

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

Scene with 71K LEGO parts to support improving Blender 2.80 performance +++ will freeze Blender 2.79 when using Outliner #56902