# Wish: Tune up MoveUVN

**URL:** <https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724>\
**Category:** Serengeti (Rhino BETA)\
**Created:** [July 15, 2020, 10:45pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724 "2020-07-15T22:45:34Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Hutchinson](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jonathan_hutchinson/32/525272_2.png) [@Jonathan\_Hutchinson](https://discourse.mcneel.com/u/Jonathan_Hutchinson)\
**Post date:** [July 15, 2020, 10:45pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/1 "2020-07-15T22:45:34Z")

</div>

I’m not sure what to suggest. But the U and V pointers could just be improved. On a big 24 inch screen, they are still barely visible, this is a single maximised viewport. Maybe the control polygon being coloured in red/green (likee the use UV wires mode for stuff that’s shaded) could be a possibilty. Or what about a U / V character attached to the nearest U/V row to the camera by distance. Or maybe an arrowhead?

Since it probably pertains most to MoveUVN, perhaps it should be like a tickbox for advanced HUD, or something.

Easy wins: Ability to amend the thickness of the marker, maybe that would help? Anyway, I think there’s something amiss with the logic of the scale.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/b/c/bcf40564118cb7cf576b74b3c202ef727f585e45.png)

---

<div class="post-metadata">

**Author:** ![pascal](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/pascal/32/479395_2.png) [@pascal](https://discourse.mcneel.com/u/pascal)\
**Post date:** [July 16, 2020, 3:45pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/2 "2020-07-16T15:45:51Z")

</div>

Hello - if you are referring to the little green and red stubs on the control polygon, those are not related to MoveUVN. They follow the CPlane X and Y colors so you can make them brighter that way, but I agree it would be better if there were somewhat more visible markers - currently the sizes are some proportion of the control polygon segment so they can be quite small on a denser surface. Basically we need a better way to indicate surface U and V… I think that is the underlying message here, correct?

-Pascal

---

<div class="post-metadata">

**Author:** ![Cadworx](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/cadworx/32/478797_2.png) [@Cadworx](https://discourse.mcneel.com/u/Cadworx)\
**Post date:** [July 16, 2020, 5:53pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/3 "2020-07-16T17:53:40Z")

</div>

I really like the concept of a “Control Point Gumball” for UVN modelling. This would add precision and good visual feedback:

 ![CV_Gumball](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/3/f/3f68dd406cd713792d583e6318c01ae49b8bf766.png)

---

<div class="post-metadata">

**Author:** ![Jonathan\_Hutchinson](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jonathan_hutchinson/32/525272_2.png) [@Jonathan\_Hutchinson](https://discourse.mcneel.com/u/Jonathan_Hutchinson)\
**Post date:** [July 16, 2020, 6:46pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/4 "2020-07-16T18:46:27Z")

</div>

Yeah I get that they don’t appear because of MoveUVN - although MoveUVN is the tool they are most useful for in my experience. That’s why I feel like an override in that panel would be helpful. Just so that folks who don’t want to see something different, aren’t faced with the option until they need it, per se. Inside Rebuild for example, It’s always quite clear temporarily about the directions you’re affecting. Good to know regarding the colour link to CPlanes

Yeah I wonder if the proportion could be amended in some way. I don’t know, could it relate to the viewport size in pixels in some way?

Also, I can’t for life of me rmemeber how I used to get the N direction displayed for a control point. I’m certain in the past there was a way to get a blue stub.

> [@Cadworx](#):
>
> ![CV_Gumball](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/3/f/3f68dd406cd713792d583e6318c01ae49b8bf766.png)
> 
> CV\_Gumball719×585 12.8 KB

Hey… yeah. Psychic… And then an arrowhead so you see the +ve direction

> [@Jonathan\_Hutchinson](#):
>
> Maybe the control polygon being coloured in red/green

---

<div class="post-metadata">

**Author:** ![Cadworx](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/cadworx/32/478797_2.png) [@Cadworx](https://discourse.mcneel.com/u/Cadworx)\
**Post date:** [July 16, 2020, 7:10pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/5 "2020-07-16T19:10:04Z")

</div>

> [@Jonathan\_Hutchinson](#):
>
> And then an arrowhead so you see the +ve direction

What do you mean by +ve direction? Tangent Extension?

---

<div class="post-metadata">

**Author:** ![Jonathan\_Hutchinson](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jonathan_hutchinson/32/525272_2.png) [@Jonathan\_Hutchinson](https://discourse.mcneel.com/u/Jonathan_Hutchinson)\
**Post date:** [July 16, 2020, 7:24pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/6 "2020-07-16T19:24:51Z")

</div>

In MoveUVN, you drag the sliders for positive or negative. Or use positive/negative values in the Scale value input. In the same way, rebuild has the arrow for the ‘direction’ of UV, which I presume is the ascending domain.

![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/8/b/8bc7198c6917c8684aeda93559260d3a9a60bc30.png)

---

<div class="post-metadata">

**Author:** ![Cadworx](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/cadworx/32/478797_2.png) [@Cadworx](https://discourse.mcneel.com/u/Cadworx)\
**Post date:** [July 16, 2020, 7:41pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/7 "2020-07-16T19:41:48Z")

</div>

Like this?

 ![Extend2](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/a/3/a34e6370ec6f9f29b6f23959d4935190cd5afca8.png)

---

<div class="post-metadata">

**Author:** ![Jonathan\_Hutchinson](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jonathan_hutchinson/32/525272_2.png) [@Jonathan\_Hutchinson](https://discourse.mcneel.com/u/Jonathan_Hutchinson)\
**Post date:** [July 16, 2020, 7:49pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/8 "2020-07-16T19:49:21Z")

</div>

I’m only really interested in the control polygon direction. Given that this then implies what the extension direction is.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/0/8/08bab9f0c405642897cd05d34c6753f585e82ca1.png)

Although if this was something tucked away for MoveUVN only, depending on which radio button you have could change the arrows displayed? (tang / cp / ext)

---

<div class="post-metadata">

**Author:** ![Cadworx](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/cadworx/32/478797_2.png) [@Cadworx](https://discourse.mcneel.com/u/Cadworx)\
**Post date:** [July 16, 2020, 8:04pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/9 "2020-07-16T20:04:03Z")

</div>

Yes, the light blue arrows are supposed to be “theoretical”. The idea is to not constantly follow the polygon, but rather travel along the extentension.

I think we both mean the same thing.

![CP-Direction2](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/7/3/73b380267dd61b4db4d8c2f6e6f27b64dda6a858.png)

---

<div class="post-metadata">

**Author:** ![theoutside](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/theoutside/32/473900_2.png) [@theoutside](https://discourse.mcneel.com/u/theoutside)\
**Post date:** [July 16, 2020, 11:17pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/10 "2020-07-16T23:17:19Z")

</div>

written up-

[https://mcneel.myjetbrains.com/youtrack/issue/RH-59546](https://mcneel.myjetbrains.com/youtrack/issue/RH-59546)

---

<div class="post-metadata">

**Author:** ![Jonathan\_Hutchinson](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jonathan_hutchinson/32/525272_2.png) [@Jonathan\_Hutchinson](https://discourse.mcneel.com/u/Jonathan_Hutchinson)\
**Post date:** [July 17, 2020, 1:21am UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/11 "2020-07-17T01:21:57Z")

</div>

For sure. The “wrong” direction is the MoveUVN: Along control polygon option though, which still has its uses. So yes by mixing the Along control polygon and Along extensions mode, you can travel any distance along either of those two blue arrows you drew.

Like you say, we both mean the same thing. Some way to better visualise UV direction when control points are on 🙂

---

<div class="post-metadata">

**Author:** ![Cadworx](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/cadworx/32/478797_2.png) [@Cadworx](https://discourse.mcneel.com/u/Cadworx)\
**Post date:** [July 17, 2020, 12:51pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/12 "2020-07-17T12:51:58Z")

</div>

What exactly was written up? The project is not publicly visible and just shows a “404”.

---

<div class="post-metadata">

**Author:** ![norbert\_geelen](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/norbert_geelen/32/476003_2.png) [@norbert\_geelen](https://discourse.mcneel.com/u/norbert_geelen)\
**Post date:** [July 17, 2020, 3:13pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/13 "2020-07-17T15:13:16Z")

</div>

Yeah, that seems to happen all the time with Youtrack.  
Any ideas why, @theoutside ?

---

<div class="post-metadata">

**Author:** ![pascal](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/pascal/32/479395_2.png) [@pascal](https://discourse.mcneel.com/u/pascal)\
**Post date:** [July 17, 2020, 3:39pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/14 "2020-07-17T15:39:13Z")

</div>

Try now…

-Pascal

---

<div class="post-metadata">

**Author:** ![norbert\_geelen](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/norbert_geelen/32/476003_2.png) [@norbert\_geelen](https://discourse.mcneel.com/u/norbert_geelen)\
**Post date:** [July 17, 2020, 4:16pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/15 "2020-07-17T16:16:59Z")

</div>

Works now, thanks!

---

<div class="post-metadata">

**Author:** ![Cadworx](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/cadworx/32/478797_2.png) [@Cadworx](https://discourse.mcneel.com/u/Cadworx)\
**Post date:** [July 17, 2020, 4:58pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/16 "2020-07-17T16:58:10Z")

</div>

Here is how I think this could work. To get that Gumball “feeling” of using a handle,  
each Control Polygon is split at the middle. You do not grab a Control Point, but the handle on either side “A” or “B” , which fully defines a Control Point and the corresponding tangent with a single click.

Additionally this would also solve the “shallow angle” problem between the tangent extention and the “next” Polygon.

 ![CP_GB2](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/2/4/24bc5d14a8e1c580154ca24cf75c6073c6d7d273.png)

This of course works in all four directions:

![CV_Gumball_select_handle](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/a/1/a1b732bcacfad5f348fa1a5b4e8c0e11b1c03411.png)

There are two way of activating the Control Point Gumball:

- By picking a Control Point, the Gumball shows up, or

- To intitially have no handle visible and as you move the cursor near one handle, it lights up, which would save one click.

 ![Cursor](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/1/e/1e1ab66eea8f60715f42a7873518485a391a73b1.png)

> [@Jonathan\_Hutchinson](#):
>
> Along control polygon option though, which still has its uses.

If you want to work this way, you simply pick the handle on the other side.  
This way a “Control Point Gumball” can do tangent extention as well travelling along the polygon the “wrong” way!

---

<div class="post-metadata">

**Author:** ![eobet](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/eobet/32/769335_2.png) [@eobet](https://discourse.mcneel.com/u/eobet)\
**Post date:** [July 20, 2020, 9:54am UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/17 "2020-07-20T09:54:22Z")

</div>

I’ve always found it a bit amusing that the scripts that @Pascal produces have way better UV direction indicators than the built-in ones:

![bild](https://global.discourse-cdn.com/mcneel/uploads/default/original/3X/3/0/30717cd10c4c608ffa1c03060a788ee6ae46586b.png)

Like, why can’t that be the default? (Although the dot should be drawn in front of the arrows.)

---

<div class="post-metadata">

**Author:** ![a.tchoukanov](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/a.tchoukanov/32/221979_2.png) [@a.tchoukanov](https://discourse.mcneel.com/u/a.tchoukanov)\
**Post date:** [July 20, 2020, 4:31pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/18 "2020-07-20T16:31:06Z")

</div>

Pascal, will your Align Grips tool make it into V7 as a standard build?  
Pretty please.

---

<div class="post-metadata">

**Author:** ![norbert\_geelen](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/norbert_geelen/32/476003_2.png) [@norbert\_geelen](https://discourse.mcneel.com/u/norbert_geelen)\
**Post date:** [July 20, 2020, 7:05pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/19 "2020-07-20T19:05:58Z")

</div>

Hey, which @pascal sorcery is that from?

---

<div class="post-metadata">

**Author:** ![pascal](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/pascal/32/479395_2.png) [@pascal](https://discourse.mcneel.com/u/pascal)\
**Post date:** [July 20, 2020, 7:07pm UTC](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724/20 "2020-07-20T19:07:18Z")

</div>

@a.tchoukanov `AlignGrips` is indeed in v7.

-Pascal

[Next page](https://discourse.mcneel.com/t/wish-tune-up-moveuvn/105724.md?page=2)