I created a custom display mode with light lines, but unfortunately itâs not static and will change with the camera position. lightlines.ini (13.5 KB)
Also, the following topic consists plenty of suggestions for Blend surface and Match surface.
Itâs extremely important to add two separate options âMatch target isocurve U directionâ and âMatch target isocurve V directionâ. Currently, Rhino has a common option for both directions and this is why often times âBlend surfaceâ gets confused which direction to use, so it ends up using both and creates messy surfaces.
The best I can do for you is this:
Make an environment, assign this hdri
(Itâs a jpeg I found and then modified into a HDRI)
Rotate the environment setting 90 degrees if you need.
Double tap the icon to Use the environment.
And change viewport background to black.
It isnât a one click solution, but itâs not too far from being a tool thatâs quick to toggle on and off since we can just double click environments to activate them.
(And obviously I donât model cars for production )
EDIT: Rhino 7 crashed when I loaded the environment map⌠I tried again, but seems like I canât make the stripes visible in the viewport. Rhino crashes every time when I want to change the type of projection⌠Even if I use a new scene with a simple sphere.
To avoid spamming the thread you can send me your systeminfo in a personal message. Maybe the image fills your vram. Iâll make a lower res version.
Edit: I changed the name of the HDRI now since it had â+â in the name, and added a compression that Rhino can use. And I made a half res version in the zip too.
Try that and update your graphic card driver if it still crashes.
Hello all,
today a new version 1.1 of the Cyberstrak PlugIn was made available: Downloads - Cyberstrak
The Blend example from Bobi should work now much better. Like Mark wrote, it was mainly related to degree 1 or planar input surfaces. Also the transitiion analysis showed sometimes strange results there.
In addition a graphics issue was fixed mentioned in another thread.
Blend surface seems to work much better now.
One thing I stumbled upon: Moving the endpoints of blend edges to perform a partial blend seems to work sometimes, but often not.
I was able to move the point on one edge, but unable to grab the other one on the same edge, or either one on the other.
Okay I did some more testing and got the points to move, but they are really difficult to select, maybe a graphics problem?
Match surface works better too, but still has some erratic behavior to it.
From what I can tell problems only occur with g2 match, which is a bit tricky to get to work.
It seems not to do anything unless âadapt degree/spansâ is selected.
âBlendâ doesnât do anything, as far as I can tell.
One question:
Shouldnât the âmatch qualityâ buttons in âblend surfaceâ and âmatch surfaceâ be exclusive on selection?
At the moment I can select any combination, for instance matching to g0 and g2, but not g1.
Shouldnât the highest g value automatically contain all levels under it and therefore make selection of the other buttons redundant?
Or am I missing something?
While building a blend surface with the plug-in, the handles are extremely difficult to use. 90% of the time I canât make them move, even though they change their colour as an indication that the mouse pointer is on them.
There are not sliders to control the G2 curvature, too. I can see only sliders on the surface to control the 2nd row of control points. And no numerical input to make the changes more accurate.
Also, during that time I can still select and move other objects by accident, which is highly risky as the model can get destroyed by accident.
Sliding an end point to change the range of the blend surface also resets the changes to the 2nd row of control points done by the slider. Pressing the âApplyâ button also resets the changes, which is counterintuitive, because this is not a âResetâ buttonâŚ
The Matching tool will not let me choose a specific surface edge. Seems like it always likes to match to the same surface edge which I never click.
Also, after I select the G2 curvature match and then deselect it and try the Position instead, the surface never goes back to that state and is left with Curvature forever.
The CSCVModeling tool is a real joy to use, with very minor cases when the arrow handles will not register my mouse movements. I wonder why Rhino lacks such a great tool by defaultâŚ
Hi Norbert and Bobi,
working on the Blend command right now, just have found the bug resetting moved tanget row when pressing Apply or moving the partial handle.On my computers I donât see the effec, that handles cannot be moved, needs further investigation.
Yes, if you select higher matching quality it includes the lower settings (so Curvature includes Tangency and Position). Maybe the minor quality toggles should automatically be switched on.
Concerning the remark surface doesn not go back: I have to look there, but with local Undo inside the dialog you can always go back to the beginning. And if you leave the command with Cancel you should receive the status in Rhino before you have entered the command.
With OK you can also use Rhinoâs Undo to go back. So you should not lose anything.
Very excited to tag along and watch the development of this plugin. As a long time user/whiner of lack of surface tools Iâm eager to see this project come to life! Thanks for developing it!
This plug-in is very aggressive and once I load Rhino 8, it opens the Sybestrack dock bar every time, despite that I keep it closed at any time. This also causes Rhino 8 to load much slower.
That panel also opens in Rhino 7 initially, but several seconds afterwards it closes automatically.
There is also a weird bug with the CSCVModeling tool. If you try to apply it to the middle surface in the attached file below, it will totally mess up its structure and make it warped at random locations. Cyberstrak fail.3dm (257.3 KB)
Hello Peter,
I am very excited to learn about this new project! Really amazing, and i am very thankful for your effort!
But really important to know is, what kind of features are you planing to Implement?
The featureset It has right now, is exciting, but far from complete.
It would have to have quite a bit more tools for it to allow for a complete workflow.
I am very curious on what your intended tools-palette is!
I am totally in favor to concentrate on a small but robust toolset, that still allows for a decent workflow-
so i can´t wait for a roadmap on where cyberstrak is heading!
so my solution would be to remember in the preferences if the dockbar should be visible or not. If you switch it off then it would not come up in the next session until you activate it again. Does this sound ok?
I want to bring it up as default, because it contains some useful stuff for the Cyberstrak commands (e.g. you can change the draw appearance of the selected objects while commands are runnning).
I did not see the effect yet that Rhino 8 is loading slower or that it appears/disappears in R7. Do you mean the start up time or the time for loading a file?
I agree with Bobi that the dock bar should not automatically load when you start Rhino. Yes it is helpful when using Cyberstrak commands, but a lot of modeling is done with regular Rhino tool and it take up a lot of screen space.
Second I would like to suggest to make this part of the panels instead of a floating window. Anytime you would start a Cyberstrak command it would bring the Cyberstrak panel to the front and you can adjust settings as needed.
When you finish using Cyberstrak commands, you can bring back a panel that is most useful to you like Layers or Object Properties.
It takes more than 10-12 extra seconds to load the Cyberstrak dock when I start Rhino 8. Not to mention that the program freezes for a moment and then it takes a few more seconds and an extra mouse click to manually close the Cyberstrak window afterwards.
In my opinion, the Cyberstrak dockâs window must not show up automatically, unless the user specifically ask to do it manually. There may be an option whether that window will appear right after activating certain Cyberstrak tools or will require a press of a button to be seen.
It would be best if that bug is non-existing in the first place, because I see a major drawback with it currently. Lets say that I make important adjustments to either end of the surface and then figure out that one of the sides no longer can go back from G2 to G1 or G0, because the plug-in refuses to to so. In this case, using the internal Undo of the plug-in is not a sufficient solution, because I will also lose the important adjustments on the opposite end of the surface. With other words, if I use the internal Undo to fight that particular but, I will literally be forced to redo the work on either end of the surface.
Hi Bobi,
the hint with the Undo was just a quick work around. The Blend issue I have already fixed, it was a strange bug introduced by a change (I should improve my regression testsâŚ).
Iâm looking now to the dockbar.
)
