i-part and skeleton model

[Anonymous]

Hi, we are trying to import an i-part into assembly but the skeleton model shows through, is there a way to turn the skeleton model off? same part prior being made to i-part worked fine. See video below

Thanks,

[Anonymous]

Hi, we are trying to import an i-part into assembly but the skeleton model shows through, is there a way to turn the skeleton model off? same part prior being made to i-part worked fine. See video below

Thanks,

[CGBenner]

@Anonymous 

Can you attach the ipart file here, maybe someone can take a look and figure it out?

[CGBenner]

@Anonymous 

Can you attach the ipart file here, maybe someone can take a look and figure it out?

[Anonymous]

Hi, see part attached opens fine on its own but not when imported into an assembly.

Thanks

[Anonymous]

Hi, see part attached opens fine on its own but not when imported into an assembly.

Thanks

[CGBenner]

@Anonymous 

The skelton model itself was not attached and is openineg unresolved.  But it raises a question... do you need the skeleton part in this ipart?  It was there, I assume to layout the part... but is it in some way controlling the dimensions of the instances?

[CGBenner]

@Anonymous 

The skelton model itself was not attached and is openineg unresolved.  But it raises a question... do you need the skeleton part in this ipart?  It was there, I assume to layout the part... but is it in some way controlling the dimensions of the instances?

[johnsonshiue]

Hi! I don't believe this is a reliable workflow. iPart was designed to create standalone library components, totally driven by a table. It is not meant to be a base to create other geometry.  There are technical issues preventing it from working correctly.

I think you need to use multiple skeletal parts. Or, you can use iLogic to drive parameters across multiple parts. Then use iLogic Design Copy to spawn the variation and then work on next variation.

Many thanks!

[johnsonshiue]

Hi! I don't believe this is a reliable workflow. iPart was designed to create standalone library components, totally driven by a table. It is not meant to be a base to create other geometry.  There are technical issues preventing it from working correctly.

I think you need to use multiple skeletal parts. Or, you can use iLogic to drive parameters across multiple parts. Then use iLogic Design Copy to spawn the variation and then work on next variation.

Many thanks!