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]

I read a lonnnnng time ago when I was researching Tool Palettes (an Autodesk University or AUGI course???), that it was good practice to keep Tool Palettes in a separate folder structure for each release.

Every time a new Autocad release comes along, I copy the existing folder structure [i.e. Acad2016], to a new folder structure [i.e. Acad2017].  LISP setup routines are updated to reflect the new paths and I do all my pre-distribution testing there without affecting the users on previous versions.  I delete the folders for "obsolete" Acad versions at the same time.

Caveat:  We're not a large company, so it's relatively easy to make changes and restructure CAD/BIM procedures as needed.

[Tekcon13]

So...

Installed the Autocad 2017.1 Update today.

Did some Autocad work, plotted the drawings... where did my symbols go???  Oh yeah, I installed the update this morning.  Sigh.

So the original issue has been fixed.  I can now import 2016 palettes and the yes/no plot variable is working correctly!  Yay!  Thank you!

Now I have to decide between re-importing 2016 palettes, reversing the original find/replace solution or a combination of both... AAARRRGH

[Sofia.Xanthopoulou]

Attention!

Please do not install the update yet! Just had a customer who has installed this update and now facing other issues! Please let me check if it is related to this update.

One thing what happens for sure is, that the TRUE/FALSE value has been reverted, so you either have to find/replace those values again, or use the original atc files, if they still exist. 

For those who already installed, please report if you notice any other changes or issues. 

My God... this is a never ending story.... so sorry....

Please bear with me, I will update this post, as soon as I find out what is going on.

Thanks

[gros33]

Thanks Sofia

One thing I've noticed is all my custom button shortcuts / temporary overwrites have elapsed.

Thank goodness I keep a backup file...

[Sofia.Xanthopoulou]

What do you mean with elapsed? 

[gros33]

I mean all mouse button combinations and temporary overwrites erased
I don't even think I got 'out of the box' settings. They were just erased.

[Tekcon13]

Thankfully I backed up my palettes before reversing the original find/replace. I've been working with the updated Acad for three days now and no issues yet.

[Tekcon13]

Sofia - since you asked...

Issue #1:

• Created a new dynamic block (using Block Editor, SaveAs)
• Saved the host drawing, closed the drawing, re-opened the drawing
• Dragged the new block to the tool palette
• Result:  Blank tool icon and error message "Block definition "test2" is not found in the source drawing "F:\0Cad\blahblahblah\SymbolLibrary.dwg"
• Same error message when new blank icon is selected

Issue #2

 Added a new visibility to an existing dynamic block

• Dragged New visibility of existing block onto palette
• Saved the host drawing, closed, reopened said drawing
• The new visibility is not available for selection in the properties of the existing block on the palette

Issue #3

 Not sure exactly what I did, as I can't reproduce it, but following Issue #2...

• Selected the new, uncooperative block with the new visibilty
• Right-clicked ->"Redefine"
• My existing dynamic block with the newly added visibility lost all its dynamic properties and Undo doesn't bring them back- but I think that's another topic!

[Anonymous]

@Tekcon13 did you install Service Pack 1? Is this the update you are referring to?

From your description, it sounds like you have a host dwg file containing the dynamic block inside of it. If this is true, I suggest WBlock out the dy block into a library folder. When you open the dwg, it should prompt you to enter Block Editor immediately. Then drag and drop the block from Design Center to the Tool Palette. I updated a block with a new visibility, saved the block file to the library folder, and the new vis states were available in the properties right away. In short, save the blocks to a common server folder and import from here, not from a host dwg

[Anonymous]

@Tekcon13 also, the find/replace isn't that hard or time consuming. We have an extensive Tool Palette with 10 tabs, and it only took 10-15 minutes to run find/replace for the entire palette.

[Anonymous]

My issue after installing is that text has a left justification when I create a fit text attribute and INSERT from a dialog box or drag and drop from windows explorer. Not sure if this is related or not, but has been a huge headache.

[Anonymous]

You can change the justification of the text in the attribute definition menu when you create the attribute

see attached pic, don't think it's related

[Anonymous]

Make the block over and over to make sure I was doing that originally and still no luck. I think this might be a separate bug as I see help topics on similar issues for earlier versions

[Anonymous]

Post your block. I'll try to help even tho it's off topic

[Sofia.Xanthopoulou]

Hi @Tekcon13,

are you sure those issues didn't exist prior to the update? When you uninstall it, is everything fine?

A quick summary from my end: 

True/False value has to be changed back to False.

Due to changes for 4K displays some dialogboxes (especially self-made dialogs) may appear smaller. 

I will address @gros33 issue to our experts and report back. 

Regards

[Tekcon13]

Hi @Sofia.Xanthopoulou

I uninstalled the Update this morning and all the glitches have disappeared.

• I can burst a dynamic block, then undo and the block retains its dynamic properties.
• I can add a visibility to a dynamic block, drag it onto a tool palette and the new visibility is respected.

[Sofia.Xanthopoulou]

Hi guys,

as we have faced several incidents ... there will be an update 1.1. You know that I am not entitled to tell when - but it will be soon 

Please hang on. 

I almost forgot to tell you another thing. Please create new posts with your observations after the update. This thread is about the blocks in the Tool Palettes. All other incidents should go public, too, with their own titles - otherwise they are lost in space...

Regards

Sofia

[Anonymous]

This Problem came up on the latest update for autocad 2017 LT for me & I only updated it last week, so im guessing that the problem hasnt been resolved? 

[Anonymous]

TIm,

I've been able to get our template down to 12 layers. We dynamically load them per dwg using lsp routines. we also change layer colors in specific production dwgs depending on what we want to highlight.

Here is the secret: http://www.daniellench.com/2009/02/my-biggest-civil-3d-template-secret/

[Anonymous]

James, I have been using a method I came up in 2008 for to this day for a networked tool palette. http://www.daniellench.com/2008/06/network-deployment-of-a-tool-palette/

That being said, it's still affected by this problem but only after I connected the palettes to my testing install of 2017.

best,

dan