Lumion Support Center

Support for unlicensed users => Post here if you can't find your License Key => Topic started by: 35design on May 01, 2018, 04:17:31 pm

Title: [Answered] Rhino model import - always one object?
Post by: 35design on May 01, 2018, 04:17:31 pm
Hello,

I've been scouring the forums for an answer to this question but have had no luck. When importing a Rhino model, Lumion interprets the model as one object. To clarify, I modeled a simple wall, with door jamb, casing, floor and base molding. The Rhino file was saved as a COLLADA (*.dae) file and once imported into Lumion, it is interpreted as a single object. The floor, casing, molding, etc. is all connected and materials cannot be applied to individual components. Is there a way to import a model from Rhino, that would allow Lumion to detect the separate pieces, floor, wall, trim, etc. to have materials applied to them individually? It would be better to not carpet the floor and walls :)
Certainly this is a process issue error on my end that I just can't figure it out!

Hope all have a good day!
Title: Re: Rhino model import - always one object?
Post by: Morten on May 01, 2018, 05:05:22 pm
Welcome, 35design. :)

Did you already read this post (https://forum.lumion.com/index.php?topic=21901.msg674941#msg674941) on how material assignments are interpreted when importing Rhino models in Lumion?
Title: Re: Rhino model import - always one object?
Post by: 35design on May 01, 2018, 05:28:39 pm
Hello Morten, and thank you for the welcome!

Also, thank you for the great link with a resolution to my question.

Have a good day!
Title: Re: [Answered] Rhino model import - always one object?
Post by: Morten on May 01, 2018, 05:55:38 pm
Thanks, you too! :)

Let us know if you've got any other questions.