Hatch visibility messed up after re-opening files

[Anonymous]

Hello CAD experts, I have been trying to figure out what is messing up all my dynamic blocks that use visibility states to show/hide hatches. Essentially, hatches would appear in visibility states that they're not supposed to. I'd fix the block, it'll work fine, then I'd save the file, close it, and if I reopen it, the problem comes back.

When the file opens, the blocks look fine. If I switch it to another visibility state and then back to the original, it'll get messed up.

This happens in multiple blocks that were made independently from each other.

I'm currently using CAD 2014 and have been able to replicate this problem in another computer with CAD 2016

File is attached. Does anyone have an idea why this is happening?

[Libbya]

You are using a single associative hatch object in all states and yet the associative boundary is different in each state.  Use a different hatch object for each state that has a different hatch boundary and your problem will be solved.  

[Anonymous]

Thanks for the reply Libbya. Unless I'm missing something, there are already separate hatch entities within the blocks related to each visibility state. You may be seeing only one across all states because the file messed up again and is showing you the same hatch entity. If I toggle the visibility mode in block editor, I can see the ghosted lines of the hatch that's being hidden. Please see if you can set the proper hatch to be visible across the different states (according to the outlines shown in the states) and seeing if that is retained after you save, reopen, and toggle the visibility states. I guess the file messes up when I save, so I can't provide you the blocks as they're supposed to be.

I'm also linking to a screencast to give a better idea of what my problem is.

[Libbya]

I fully understand your problem and what is causing it.  I see now that you do have different hatches within the blocks, but you have the incorrect hatches showing in the given visibility states.  This is causing the hatches to switch associativity when the boundary is made smaller and lose associativity when it is made larger.  The attached screencast makes the issue quite obvious.  This issue is the same in the other blocks.  As a visual aid you can see how I set the individual hatches to individual colors.  That would be a good way to repair your blocks.  The solution is as I stated before.  Use a hatch that matches a given hatch boundary.  

[Anonymous]

Thank you for your detailed response and for being patient with me. I've followed your suggestion and recolored the objects per visibility so that the problem is more visible. The problem I'm having however is that whenever I close and reopen the file (after fixing the block), the block gets broken again. I made another screen cast demonstrating this. Skip to 2:00 and 4:35 to skip the block editing part, I fixed the block twice. If you re-open the file you fixed for me, does everything still work the same way as it did before you closed it? Up until now I've had to fix the block every time I open the file. Sorry if I wasn't clear.

[Libbya]

After fixing your block I cannot replicate the issue.  Notice in this screencast I save, close, and reopen and it all works fine. 

Please post your updated block so I can try to see what the issue is with it.

[Anonymous]

I've attached the file that I created in the previous screencast. Could you also upload the file you fixed? I wonder if it would open up differently in mine.

[Libbya · Accepted solution]

Here's the block you just posted with each of the hatch visibilities set correctly in all three blocks. It closes and reopens for me without issue.

[Anonymous]

Okay so when I opened up your file, it works just like it should. But when I saved the file (without making any block changes), and re-opened the file, the problem is back. I hope it's not just a problem because my CAD version 2014 is old, because that means these blocks can never be used reliably by people without the latest CAD version.

[Libbya]

I do not think it is a problem with 2014 (unless you don't have the service packs installed).  I have had similar blocks going back to 2007.  It might be an issue with the installation on your local machine, though. I would try a repair and a reinstall.

[Emmsleys]

There were some great post's in this thread. Following up, were you able to find a solution or a workaround?

Did any of the posts in the thread help with the issue?

Please use the Accept as Solution for those post’s that helped. It may benefit other users who might have a similar question or issue.

Thanks for your time.

[Anonymous · Accepted solution]

I know it's been a while but I've found the solution and want to share it in case anyone else is having the same issue. After upgrading to AutoCAD 2018 and getting the same problem, I figured it wasn't a problem with my installation. Then it hit me - we've set our CAD to save to 2004 for compatibility reasons. Sure enough, after saving Libbya's good file onto all the different versions available, the blocks started working correctly at version 2010 and newer.

I'm making a case for our office to set AutoCAD 2013 as the standard instead of 2004. Thanks to all who helped!