Hiddenparts = {root.subassembly.part} --> Crash

[Anonymous]

Hello ,

I am trying to exclude a subassembly from the drawing but if chrashes all the time.

Following code is working :

As soon as I add the assembly in the list it crashes.

The structrue looks simply like this:

Root:

I try to add only one part, both or the assembly name.

But eventually it always crashed during renderprocess

of the drawing.

Thank you / Regards

Timo

[wayne.brill · Accepted solution]

Hi Timo,

There is one old ticket that seems similar: The title is:

“Hide a sub-assembly in cross section view crashes Inventor”

This was logged for an older release and now has a status of fixed. Can you try this in ETO 2014 and let me know if you can still recreate the behavior?

I do not see anything wrong in your rule. I could test this in ETO (2014 or 2013). If you want me to test it please provide a small but complete dataset.

Thanks,

Wayne

[Anonymous]

No Error with ETO 2013R2

Thank you

[JackGregory]

Your "crash" code has obvious syntax errors.  One line ends with ,v

Probably just a posting error, but could you post the failing code again?

And tell what changed from the working code.

[Anonymous]

Jack ,

This is just the picture end. The list was OK and ending with a existing part. The

code which was not working is shown. The change from the working code was that I added

the two parts from the assembly shown above in the small picture. Somehow this subassembly

parts did cause the crash.

Thank you / Regards

Timo

[JackGregory]

I am sorry, but we can't really help with the information given.

[Anonymous]

Hi Jack,

There is a solution posted by Wayne Brill . What else can we do . If there is a chance to solve this for ETO 2012 then

I thought all the information is available. According to Wayne Brill the coding is OK. Its just the list of hiding parts

 wich is either including the subassembly parts and then chrashes or it does not include the subassembly parts and

then works. From my point of view the answer and help is already given. If there is a bug fix for 2012 it would surly help

us as we can only update in half a year and need to go on with the development .

Thank you / Regards

Timo

[JackGregory · Accepted solution]

Sorry, I missed that you had reported it fixed in 2013 R2.  I should read more and type less. 

While I am not permitted to discuss what we "will" do, I would not hold out hope for any kind of fix back to 2012.