Wipeouts go to front of blocks when drawing is opened.

[jacob.dwyer]

Hi all,

Been searching these forums and others for awhile now and I've found no answer to why this is happening. I have a drawing which holds all the blocks I use, and i insert them from there into new drawings when i need them. The problem is any blocks containing wipeouts have a draw order issue where the wipeout comes to the front. I have tried every technique i can find to correct draw order, including recreating the blocks so the wipeout is created first. None of them seem to have any effect. Even more perplexing, after i fix a block and save the drawing, when i close and re-open, the wipeout goes to the front again. I have to fix the blocks every time i open the drawing. 

I'm at a loss. If i have to fix the blocks every time i open the drawing, it becomes a huge waste of time, but i have found no solutions. Any help would be appreciated.

[msupron]

I take there is no real solution to this problem yet?  We are working with very complex blocks which are heavily reliant on wipeout order, which tends to jump to the front in some dwg instances. Redoing the blocks with the wipe-out being the first created item would be way too time-consuming so hoping for another solution.

[lanceX2G2C]

I haven't seen a fix yet. I'm using 2023 and it hasn't gotten better. Not much hope for 2024 but we'll see I guess.

My advice for now with your compex blocks is to change the wipeout to be a solid hatch on a layer that prints with the lightest grey color. I made my "noplotscreen" layer print like that but I gave the layer a very dark purple color so it doesn't get in my way visually. It will show as a light shading on PDFs but it has worked out pretty well for us.

[jeguizaASRZM]

Hello Lance,

By any chance can you share the lisp file? I tried to add "(defun c:josh (" but it didn't work. No idea on how to code but interested to see what I was missing to making this into a lisp.

I was hoping this code did all the blocks in the drawing as some codes only do by selecting a specific block(by selection).

Thank you so much to you and @jtoverka 

[lanceX2G2C]

Here's the LISP that I added a name to. I have it load when I start AutoCAD and have it assigned to a button. I won't go into how all that happens since there are plenty of forum threads and video tutorials on that sort of thing.

[jeguizaASRZM]

Awesome, Thank you!

Looks like I was missing a lot more parenthesis haha. Works great btw!

hope many more people find this awesome creation.

Thank you!

[Ultimately]

I have had the same issues with Wipeout in Civil 3d 2024. I have since discovered that if you Copy and Paste (Ctrl-Shift-C) and select everything in your block but the Wipeout, I use 0,0 as my copy point. You then Paste (Ctrl-V) to the center point and if you want, delete the items below the pasted (lines, text, whatever). Voila, Blocks are fixed. 

I am not 100% certain, but it seems that something with copy/paste forces the Above Below to actually work. 

I hope it works for you. 

[msupron]

The problem with re-pasting solution is that if you have a complex dynamic block you will loose all of your assigned function and will have to re-link everything/build up new visibility states etc. If your blocks are simple doing that should work, as apparently (from reading up on the issue, please correct me if I am wrong) arises from the fact AutoCAD remembers that lines that end up hiding behind the Wipeout have been created prior to its creation and this "Chronological" drawing order somehow overrides the order set by the user.

[Ultimately]

Thank you for that information, I'll test that! I'll set up a brand new block, in Chronological order when I craft it. I'll report back with my findings.

I personally do not mind relinking the functions, provided that the block actually works as intended. 

[tcarrBDA]

Oh Yeah! That's what I'm talking about !  Quick, easy, done.