New blocks in a drawing have layers set to do not plot... again.

New blocks in a drawing have layers set to do not plot... again.

Anonymous
Not applicable
516 Views
4 Replies
Message 1 of 5

New blocks in a drawing have layers set to do not plot... again.

Anonymous
Not applicable

Hey Folks,

 

This is now my second time posting about this.

 

Whenever we insert a new block that has layers associated with it into a drawing those layers are set to NON-PLOT.  We first encountered this issue in the 2017 release with one of the updates.  The fix provided by the Autodesk folks was to either rebuild tool palettes or roll back to the previous software build.  Both solutions worked.  Thinking forward, we chose to rebuild tool palettes.

 

We have all upgraded to the newest release and are right back in the same situation.  Has anyone else been dealing with this?  Anyone found a fix that doesn't involve rebuilding tool palettes?

0 Likes
517 Views
4 Replies
Replies (4)
Message 2 of 5

Libbya
Mentor
Mentor

I'm using ACA 2017.  ACA uses layer keys.  I had not noticed that behavior, but I can replicate your issue.  If the layer does not exist, then the new layer will be set not to plot despite the layer of the block source file being set to plot AND the layer in the layer key set to plot!  That's fairly obnoxious.  The good news is that if the layer already exists in the host drawing, then the plot status is not changed.  The other good news is that the layer/make layer command does not set the new layer not to plot.  Can you add the necessary layers to your template drawing?  Alternatively you could create a simple lisp routine that would make all of the necessary layers in one swell foop.  Then consequent block insertions would be on layers that were set to plot.       

0 Likes
Message 3 of 5

Anonymous
Not applicable

Thanks for the quick response.


@Libbya wrote:

If the layer does not exist, then the new layer will be set not to plot despite the layer of the block source file being set to plot AND the layer in the layer key set to plot!  That's fairly obnoxious.       


Its more than obnoxious.  Not sure Autodesk had intended it to work this way.  If that is the case whats the benefit this offers?

 

I had thought of adding the layers to our template drawing but decided against it.  There are 5 different departments that manage the master drawing.  Having all the layers in the drawing would cause issues and all it would take is one person to PURGE the drawing and then it would all be for nought.  

 

Some of the blocks that we utilize are tools that we use to detail out jobs.  Some of them have components that are set to do not plot on purpose.  I feel that a simple lisp to turn everything on would be a wild goose chase to track down the layers that are not supposed to plot.

0 Likes
Message 4 of 5

Libbya
Mentor
Mentor

I was unclear.  I was not suggesting for a lisp to turn on all layers.  I was suggesting a lisp that would MAKE the specific necessary layers that need to be on.  If different departments have different layers that needed to be added, then a separate lisp for each department could be made.  

 

The code for a single layer is very simple:

 

(command "-LAYER" "M" "A-Heavy" "C" "250" "" "")

 

That line of code will make a layer called "A-Heavy" with a color of 250.  Whatever other per layer variables are needed can be added as well.  Do a similar line of code for each layer necessary.  Turn all the individual layer lines into a single function definition per department so a drafter can enter the command to add the layers or make it automatically run by having individual department drafters add the lisp to their startup suite so the necessary layers would automatically be made in each drawing they opened.  It would be immune to someone else purging the layers as they would just be added the next time someone opened the file.   

0 Likes
Message 5 of 5

Anonymous
Not applicable

I understand what you were referring to and your work-around makes sense to me.  It is not, however, a viable solution for us.

 

This is an issue that came up when migrating from the 2016 to the 2017 release.  Autodesk supposedly fixed it in a software update after they advised us to either revert back to the previous release or rebuild our tool palettes.  We all chose to rebuild our tool palettes.  Clearly, this issue has come back.

 

Autodesk needs to fix this!

0 Likes