2017 Blocks inserted using Tool Palettes create Noplot layers

[Tekcon13]

New issue with Autocad 2017: 

When inserting a block (electrical symbol) from a Tool Palette, if the block's layer is not already defined in the drawing, the symbol layer is created as a Noplot layer.

Been using Tool Palettes for years and have never seen this particular quirk.

All the electrical symbols are in one master library drawing.  The layers in that drawing are all set as plottable.  I also made sure that the current layer of the drawing into which I was inserting the symbol was not set to Noplot, just in case the new layer was being created based on the current layer settings.  The new layer still got set to Noplot.

If the symbol layers are created before the symbol is inserted, inserting a symbol from the tool palette doesn't affect the preset layer settings.

The trouble is, as we are used to the layer being created properly in previous versions of Autocad, and Noplot layers presenting on screen as if they were plottable (ie. not faded or a different colour to indicate the Noplot status - HINT, HINT Autodesk!), drawings are getting plotted with missing symbols.

Anyone else noticing this behaviour?

[Tekcon13]

New issue with Autocad 2017: 

When inserting a block (electrical symbol) from a Tool Palette, if the block's layer is not already defined in the drawing, the symbol layer is created as a Noplot layer.

Been using Tool Palettes for years and have never seen this particular quirk.

All the electrical symbols are in one master library drawing.  The layers in that drawing are all set as plottable.  I also made sure that the current layer of the drawing into which I was inserting the symbol was not set to Noplot, just in case the new layer was being created based on the current layer settings.  The new layer still got set to Noplot.

If the symbol layers are created before the symbol is inserted, inserting a symbol from the tool palette doesn't affect the preset layer settings.

The trouble is, as we are used to the layer being created properly in previous versions of Autocad, and Noplot layers presenting on screen as if they were plottable (ie. not faded or a different colour to indicate the Noplot status - HINT, HINT Autodesk!), drawings are getting plotted with missing symbols.

Anyone else noticing this behaviour?

[JGAo1]

Dan,

Thanks for the post. We have the same setup, but keep the original ACAD palletes in place. I added a new network folder to the toolpalletes path & make it the first in the queue so AutoCAD adds new palletes in the network location.

I typically just copy & paste palletes from older versions to a new folder for the latest ACAD, but didn't bother this time - & have paid the price!

Forgot to say, nice blog!

[JGAo1]

Dan,

Thanks for the post. We have the same setup, but keep the original ACAD palletes in place. I added a new network folder to the toolpalletes path & make it the first in the queue so AutoCAD adds new palletes in the network location.

I typically just copy & paste palletes from older versions to a new folder for the latest ACAD, but didn't bother this time - & have paid the price!

Forgot to say, nice blog!

[Anonymous]

YEah, it's not happy now.

I've set up multiple palettes also. I expose the advances palettes to users
as they move up in experience. Interns get a standard palette with title
blocks, design blocks, details etc...

Advanced users have sub assemblies and other specifics. They also can have
the out of box ones if they want but mostly the pruned ones I've developed
are good.

Getting the sub assemblies in there was a trick that required using the
eyedropper from a local catalouge if i remember correctly. it's been a
while. Nice thing with them is you can spec city standard slopes and widths
in the properties of the sub assembly in the palette.

Best,
Dan

[Anonymous]

YEah, it's not happy now.

I've set up multiple palettes also. I expose the advances palettes to users
as they move up in experience. Interns get a standard palette with title
blocks, design blocks, details etc...

Advanced users have sub assemblies and other specifics. They also can have
the out of box ones if they want but mostly the pruned ones I've developed
are good.

Getting the sub assemblies in there was a trick that required using the
eyedropper from a local catalouge if i remember correctly. it's been a
while. Nice thing with them is you can spec city standard slopes and widths
in the properties of the sub assembly in the palette.

Best,
Dan

[Anonymous]

This issue is recurring again in 2018.

Autodesk please fix!

[Anonymous]

This issue is recurring again in 2018.

Autodesk please fix!

[Jhallock!]

Are you saying that I should NOT undo my fix for 2017. Before upgrading to 2018.

[Jhallock!]

Are you saying that I should NOT undo my fix for 2017. Before upgrading to 2018.

[Anonymous]

This issue is reoccurring again in the 2018 release.  Is there anything in the works to resolve it?

[Anonymous]

This issue is reoccurring again in the 2018 release.  Is there anything in the works to resolve it?

[Anonymous]

I would set that aside for the moment and let auto desk figure this out before updating.

[Anonymous]

I would set that aside for the moment and let auto desk figure this out before updating.

[Tekcon13]

---

@Anonymous wrote:

This issue is recurring again in 2018.

Autodesk please fix!

---

I learned my lesson last year.  That's a lie!

Thankfully, I've been to busy to install and deploy the latest gem.

[Tekcon13]

---

@Anonymous wrote:

This issue is recurring again in 2018.

Autodesk please fix!

---

I learned my lesson last year.  That's a lie!

Thankfully, I've been to busy to install and deploy the latest gem.

[Anonymous]

This is still an issue. It has had an impact on my professional reputation Autodesk.

This problem has made me look somewhat incompetent to my clients.

What is the point of licensed software if it is not as reliable as the pirated stuff??

Please fix this issue! I shouldn't have to patch anything or change scripts or anything if

I'm paying for robust professional software.... now Should I???

Regards

[Anonymous]

This is still an issue. It has had an impact on my professional reputation Autodesk.

This problem has made me look somewhat incompetent to my clients.

What is the point of licensed software if it is not as reliable as the pirated stuff??

Please fix this issue! I shouldn't have to patch anything or change scripts or anything if

I'm paying for robust professional software.... now Should I???

Regards

[Anonymous]

I am currently experiencing this issue on AutoCAD 2018. How would I fix it? What update do i need?

Thank you,

Garrett

[Anonymous]

I am currently experiencing this issue on AutoCAD 2018. How would I fix it? What update do i need?

Thank you,

Garrett

[Tekcon13]

My palettes are working in 2018.

I looked at the .ATC file for one of my tool palettes and "isNotPlotted" is set to "FALSE", which is correct for 2018 ( and for 2017 AFTER they fixed it).

If the items in your palettes are displaying "TRUE", a Find/Replace will quickly fix the problem. 

You may have done what I did originally and imported the 2017 palettes that had been "corrected" to work with unfixed 2017 into 2018...

J

[Tekcon13]

My palettes are working in 2018.

I looked at the .ATC file for one of my tool palettes and "isNotPlotted" is set to "FALSE", which is correct for 2018 ( and for 2017 AFTER they fixed it).

If the items in your palettes are displaying "TRUE", a Find/Replace will quickly fix the problem. 

You may have done what I did originally and imported the 2017 palettes that had been "corrected" to work with unfixed 2017 into 2018...

J

[msuracer10]

I was having this same issue with 2019 and stumbled onto a simple solution:

Open the drawing/drawings that contain the affected tool palette blocks and right click on the tool in the palette.  Click Redefine, and viola, when inserted in a new drawing, the newly generated layers come in correctly.

Not ideal if you have a ton of blocks to deal with, but it worked for me and I wanted to pass it along. 

[msuracer10]

I was having this same issue with 2019 and stumbled onto a simple solution:

Open the drawing/drawings that contain the affected tool palette blocks and right click on the tool in the palette.  Click Redefine, and viola, when inserted in a new drawing, the newly generated layers come in correctly.

Not ideal if you have a ton of blocks to deal with, but it worked for me and I wanted to pass it along.