AutoCAD dynamic blocks

[Anonymous]

Hi all,

I have been trying to figure out a form of a dynamic block which has been done by other users a lot of times before.

So basically i have a weld symbol with desired weld and all the visibility states have been set up. 

Mistake no.1 was that instead of choosing a parameter set, i chose single parameters and assigned a lookup action to the parameter. i've added a visibility parameter property, and then populated the input property list with all the predefined visibility states. After that, i populated the lookup properties, and by the time i realized what i did, i have already shot my self in the foot.

So, me being me, i chose to redo all of that but this time, i was smarter, so i chose the lookup parameter set (dual lookup tables, bactionbarmode set to 0), populated input properties & lookup properties.

After that part was done, i decided to set the point parameters for the second lookup table assigned to the same lookup parameter. Did that. 

Upon completing that, i decided it was time to set all the input properties and lookup properties, and then this time, AutoCAD decided to shoot me in the other foot by just randomly stopping to work. 

At this point, i was already on the edge... So, knowing i've setup my autosave to every 3min, i expected it will be saved. I got a slap from AutoCAD. No temp file, no nothing. 3hrs of work wasted. Now i am fed up with redoing all of that again. 

So my question is, is there a way i could autopopulate the input properties by selecting the visibility parameter property? 

In case i cant do it, can one tell me if i could assign a new lookup action to an already existing lookup parameter and action? (so that i can use the one i have already created? and just assign another lookup action to it?

Thanks in advance

[pendean]

FWIW Relying on AutoSAVE is probably the biggest mistake users of AutoCAD without the experience of a major loss ever do: teach yourself to manually save often, there are many quick-easy ways to do it. Own your actions, don't just assume "it's taken care of" because you checked a box somewhere.

Dynblocks have a dedicated forum right here https://forums.autodesk.com/t5/dynamic-blocks/bd-p/154
Post your problem blocks in a container file in case they need them.

[Anonymous]

Hi Pendean,

thanks for the tip 🙂

Trust me, i have been using AutoCAD for the past 13years and have had a fair bit of experience with quick saves, major mhrs loss and all. This is just something i have not anticipated happening during saving, as this did happen while i wanted to save the dwg, and since the software crashed, i had nothing else to rely on but the potential bak file or the temporary save file. Which are missing for some weird reason. 

[pendean]

Sounds like you system or AutoCAD session (or file state) had issues. That sadly happens sometimes.

As an old timer user of AutoCAD myself (27+years), I ALWAYS assume AutoCAD is going to crash or freeze at any moment and have dedicated many commands, shortcuts, and buttons to perform a variety of QSAVE and AUDIT combos as well as alt-saves to secure no-delete folders "just in case".
To this day I've not lost anything more than 3-5minutes work, and I always have a file to recover from somewhere on my PC or network.

AutoCAD crashes and/or freezes occasionally: anyone that tells you otherwise is not an 8+hour a day user of the program. Never forget it, always assume the worse is going to happen at any moment.

[Libbya]

There is not any way to auto-populate a lookup table.  

The double-lookup must have both tables assigned in the TOOL.  You cannot assign a second lookup table to an existing lookup parameter in order to create a double-lookup.

Always remember that AutoCAD is inanimate and cannot DO anything to you.  You do things to AutoCAD, not the other way around.  Consider the lost time good practice.  It will go a lot faster the next time.  Post the block if you want specific assistance in setting it up.   

[Anonymous]

Hey,

thanks for the replies and advices.

This is currently what I am trying to remake. Basically, I have found one welding symbol which was created by some user in this community.

The one that I am trying to remake is the one that is called weld remake. The one that im trying to replicate from is called Weld symbol.

Now, I am doing something wrong and I don't know what and I was hoping that this is were You guys with more knowledge and expertise kick in.

I have setup the visibility states, flip parameter.. I have also setup the double lookup tables, but im having trouble giving the lookup action an idea of what I want to do with it.

Can someone explain what I am doing wrong in this block and how to solve it please.

The issue I think I have has to do something with the point parameters which have their input properties and lookup properties messed up. TBH, im not sure even how this should all be setup 😕

Thanks in advance for all help

[Anonymous]

I was fiddling around with the block, and really haven't done anything to it. I've reset the block, and it's partly working so im currently puzzled.. its still not working the way it should though..

[h_s_walker · Accepted solution]

The Y position of Points 1, 2 and 3 are wrong. They need to be moved to 1, so that when you insert the block it defaults to the first items in each lookup

[Libbya · Accepted solution]

The three Y positions should be pos1Y=1, pos2Y=2, and pos3Y=1.  In order for the double lookup to start working, the as-drawn state (parameter positions) must match a row on the double lookup table AND that row must match the topmost visibility state in the visibility state dialog.  In this case, the topmost visibility state is Fillet-Top which corresponds to the 1-2-1 row on the double lookup.  The input values for the 1-2-1 row are 1,2,1.  Once that is set correctly, there might still be some issues.  If there are, then you need to do a bit of diagnosis.  It could be incorrect input on the lookup table either with the table values or non-matching lookup property names for the two tables.  It could also be an issue with the individual visibility state displaying the incorrect items.  See screencast to get started.  Report back if there are further issues.  

[Anonymous]

@h_s_walker

@Libbya

Hey guys, thanks a lot for the time You have invested in this matter. Both solutions do work, meaning, when I set the Y value of all three position parameters to 1, or if I do pos1,pos3 Y=1 and pos2 Y=2, it all seems to work. I really haven't seen any difference in the performance of any of these blocks.

Do You maybe know why it works in both cases? I'm trying to figure it out so that I can learn to properly develop a double lookup dynamic block in case I need to do it again.

[h_s_walker · Accepted solution]

Look at the following two images.

The first one has all visibility states of the block (there are 72 in total) and a unique reference for each.

The second image references the x and y of a point and whatever the result is, chooses a reference to send to the other table.

[Anonymous]

I understand now.

Thank You very much for all the help and time 🙂

Regards,

Raf

[Anonymous]

Got one more thing to do with this block and really cant figure it out (maybe cause i have been looking at it for the past two weeks).

So, i would have to add another look up table which has a visibility parameter property, which would in turn be defined so that the end user could turn off/on the weld tail, but independently of the arrow side weld/other side weld, meaning, no matter what i choose for my top or bottom symbol, i can have the tail turned on or off. 

any advice's?

[h_s_walker]

Here you go.

I just added a linear parameter to the tail and a scale action to that which scales the tail.

The lookup table uses the linear parameter to scale the tail so you can see at / so it's so small it won't be seen on a plot

[Anonymous]

@h_s_walker- thank You very much. Sorry for the late reply, I had no access over the weekend.

Anyway, this seems to be a very good solution. However, I would still like to know how could I make the the tail visibility toggle on/off regardless of what my top or bottom welds are? do I have to recreate a new visibility state for that as well? ie. fillet top - Ref. ON, Fillet top - Ref. Off and so on for each type of the visibility states? Or is there a simpler solution without scaling the tail?

Thanks so much

[h_s_walker]

Unfortunately I don't think there is a simpler solution than scaling the tail.

Putting in more visibility states would be a massive pita (no not the bread)

[Anonymous]

Do You think maybe that this could solve my problem? I have added point 4, and an additional double lookup table. One lookup table refers to a visibility state, and the other to the Y value of point 4. And the newest of all lookup tables, refers to the point 4 Y value where the appropriate ON/OFF have been assigned. However, I cant get it to work XD

[Anonymous]

Hey guys,

so I kind of made it work. I still don't get it where or what im doing wrong here. I am not able to change the tail toggle on/off, without turning off all of the other thing on the weld.

file is attached, and if someone could assist me in figuring this out, I would be very thankful.

Thanks in advance

[Libbya]

In stock autocad there can be only one visibility parameter and you have that visibility parameter controlled by two double lookups.  When you switch one of them, it switches the visibility to ref.on or ref.off.  When you switch the other, it switches between all of the other visibility states.  When you switch to ref.on it resets ALL objects to those that are set as visible for the ref.on state, etc... 

In order to turn the tail on/off independently of all the other states, then you would need to double the number of current visibility states.  You would need each current visibility state with the ref ON and each state with the ref OFF.  You would then delete that second double lookup, add position4 to the prior lookup table, and double all the rows with the appropriate values for ref ON and ref OFF.

Like hwalker said, it's a PITA.  If scaling works for you, then do it that way.  If not then duplicate all the visibility states and the rows on the table.    

[Anonymous]

@h_s_walker

@Libbya

alright. thank You very very much for clearing this for me! I suppose that the moderator can now lock this thread!

Once again thank You very much.