I also propose to replace the square tickboxes for the “Tangent” and “Curvatire” with round ones, because in Rhino this is how they work in a more logical way:
Square tickboxes are used to turn on or off non-mandatory secondary options, such like the analysis options in your “Surface blend” window;
Round tickboxes are used to switch from one main (mandatory) option over another, such like: either “Tangent” or “Curvature”.
Also, the two buttons to pick surface edges are named differently, whereas they should have be named similarly (except for the numbers 1 and 2). Currently, the button for the first edge is called “Select edge 1”, while the one for the second edge is called just “Edge 2”. This also may look more consistent if you simply name them “Edge 1” and “Edge 2”, respectively.
I noticed a bug yesterday with control point modeling. I was trying a move a CV tangent and when I zoomed in the handles got really big and I could no longer grab them with my mouse and in some cases the handles and the surface I was trying to modify would disappear completely.
Hi Peter,
I noticed that in cyberstrak is not possible to flip the direction of the surface blend, and if I remember well that was possible in VSR, which sometimes is very useful, for example to get an average blend of 2 patches.
Hi Jordi,
in the new version I will upload soon I fixed some bugs concerned to twisted blends. If possible, I would like to implement a good automatic detection for the edge and direction orientation, so if you send me your example I will have a look.
At the end I may anyhow need to add some orientation help (toggle or something on the handle)…
Hello Mark,
just to understand the problem: Do you work in central perspective? I have an algorithm calculation the handle size in pixels from their 3d size, but in central perspective it may need some improvement.
It seems to be in perspective view, related to the scroll wheel for zooming in and out. Something has changed with the navigation in the last few releases of Rhino (for the worse), there seems to be some recalculation of bounding boxes/view frustums or something and it gets it terribly wrong, especially if you have a lot of other large geometry showing at the same time. This results in the scroll wheel zoom not working, also rotation centre can ping off somewhere else. I think the Cyberstrak arrows go funny when this happens.
I’m also finding the Cyberstak arrows very chunky and intrusive. Is there any way we could have something more delicate or perhaps make them transparent by a percentage?
The possibility to flip the blend orientation is crucial and cannot be replaced by “automagic” detection of the supposedly “right” orientation, because there is no way the software can read my mind
in the first time I did not understand the issue correctly, after Jordi sent me the example I did. This will not come with the next update, but there will be a solution.
I see that you have quick keys implemented on the CV Modeling (very exciting!!) - is there any way to suppress the CLI when the tool is active? In VSR, it would still go through to the CLI, but there was a prompt in the command line that the quick keys would dump into, instead of just the “open” CLI if that makes sense:
The VSR workaround here was perfectly fine, because when you closed out of the tool, it would clear out the CLI of all the quick key inputs. I see that Cyberstrak does this in that the CLI clears, but when you use quick keys in the command, the CLI keeps auto completing commands, which can be a little distracting:
Hello Sky,
the CV Modeling in VSR was using internally the point selection of Rhino, which caused some other problems… (e.g. you needed to abort selection loop before starting some other tools). In Cyberstrak, the CV handles are a 3d tool. Unfortunately keyboard events are not only captured by the 3d handle, but also by Rhinos “CLI” (Command Line Interface?). I asked at the McNeel dev conf if something could be done about this and noticed, in Rhino 8 the keys in the graphics area do not influence the command line anymore. I asked but nobody was telling me is this was changed by intention. So I hope it was.
Hi Peter,
I would like to ask you for a very useful option that blend command has in Icem surf, that you may know very well, and is the possibility to slide the blend patch onto the base surfaces by its iso.
For me, save a lot of time in many occasions when creating new patches, cause there is no need to trim the base patches previosly or duplicate and split them, etc… and also you can blend surfaces more intuitively, without restriction, like in the blend curve command.
