# VisualARQ 2 Beam Cuts not working

**URL:** <https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873>\
**Category:** VisualARQ\
**Created:** [April 18, 2018, 9:57pm UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873 "2018-04-18T21:57:26Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![jwellis394](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jwellis394/32/304037_2.png) [@jwellis394](https://discourse.mcneel.com/u/jwellis394)\
**Post date:** [April 18, 2018, 9:57pm UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/1 "2018-04-18T21:57:26Z")

</div>

I am trying to get a few beams to change the end cut so they come to a taper at one end. I have never had an issue with this.  
I have the beam created via a curve and in the drop down menu the beam’s end and start cute plane is changed however the geometry never reflects this change.

In the beam properties menu I do not have the option to adjust the end miter.

Is this a new bug?

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [April 19, 2018, 7:43am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/2 "2018-04-19T07:43:37Z")

</div>

Hi @jwellis394, Can you send the model where that hapenns to [visualarq@asuni.com](mailto:visualarq@asuni.com)?  
We will check it out.  
Thanks,

---

<div class="post-metadata">

**Author:** ![jwellis394](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jwellis394/32/304037_2.png) [@jwellis394](https://discourse.mcneel.com/u/jwellis394)\
**Post date:** [April 21, 2018, 12:00am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/3 "2018-04-21T00:00:10Z")

</div>

Its like my Visual ARQ says its updated to V2 but I still have all 1.0 tool bars and what not.

---

<div class="post-metadata">

**Author:** ![enric](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/enric/32/624049_2.png) [@enric](https://discourse.mcneel.com/u/enric)\
**Post date:** [April 21, 2018, 7:09am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/4 "2018-04-21T07:09:22Z")

</div>

Hi @jwellis394,

In the main menu, go to Rhino \> Tools -\> Options \> Toolbas, and make sure there is only one “VisualARQ2” toolbar. If there is also a “VisualARQ” (without the number 2), right click over it and select close.

Enric

---

<div class="post-metadata">

**Author:** ![jwellis394](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jwellis394/32/304037_2.png) [@jwellis394](https://discourse.mcneel.com/u/jwellis394)\
**Post date:** [April 22, 2018, 12:57am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/5 "2018-04-22T00:57:33Z")

</div>

I’ve completely reinstalled VisualARQ for Rhino 5 removed all the toolbars. It still won’t show the updated Beam Option menu.

I downloaded the Rhino 6 release and it too doesn’t have the correct menu either.

---

<div class="post-metadata">

**Author:** ![jwellis394](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jwellis394/32/304037_2.png) [@jwellis394](https://discourse.mcneel.com/u/jwellis394)\
**Post date:** [April 23, 2018, 12:43am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/6 "2018-04-23T00:43:15Z")

</div>

Its happening in all my models. I can not get the Beam properties tab to work as the V2 in the tutorials show. Even in Rhino 6 with a fresh install.

Its like the beams are bugged out.

 ![VisARQBeam](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/2/b/2bd2307f2cbbb23f0b4900ab6120e63297fe2f7d.JPG)

No matter the settings the beam profile does not change in Rhino 5 or Rhino 6

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [April 23, 2018, 7:21am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/7 "2018-04-23T07:21:22Z")

</div>

@jwellis394 beams solve their intersection only if they have their end points in the same exact position. From the screenshot, the beams are placed in the XY plane, so you won’t appreciate any change on their cut planes.  
Please send the model to [visualarq@asuni.com](mailto:visualarq@asuni.com) so we can check out what’s going wrong.

---

<div class="post-metadata">

**Author:** ![bjornsmolarek](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/bjornsmolarek/32/767737_2.png) [@bjornsmolarek](https://discourse.mcneel.com/u/bjornsmolarek)\
**Post date:** [June 22, 2020, 9:20pm UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/8 "2020-06-22T21:20:16Z")

</div>

Hello,  
I have the same problems with my custom Grasshopper steel beam, the ends are not connected even though they are in the same position.

Best regards

 ![Beam Problem](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/d/6/d68f4e7270858b6768565489eaca1b9f5b54f689.jpeg)  
[Träger.gh](https://discourse.mcneel.com/uploads/short-url/l7u0i4FUC0FBK8iZB8oTd0YCS7g.gh) (34.3 KB)

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [June 23, 2020, 6:29am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/9 "2020-06-23T06:29:21Z")

</div>

@bjornsmolarek in this case, beams preview in Grasshopper don’t calculate the join. Only when you bake the beams you will see how they join. We are planning to add the option to calculate intersections in GH in future versions.

---

<div class="post-metadata">

**Author:** ![bjornsmolarek](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/bjornsmolarek/32/767737_2.png) [@bjornsmolarek](https://discourse.mcneel.com/u/bjornsmolarek)\
**Post date:** [June 23, 2020, 7:59am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/10 "2020-06-23T07:59:51Z")

</div>

I also have the problem when I use a Visualarq Beam with a Grasshopper definition, whether with or without a Beam Node in the definition. Is it normal that there are no end connections?

 ![Beam Problem2](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/8/6/8671a89b8c029610ff49ed419326ac2d94588eba.jpeg)  
[sicherung\_Träger.gh](https://discourse.mcneel.com/uploads/short-url/9WAR8JycOx94WhZFBv9TnpM3gKA.gh) (48.6 KB)

When baking the Grasshopper file “Träger.gh” it works as you said but it would be great if the definition in the Visualarq element would also work “End Connections”.

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [June 23, 2020, 12:27pm UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/11 "2020-06-23T12:27:23Z")

</div>

@bjornsmolarek Unfortunately beams created with GH styles don’t solve the joints at corners. This is also a feature planned for future versions.

---

<div class="post-metadata">

**Author:** ![bjornsmolarek](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/bjornsmolarek/32/767737_2.png) [@bjornsmolarek](https://discourse.mcneel.com/u/bjornsmolarek)\
**Post date:** [June 23, 2020, 1:55pm UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/12 "2020-06-23T13:55:12Z")

</div>

Many thanks for the info

---

<div class="post-metadata">

**Author:** ![ANDhitecture](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andhitecture/32/504729_2.png) [@ANDhitecture](https://discourse.mcneel.com/u/ANDhitecture)\
**Post date:** [June 25, 2020, 9:38am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/13 "2020-06-25T09:38:46Z")

</div>

@fsalla can you share some thoughts (a workaround) on how to solve the “cut-problem” inside definitions without baking?

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [June 25, 2020, 12:02pm UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/14 "2020-06-25T12:02:52Z")

</div>

Hi @ANDhitecture, you can try to calculate manually the intersection of the beams in GH with some work. Find attached a definition aimed for this purpose, that should work with two beams created from a polyline of two segments.

The definition generates two new beams, a bit longer than the original ones, and after exploding them and obtaining the resulting Breps, the intersection is calculated.[Beam joins calculation.gh](https://discourse.mcneel.com/uploads/short-url/6DnFUtCOOJOg5OCJQg1u2yj50e8.gh) (18.7 KB)

---

<div class="post-metadata">

**Author:** ![ANDhitecture](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andhitecture/32/504729_2.png) [@ANDhitecture](https://discourse.mcneel.com/u/ANDhitecture)\
**Post date:** [June 26, 2020, 10:15am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/15 "2020-06-26T10:15:02Z")

</div>

Basically what I’ve been doing all along.  
It works quite well. Thank you for your input.

But still… it’s not as elegant as I’d like it to be 🙂

I have to ask - when could we expect cuts to work natively?

---

<div class="post-metadata">

**Author:** ![fsalla](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/fsalla/32/548133_2.png) [@fsalla](https://discourse.mcneel.com/u/fsalla)\
**Post date:** [June 29, 2020, 7:02am UTC](https://discourse.mcneel.com/t/visualarq-2-beam-cuts-not-working/60873/16 "2020-06-29T07:02:08Z")

</div>

I don’t know when we will be able to implement the calculation of intersections of VisualARQ objects in GH, but I’ll keep you posted if there are any news.