Solids and Blocks

OK, have I just gone crazy or does someone know of a problem with the number/ complexity of Solids within a Block before AutoCAD won't play ball and hide the Objects? Let me explain - I develop up a 3D 'Complex Object' using just about all the 3D Solids Tools (Extrude, Union, Subtract and so on) check it out and it all hides to perfection. Great, now I need to put it away as a Block, add some attributes and Dynamics to control the Attributes and suddenly I can't hide it any more.

Now, that's fine - is the culprit the Nested Blocks, the Attributes, the Dynamics or something else that's causing the issue? Well, it appears to be none of these because lesser blocks (constructed exactly the same way with the same 'accessories') are working fine in the same drawing. I even Insert the ones that aren't working into a brand spanking new drawing and still these troublesome ones won't hide!!!

I can get it to hide by exploding it, but as we all know, that really isn't an option if I want to keep using the Attributes. Besides, because other less knowledgeable characters are going to use these Blocks, I don't want them to even have the option to explode them (thankyou Autodesk for at least making that a reality).

Now, my query is basically is there a limitation - if so what is it and naturally, is there some form of workaround without exploding it??? To help you understand why I want this is basically I generate Automated Elevations from the 3D Model. There are 2 ways to achieve this -

1. Using the FLATTEN command from the Express tools, but this needs the HIDE to work on the Blocks (which it currently doesn't)

2. Use the FLATSHOT command. FLATSHOT works on 3D Solids only and not Surface modelling and some of my Equipment has to be 3DFACEs or Lines with Thickness, etc because I need to use Dynamics to change the length... I can't use Solids because the Stretch Action Dynamics won't work in this case...

I've attached a sample with 2 Blocks (one that does and one that doesn't hide) - test it and then tell me I've missed something... This is in 2007 format, but I've tried it in both 2010 and 2009 with the same results.

Thanking whichever genius solves this one in advance:cry:

3D Won't Hide.zip

It appears to be some bug with creating Attributes as a Field linked to the value of another Attribute.

What is the workflow with regard to the ITEMNO attribute? As it stands, the value is preset: Is there some automated process to modify the value post block insertion? Perhaps the same automation could also modify the EL-INUM attribute, thus avoiding the need for the linked field.

It appears to be some bug with creating Attributes as a Field linked to the value of another Attribute.

Touche SEANT... That's the one aspect I didn't consider (besides, who'd ever expect a field in an attribute to stuff up the viewing of a Block). I guess that's what you get for trying to use those advanced features to automate what you do... Maybe I was expecting just a little too much - now that stuffs up my idiot proofing:x.

Autodesk, here I come... Bug fix required urgently!!!

Hey, guess what... I'm not holding my breath, but I sent off a support request to Autodesk to receive the usual pleasant automated response. But then, Shock - Horror, a couple of hours later I got another response from a human being at Autodesk saying it had been escalated to a Technical Specialist. Nah, not possible...

I'll keep you posted as to the end result - cross your fingers for me/ us

Is it possible that we are seeing a kinder, more considerate Autodesk?

More joy - I've now had an email from the Technical specialist asking for the LISP routine, the XREFs that are missing, etc. WHAT THE - which drawing is he looking at? Anyway, just gone back to him with the simplest example - build a 3D Solid, an Attribute and another Attribute that references that one and he can replicate the problem for himself in under 5 minutes.

Told him to go away and do it for himself and watch it fall in a hole (I did it pleasantly though). Sometimes I think there's more brain power on the CADTutor site than at Autodesk...

Anyway, he'll check it out and escalate it too if neccessary... How far can things go before it gets some action in there??? I must say that 2010 is very stable - the best I've worked with for many a year. They're probably all sitting there twiddling their thumbs waiting for a problem to crop up (nice thought, huh)

Hey guys - long time between drinks (That's Aussie for: Geez, they took forever to get back to me), but Autodesk have finally realized that there is a problem here... But (and there is always the disclaimer), they may not do anything about it because there aren't enough clever Users that will find this one...

Here's their reply:

"Thank you for providing me a step by step procedure to reproduce the issue. I have tested and could reproduce the issue at my end. As of now I do not have nay suggestions. Therefore, without any delay your Support Request has been documented and sent to our development team for investigation. The development team will try to reproduce your Support Request and make an initial assessment. We will notify you immediately by email whenever your Support Request is updated. We appreciate your patience as we work to resolve your inquiry. Please note: Not all issues identified in Support Requests are considered significant enough to address in their entirety; a proposed correction may create significant stability risks; some issues may be impossible to fix due to product architectural restraints. Whenever possible, we will work with you to establish an acceptable workaround."

Fingers crossed