Export instance geometries to Sketchup #51593

New Issue

Luca Saiani · 2017-05-23T11:06:03+02:00

Luca Saiani commented

2017-05-23 11:06:03 +02:00

Hi,

according with this page Sketchup needs <instance_node> and <library_nodes> section for instancing geometries.

Blender Collada Exporter does different and when I import in Sketchup the geometries are not instances anymore.

Is there a way to improve the export between the two softwares?

Thank you.

Hi, according with this [page ](https://asmaloney.com/2011/11/code/collada-files-and-sketchup-component-hierarchies/) Sketchup needs <instance_node> and <library_nodes> section for instancing geometries. Blender Collada Exporter does different and when I import in Sketchup the geometries are not instances anymore. Is there a way to improve the export between the two softwares? Thank you.

Luca Saiani commented

2017-05-23 11:06:03 +02:00

Changed status to: 'Open'

Luca Saiani commented

2017-05-23 11:06:03 +02:00

Added subscriber: @Luca-Saiani

Gaia Clary commented

2017-05-25 10:25:19 +02:00

Added subscriber: @GaiaClary

Gaia Clary self-assigned this 2017-05-25 10:25:19 +02:00

Gaia Clary commented

2017-05-25 10:25:19 +02:00

This sounds like a reasonable request.

I know it is easy to setup, but still it would help me a lot if you can add a simple model (blend file) so i have something to look at and be sure we talk about the same thing.
Also can you indicate in detail what you expect to see in the dae file and how it differs from what Blender does at the moment?

This would let me get started a lot faster :)

thanks

This sounds like a reasonable request. I know it is easy to setup, but still it would help me a lot if you can add a simple model (blend file) so i have something to look at and be sure we talk about the same thing. Also can you indicate in detail what you expect to see in the dae file and how it differs from what Blender does at the moment? This would let me get started a lot faster :) thanks

Luca Saiani commented

2017-05-30 10:37:58 +02:00

Hi Gaia,

Please find attached the blend file, the collada file exported from Blender (cube.dae) and the file modified by me (cube_mod.dae) which works as I expect. In the modified file I added few comments to show what I changed.

Thank you so much,

Luca

cube.blend

cube.dae

cube_mod.dae

Hi Gaia, Please find attached the blend file, the collada file exported from Blender (cube.dae) and the file modified by me (cube_mod.dae) which works as I expect. In the modified file I added few comments to show what I changed. Thank you so much, Luca [cube.blend](https://archive.blender.org/developer/F612753/cube.blend) [cube.dae](https://archive.blender.org/developer/F612752/cube.dae) [cube_mod.dae](https://archive.blender.org/developer/F612751/cube_mod.dae)

Gaia Clary commented

2018-01-31 18:55:54 +01:00

According to Collada the Node library is used for organizing scenes with many objects into manageable subgroups (see citations at bottom of page). If i understand correct, then your request introduces one library Node per instance_geometry. This adds one level of hierarchy to the exported data:

  visual_scene:node -> instance_node -> library:node -> instance_geometry

compared to what we have today:

  visual_scene:node -> instance_geometry

The only solution i can see here is to add an export option for switching between "Export with instance_geometry" and "Export with instance_node". BTW the collada importer can handle both variants.

I have marked this report as "Design" and put it into my "feature request basket". Please let me know if you agree.

cheers,
Gaia

from the collada specification 1.4 (library_nodes):
As data sets become larger and more complex, they become harder to manipulate within a single
container. One approach to manage this complexity is to divide the data into smaller pieces organized by
some criteria. These modular pieces can then be stored in separate resources as libraries.

from the collada specification 1.4 (instance_node):
An <instance_node> creates an instance of an object described by a element. Each instance
of a element refers to an element in the hierarchy that has its own local coordinate
system defined for placing objects in the scene.

from the collada specification 1.4 (instance_geometry):
The <instance_geometry> element instantiates an object described by a element. A
geometry object is instantiated within the local coordinate system of its parent or and
that determines its position, orientation, and scale.

According to Collada the Node library is used for organizing scenes with many objects into manageable subgroups (see citations at bottom of page). If i understand correct, then your request introduces one library Node per instance_geometry. This adds one level of hierarchy to the exported data: ``` visual_scene:node -> instance_node -> library:node -> instance_geometry ``` compared to what we have today: ``` visual_scene:node -> instance_geometry ``` The only solution i can see here is to add an export option for switching between "Export with instance_geometry" and "Export with instance_node". BTW the collada importer can handle both variants. I have marked this report as "Design" and put it into my "feature request basket". Please let me know if you agree. cheers, Gaia > from the collada specification 1.4 (library_nodes): >As data sets become larger and more complex, they become harder to manipulate within a single >container. One approach to manage this complexity is to divide the data into smaller pieces organized by >some criteria. These modular pieces can then be stored in separate resources as libraries. >from the collada specification 1.4 (instance_node): >An <instance_node> creates an instance of an object described by a <node> element. Each instance >of a <node> element refers to an element in the <node> hierarchy that has its own local coordinate >system defined for placing objects in the scene. >from the collada specification 1.4 (instance_geometry): >The <instance_geometry> element instantiates an object described by a <geometry> element. A >geometry object is instantiated within the local coordinate system of its parent <node> or <shape> and >that determines its position, orientation, and scale.

Luca Saiani commented

2018-02-02 23:02:59 +01:00

Hi Gaia,

Nice to hear from you.

You are correct: the node library is useful when there are repeated subgrups of objects: for example a repeated window on a facade.
I suppose that the solution you proposed can solve the problem.

Cheers,

Luca

Hi Gaia, Nice to hear from you. You are correct: the node library is useful when there are repeated subgrups of objects: for example a repeated window on a facade. I suppose that the solution you proposed can solve the problem. Cheers, Luca

Igino commented

2021-09-07 09:44:46 +02:00

Added subscriber: @igiornotigi

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Export instance geometries to Sketchup #51593