A Dynamic block for a Bolt with a Nut.

[mohannad_3bdo]

Hi All;

  I created a dynamic block for a Bolt with a movable nut, the block has an array action to add a new threads associated with a stretch action, the problem is the new threads that generated by the array action goes up the movable Nut. 

Is there anyway to make the new generated threads goes under the movable nut ?

   I've attached the dynamic block.

   Regards.

[h_s_walker]

Unfortunately not. Any arrayed object in a block is treated as a new item and is drawn "on top" of linework which is already in the block.

[JamesPowell7164]

Could you put a wipeout under the nut but on top of the bolt so that it covers all of the threads and moves with the nut?

[j.palmeL29YX]

With a little cheating ... try the attached attempt. 

[j.palmeL29YX]

---

@JamesPowell7164 wrote:

Could you put a wipeout ...

---

Not tested, but I'm afraid, each new created array item will be placed in front of the wipeout too. 

[Washingtonn]

Use three blocks. one for the bolt, one for the nut, and another for the assembly of the nut and bolt.  The insert point for all of the blocks should be where the threads meet the washer face.  The washer has a stretch parameter and has a drawing order above the threads. The bolt as previously drawn (except for moving the insert point and associated changes).

Insert the assembly with explode to leave 2 blocks. Then you can move the nut, lengthen the threads and maintain the desired look.

[MMcCall402 · Accepted solution]

This is my attempt to solve it.  My thought was "If the arrayed items get drawn last, what happens when two arrays overlap each other, which one gets drawn last?"  The answer, the one that gets altered/moved last.  Also, only the arrayed items are considered "new" items, not the original item chosen to be arrayed.   So, I made the nut into a tiny little linear parameter & array (0.001). This made 1 new item in the array that is basically in the same place.  Then I included it the stretch action for the nut.  This draw order works as long as you move the nut last.

Update!   I added a Move action to the parameter for the length of the bolt, selected the parameter for the placement of the nut, chained the action and set a distance multiplier of 0.0001.  This makes the nut move when the bolt length is changed, which results in the nut array always being drawn last.

[mohannad_3bdo]

I tried to make a wipeout, but the same result, the new threads are generated above the wipeout too.

 Thanks.

[mohannad_3bdo]

Thank you very much. It's so helpful.

 Regards.

[mohannad_3bdo]

Thank you, it works fine.
Could you please tell me how you did it ?
Regards.

[j.palmeL29YX]

---

@mohannad_3bdo wrote:

Could you please tell me how you did it ?

---

I used 2 arrays (Path array, not array action), one above the nut which fills the room between the nut and the head an a second to fill the room between the nut and the end of the bolt. 

But the solution posted by @MMcCall402 is much more better. All my thumbs up! 😉