I never realized that if you activate “Only draw preview geometry for selected objects” and selected a param viewer, this would draw dots indicating the branches and item numbers of objects in the Rhino viewport.
Nice !
But then, obviously, I wanted to bake them, which is way simpler than doing all the fiddling with other components to achieve this…bummer. There’s no “Bake” on the Param viewer component.
Bake them from the Orient component.
I’m not at my computer and I have not tried this but maybe the dots can be baked using a shortcut for bake selected. I’m using the insert button for this.
This does not work
This does not work neither
Maybe you can share the definition so we can figure-out what’s happening there.
There really isn’t anything to look at. The dots created by Param Viewer cannot be baked.
Brep Topology is a similar component which displays face indeces and the component right click menu even has a bake option but it is greyed out…
Yeah, thus my wish that they could.
1 Like
Hi Olivier -
On the list → RH-84364 Grasshopper: Bake Preview Info From Param Viewer
-wim
3 Likes
Hi @osuire,
Bake on components use to Bake the actual data the component contains, in your screenshot some user may expect that the input geometry is Baked but not the dots.
What’s you expectation? The geometry and the dots should be baked? Only the dots?
I’m more interested to understand how would you use the result of the Bake.
Thanks in advance for your thoughts.
1 Like
Dear Kike,
One expects “Bake” to bake whatever is highlighted when a component is selected, right ?
This answers your question.
Would be nice to understand how would you use the dots once are baked on the model.
This would help me understand better how this is going to be used.
Are you trying to establish if my request is relevant / has merit / is legitimate ?
How about using it to label a bunch of stuff easily without having to thread a bunch of components to obtain the very same effect ?
If I may add another request : give out a warning when one wants to display these dots and they are over .
Indeed, with some large trees, it will take GH forever to display them and the only resort is to kill the Rhino.
Param Viewer is showing the preview since 8.12.
This was added to allow the user recognize on the viewport which piece of geometry is on which branch and index. This feature is done and finished.
I’m glad to implement what you are suggesting, but yes is part of my job try to understand how a feature is going to be used and prioritize based on that.
I’m just trying to understand how can be used all these dots on the document latter in a real workflow.
Don’t get me wrong, I’m asking because maybe I learn something of your answer.
Your last request is fixed and will be available on next 8.14.
1 Like
Well, apart from using it to label the stuff that you bake, what could it be good for ?
Anyways, please consider adding some sort of warning buffer before displaying tens of thouthands of dots*
Rhino always had a hard time displaying them when they start being too numerous, and I had to crash Rhino several times because of this.
*even better : improve the display of large number of dots.
1 Like
I tried to improve the preview performance by degrading it dynamically.
It shows a maximum of 1.000 tags.
If there are more than 1.000 visible on screen it turns to plain dot mode.
If there are more than 100.000 items, visible or not, is considered huge and it previews just the bounding box.
1.000 tags perform well and more than 1.000 are really hard to read anyway.
1 Like
Smart !
The thing is given the fact the users are dealing with huge amount of data on this component and that once baked these dots will not perform well I see more trouble than benefits on implementing Bake on it.
I see the point on consistency between preview and Bake you mention but given the issues above I will pospone Bake until dots perform like crazy on Rhino.
Ok, it’s no big deal anyways.
At least you have prevented this new dot feature from becoming a ticking crash-bomb.
This brings back the discussion about the ability to crash GH without crashing Rhino.
I hope that it will be the case with GH2.