I posted a reply in this thread before realizing it’s limited to ‘Grasshopper Developer’ instead of the whole GH forum, so will re-post that reply below:
I found this thread in my quest to work around the bleeding edge deficiencies and glaringly obvious flaws in R6. This snippet of Python looks very promising except that when I open that GH file, not only is the Cone not visible in the Rhino wiindow but any other geometry I add to the GH canvas also isn’t visible!?? How absurd is that!? Another in a very long list of wild goose chases in the pursuit of basic functionality that is sorely missing from Grasshopper itself.
Two years ago I cobbled together a simple Python ‘bake to layer’ component from examples found on the forum. It worked great at the time but has no ‘M’ input for material, depending as it did on the material being defined on each layer in the .3dm file. Now I’d rather avoid.that dependency, which is why I’ve extended the C# code for creating materials in GH that are suitable for viewing and baking with Custom Preview.
I’d like a Bake to Layer component that accepts the same ‘G’ and ‘M’ inputs as Custom Preview. I might eventually figure it out myself but would rather focus on my own project instead of coding GH “enhancements” that should have been built in years ago.
I would post my old Python Bake to Layer component but it appears to be broken now.
I’m aware that some plugins like Elefront offer this kind of functionality. Why must I become dependent on a plugin for a basic, low level capability like this that should be built into Grasshopper? SERIOUSLY?