I guess EnterEnd would be enough.
Thanks @gankeyu
I think there is an inconsitency in the export component. It works for DXF and Step but it requires command line interaction for SKP⌠I guess this could be fixed.
In the new version, weâre trying to use this function in order to avoid using the Command Line, if possible, but need to do more work to think about how the Scheme is set up. It may be that the Command Line is used once to set the scheme, and then this function is used after. Anyway, TBD.
For the existing version, I would think you could use once of these strings as the input for the scheme for the current, Command-Line-based approach in eleFront v4?
I donât have SketchUp so canât test it.
None of these work for me automatically.
And you donât need Sketchup to test this 
Attached is my definition and a Rhino file containing two boxes.
elefront_export.3dm (34.1 KB)
elefront_export.gh (16.4 KB)
The Material Name input is gold for people using Keyshot for rendering. Selecting specific material names will allow Keyshot to automatically assign materials on import⌠
Iâve pushed an update to the PackageManager that has the Boolean input for Bake components added back in. Thatâs the only change thatâs been made for now, just to make it easier for people to continue testing. Weâll address more of the issues found so far in a bigger, later update.
You should be able to find the new version as â5.0.2-betaâ. Thanks again everyone - all of the feedback is extremely useful!
1 Like
Has anybody already tested this on Mac?
Yes I did try it a bit, several times. I donât remember exactly, and I should make a more exhaustive list for developers (@krahimzadeh), but a lot of things do not work the way theyâre supposed to on RH7 macOS. In my recent scripts, every time I wish to use elefront component, I know I should use legacy RH6 components only.
One workflow I am sure has lots of bugs is baking with attributes.
- itâs not possible to bake on child layers - elefront will always create (or bake on) a parent level layer.
- if one try to bake on an existing (parent level only) layer, elefront will always override all layer properties
- object color attributes are not baked
Hi, I found elefrontâs Bake Objects loses its contents when I re-open the gh. file,
Re-referencing objects is really a useful idea if I could keep modifying the object before the bake inside Grasshopper or either keep modifying the object after the bake inside Rhino viewport. But that object synchronous possibility seems just to break if the component canât permanently memorize the data once baked.
I just started to use eleFront currently, and am just getting started to feel like keeping attached to this great app. Thanks!
The normal workflow for this is to bake objects with an identifier such as a bake name, and reference them âby nameâ later in the script (as per the old âdynamic pipelineâ).
Alternatively, you could add a recorder node to the object IDâs. But using the bake name is the more common workflow.
Thanks, Patt, got it! For the alternative, I simply internalize the data inside primitive GUID for the post workflow. I guess whenever it gets to the timing to bake, itâs maybe actually getting close to the documentation process or other things like maintaining and sorting model information; or in early prophase workflow, to reference something that contains some details to prepare for any further complexityâŚ
The Bake component does re-reference the geometry when you bake, but as you point out, it wonât reference any geometry in if youâre opening the script, since the Bake component hasnât been activated.
As @Patt pointed out, you can use the Reference by Bakename component (it looks like you have a BakeName provided to your bake component, so it should work fine) as a parallel stream for scenarios where you are opening the script, and want to reference geometry in without having to bake it again. So it could be something like using a Stream Gate, to choose from the Reference component only in cases where the output of the Bake component is empty.
That said, we can look at adding the re-reference functionality to the Bake component. I can see how that could be useful.
2 Likes
HI @weekenlwk does it count as exciting if I say that weâre actively working on it? Weâve been stress testing it on some other work, but now weâre back to development, and I would expect a major update in 6-7 weeks, which should address a lot of bugs / missing functionality around Blocks, Layers, and Materials, as well as some significant performance improvements.
Thanks for your patience, all!
10 Likes
Thatâs absolutely exciting news for me. And I am very grateful for all your effort and the awesome ideas for the workflow made in the plugins. Keeping trying my new thought of method on the beta elefront plugin is one of my interests on BIM job 
Thanks a lot for your efforts.
Also the âsome other workâ is a very good sharing. Thanks again!
I think I have identified a bug with the automatic population of Value Lists in the Beta version. When I connect a Value List, it is not modified to show the contents of the Rhino Doc.
Thanks. We hadnât ported that feature over as of this release, but it has already been updated for the upcoming final release.
2 Likes
Iâm also interested in this question by @tay.othman, and I have another one.
Iâm currently sometimes running into the same problem as @tay.othman because of AutoGraph. Is there currently a way to convert the Data Descriptions into Relays?
I understand that AutoGraphâs hotkeys will be integrated in the Canvas Management feature of eleFront v5.0. This should solve the AutoGraph incompatibility issues from eleFront v5.0 onward, right?
I like being able to see the Grasshopper component icons. I think itâs easier to recognize components that way. However, the Data Description components are not so useful when Display > Draw Icons is toggled on, unless you select the âAlways draw nameâ option of the Data Description components.
Is it, or will it be possible to make the âAlways draw nameâ option of the Data Description components be the default behavior of the Data Desciption components?
1 Like