Dynamic block (multi vis states) need help with 1 state

Dynamic block (multi vis states) need help with 1 state

Anonymous
Not applicable
956 Views
8 Replies
Message 1 of 9

Dynamic block (multi vis states) need help with 1 state

Anonymous
Not applicable

Hi there,

 

I got a dynamic block for aluminium square tubes (european). The block is working perfectly (many thanks to M_Hensley) as i would like except for 1 part. I would like to add the possibitlity to say if its a section or an elevation view. With adding lookup tables linking to my vis states i thought this would be peace of cake... This even would be a piece of cake when i didnt wanted the attribute that shows the text from the different lookup tables.. But i really really want to keep that attribute in there. 

 

Anyone able to help me solve this small nugget? 

 

Many thanks!

-Patrick

0 Likes
957 Views
8 Replies
Replies (8)
Message 2 of 9

Libbya
Mentor
Mentor

You can do multi-vis using this technique I came up with:

 

http://forums.autodesk.com/t5/dynamic-blocks/ootb-multiple-visibility-states-solution/m-p/4961288#M1...

 

You'll want to read through the whole thread as I have simplified the process.  Once you understand the process, I will be happy to assist with fine-tuning your block.

0 Likes
Message 3 of 9

Anonymous
Not applicable

Hi there Libbya,

 

I have been reading that couple days ago, and been experimenting with that method a bit. So far i think i am slight to inexperienced for it yet. I am trying to figure it out a lot with trial and error thought. But this nugget i can't seem to get figured out :-(. 

 

I could use some directions, i don't need someone to finish the block for me, then i would not learn anything. Got any tips or tricks for me?

 

-Patrick

0 Likes
Message 4 of 9

Anonymous
Not applicable

My tip is to re-read very slowly Libbya's wisdom.  Its dead on for this topic.  Took me some time to realize what I was doing wrong to make it work.

0 Likes
Message 5 of 9

Libbya
Mentor
Mentor

Right now you have two single-lookups (Dikte and DSN/ELE)  that are both able to independantly change visibility states.  As you can see, that does not work properly.  

 

The way that it needs to be set up in order to have independent visibility parameters is that you have a lookup for each desired visibility parameter and instead of having those lookups directly change the visibility state, they change the x or y position of an invisible point parameter.  The x and y positions of that point parameter are then used as the input parameters for a double lookup parameter and the second table changes the actual visibility state.  You need to create a visiblity state for each of the permutations for the two lookup parameters.  Dikte has the choices of 2mm, 3mm and 4mm.  DSN/ELE has the choices of Doorsnede and Aanzicht.  The permutations would then be (2mm, Doorsnede), (2mm, Aanzicht), (3mm, Doorsnede), (3mm, Aanzicht), (4mm, Doorsnede), and (4mm, Aanzicht).   You need to make all six of those visibility states.

 

You then need to add a point parameter.  For ease, name it Input.  For its location, I would recommend placing it at 2,1.  The Dikte and DWN/ELE lookups will NOT change the visibility state directly as you have it set up.  Instead, they will change either the x-position or the y-position of the Input parameter that you just added.  You will need to add remove Visibility1 from both Dikte and DSN/ELE tables.  Then add Input X as the input parameter for Dikte.  Input a value of 2 so it corresponds to 2mm, 3 to 3mm 4 to 4mm.   Next add Input Y as the input parameter for DSN/EXE and add the value 1 to correspond to Aanzicht and the value 2 for Doorsnede.

 

Next you will need to add a double-lookup parameter - if you do not know how, then follow the directions of the thread I linked above.  Name the double-lookup Bridge.  Name one of the two associated lookup tables Input and name the other Vis.  

 

Open the Input lookup table.  For lookup properties on the right, add 2 - 1, 3 - 1, 4 - 1, 2 - 2, 3 - 2 and 4 - 2.  Add Input X and Input Y as input properties to the Input table.  Add the appropriate values for Input X and Input Y so that they correspond to the 6 Lookup Properties you added in the last step.

 

Next open the Vis table.  Add the SAME six lookup properties on the right.  They need to be exactly the same as the lookup properties on the Input table.  Add Visbility1 as an input property to the Vis table.  Choose the correct state for Visibility1 so that it corresponds to the correct lookup property that corresponds to the correct Input X and Input Y values on the Input table.  

 

Crystal clear?

 

In looking at your block I would make a couple other suggestions.  If you have three different size lookups then I would recommend having them reference three different X distance parameters and three different Y distance parameters.  That way you can have the default size of each be on its corresponding lookup table and will avoid the KIES PROFIEL!!! value.

 

You only need one rotate parameter/action and have it visible for all states and rotate all three attributes.  Do the same for the point/move - just have one that is visible for all states and have it move all three attributes.

 

Let me know if you get stuck.  

0 Likes
Message 6 of 9

Anonymous
Not applicable

Hi libbya,

 

I think i know what u mean, i will have to do some trial and error work/runs with it but i think i can manage it. In the next day(s) i'll check into it and will let you know if i got it working. If i can get this one working i can recreate some other blocks as well that will benefit from it!

 

Many thanks for now already!

-Patrick

0 Likes
Message 7 of 9

Libbya
Mentor
Mentor

The attached block may help for reference.  I set up the multi-vis.  I assume Doorsnede is the section view that is shown and Aanzicht is the elevation view which is not yet drawn.  Instead of guessing at how you wanted the elevation view to look, I just placed a big A in the visibility states and made it so the A is stretched/warped with size changes and is displayed as either 2mm, 3mm, or 4mm line width.  I also changed the starting size for the distance parameters to 40 and 40 as 40 x 40 exists on all three size lookup tables and went to a single move and single rotate parameter as I described previously. 

0 Likes
Message 8 of 9

Anonymous
Not applicable

Hi Libbya,

 

Doorsnede is dutch for Section, Aanzicht is dutch for Elevation ;-). In this block i want to use Elevation (aanzicht) for the same look but without the solid hatch. Many times a square tube is drawn in a section drawing when its a bit in the back cause it is needed for mounting sheetwork or some sort. 

 

So i short i want that aanzicht looks exactly like doorsnede but without the solid hatch :-). I will look into your  block this afternoon, currently creating some others that don't need assistance ;-). 

 

Do you perhaps know where i can find some more explination how the bridge lookup works exactly? How are these working together? I really want and need to know more about this as it makes a lot more stuff possible within dynamic blocks. And for my company it will be very interesting :-).

 

Many thanks in advance!

-Patrick

0 Likes
Message 9 of 9

Libbya
Mentor
Mentor

I do not know of any reference material that discusses the function of the double-lookup.  It has been discussed/used a fair amount on this forum.  In my opinion, it is the most powerful tool available within the dynamic blocks.  

 

The basic function when there are two lookup tables linked to the same lookup parameter is as follows.  If you look at the right side of a lookup table you will see 'Lookup Properties'.  On the left side you will see input properties.  When there is only a single value on the Input side that corresponds to a single Lookup property on the right, then 'allow reverse lookup' shows at the bottom of the Lookup Properties.  When the table allows reverse lookup, then when a Lookup Property is slected it forces the input properties to the value for that selection.  When there are two lookup tables linked to the same parameter then if the specific input properties are met for one of the tables then it will behave the same as if that specific Lookup Property was selected on the second table and will change all the properties on the table that allows reverse lookup to their specific value for that Lookup Property selection.  There are quite a few different ways that you can set up the two tables that give different types of functionality.  

 

IMO, the best way to learn how it works is to dive in, flop around for a while, ask questions, etc...

0 Likes