dyn. blocks with vis states revert to default vis state after ATTSYNC??

dyn. blocks with vis states revert to default vis state after ATTSYNC??

matthew_neesley
Collaborator Collaborator
692 Views
5 Replies
Message 1 of 6

dyn. blocks with vis states revert to default vis state after ATTSYNC??

matthew_neesley
Collaborator
Collaborator

I'm having a REAL sudden problem here.  I've developed an extensive library of dynamic blocks for my employer.  Each block is made up of sub-blocks, and they're all controlled by visibility states.  

 

I've tried updating all the master block definitions...but when I go through the update process with an existing layout and do an ATTSYNC, ACAD changes ALL the existing blocks back to their default-insertion state!!  AWFUL!!  How can I stop this from happening?

 

I've attached a sample conveyor bed layout.  You'll see how the attribute tags are clearly NOT where they're supposed to be.  Run ATTSYNC and watch how some of the shorter straight beds REVERT to the default-inserted length of 144"!

0 Likes
Accepted solutions (1)
693 Views
5 Replies
Replies (5)
Message 2 of 6

Libbya
Mentor
Mentor

Have you selected one of the block insertions prior to the attsync and looked at properties palette?  It appears to me that they are already set to the 144 length but the shorter ones are displaying a different state prior to the ATTSYNC.  You would need to address whatever changed their vis state to 144.  That change occurred before you posted the file.  

0 Likes
Message 3 of 6

Libbya
Mentor
Mentor

You also might want to revisit your prior thread on this block.  You have a large number of unnecessary extra objects, parameters, and actions and I recorded a prior screencast in your prior thread showing step-by-step how to eliminate the unnecessary extra items.   

0 Likes
Message 4 of 6

matthew_neesley
Collaborator
Collaborator

I followed this procedure here:

 

https://www.youtube.com/watch?v=z1uUZOFPYzs

0 Likes
Message 5 of 6

matthew_neesley
Collaborator
Collaborator

....although I think I see the problem here.  I've changed the names of ALL the visibility states in this latest update, so I think I just royally SCREWED myself 😞

0 Likes
Message 6 of 6

Libbya
Mentor
Mentor
Accepted solution

Yeah, if you renamed the visibility states and then redefined the block, that would account for the issue.  The only solutions are the reset the individual visibility states or revert to a saved version of the file prior to the redefine. 

0 Likes