Move basepoint parameter z-axes with look up

[jarredmonday]

See attached...

I'm trying avoid making more visibilty states or another block to have the three options of "Open Joist, 2x6 & 2x8" options. It's simple to move the basepoint parameter on the z-axes manually and save as a new block. But to duplicate the objects and have a few visibilty states for each one is a bit more difficult. 

[Libbya]

Is there a question in there?  I would not move the basepoint on the Z axis.  I would create a visibility state for each Z position and have the objects at the appropriate z elevation.  

[jarredmonday]

Move basepoint parameter z-axes with look up Can we move the basepoint parameter z-axes using look ups? I was meaning the question to be in the subject line.

I thought you would say that about not moving the basepoint on the z axis. 

My was trying to replicate the Multi-view Blocks that is available in higher versions of autocad than what we are using. 

Thanks 

[Libbya]

As an alternative, you could create the block 'tipped on its side' with the Y axist being manipulated by the lookup, then change the UCS in the host drawing prior to insertion.  That can get confusing for other users, though.  I have a window muntins block that I use in 3D models of houses in that manner.   

[jarredmonday]

See attached please.

Your last solution wouldn't be too much of a problem for myslef, but not for my collegues. But I'll keep that in the back of my mind.

I created all the visibility states and the appropiate look ups. Although, there is a problem and I cannot recognize a solution for. The problem is, when I insert the block or when I use it the fist time, the changes are not visible until I select an option from a lookup. After that it seems to work properly. Also, the double lookup will not have a grip when completed.

Details of the block:

   -The END CAP L & END CAP R toggles the visibility of the end caps. 

   -LOOKUP2 parameter chooses 2X6, 2X8 or OJ

Thank you for any suggestions.

[Libbya · Accepted solution]

If you are using a point parameter solely as input on a lookup table, there is no need for an action associated with it.  No need for the move or the construction circle.  

In order for a double lookup that controls the visibility state to work right off the bat, the default input parameter values must match the lookup row that matches the default visibility state.  The default visibility state is the one that is topmost in the visibility dialog list.  Move your input point so its x vlaue is at 1 and it will work immediately upon insertion.  

[jarredmonday]

That makes sense. Your reply obviously worked once again. 

 Thanks for taking the time to help out.