Grasshopper Baking

General
1

Hello,

I just started experimenting with the local version of Orkestra today. I am really impressed with the concept so far and I’m fascinated by how it could enhance our design process! I haven’t tried it yet but OkPy also looks really interesting for our purposes.

I’ve run into some issues with baking after running a GH script from the Rhino window. The preview function works very well, but when clicking “Run” in the dialog I am not able to get geometry to bake from the “Context Bake” node (which I found suggested in the v1.8.0 release notes).

I’ve tried the “Content Cache” node too but I’d rather not have a separate button in the UI for baking or have to work out logic to trigger the baking event. If I hard code the “Content Cache” action to True, the action will repeat the continuously even after the Orkestra command has concluded (I guess this is because Grasshopper is still running in the background.)

I’ve also tried tagging nodes with “out” but this doesn’t seem to have anything to do with baking.

What I’d like is to run the same GH scripts as a Grasshopper Player command OR in Orkestra with a dialog where the resulting geometry is baked at the conclusion of the script.

Overall, it is a bit unclear to me what the proper implementation is from what I could find between the wiki and the release notes. Some example GH files would be very helpful!

Thanks!

1 Like
2

Hey there @DomenicG !
Welcome to the forum :slight_smile:

I just realized your post got flagged for some reason and was not publicly visible. Hopefully all your next posts will be published directly!

First of all, thanks for the kind works! Super happy you see potential in Orkestra and OkPy!

but when clicking “Run” in the dialog I am not able to get geometry to bake from the “Context Bake” node (which I found suggested in the v1.8.0 release notes) .

Yes the context bake should normally bake when hitting the Run button. Are you able to provide a minimal reproducible case of the issue ? I just gave it another test and it seems to work as expected.

3

Here are some scripts that might help reproduce the issue:

When I run the script with parameters and sliders marked with “ok” the form shows up as expected, but when replacing them with the Grasshopper Player parameters, I get this error and the form does not appear. Maybe whatever is causing this is similarly effecting the Context Bake node?

image
image1024×551 45.9 KB

Here is my SystemInfo from Rhino in case that’s useful to you:

Rhino 8 SR20 2025-6-6 (Rhino 8, 8.20.25157.13001, Git hash:master @ 73b00899cf43922900a763212f167c03dc6f27cc)
License type: Commercial, build 2025-06-06
License details: Cloud Zoo

Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 32GB)
.NET 8.0.14

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA RTX A2000 (NVidia) Memory: 6GB, Driver date: 5-14-2025 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 576.52
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 5-14-2025
Driver Version: 32.0.15.7652
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 6138 MB

Rhino plugins that do not ship with Rhino
C:\Program Files\Orkestra\Orkestra\net7\OrkestraRGH.dll “Orkestra Online” 2024.1.9.8
C:\Users\domen\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\Speckle.Connectors.Rhino8 (2153799A-0CEC-40DE-BC3A-01E5055222FF)\Speckle.Connectors.Rhino8.rhp “Speckle” 3.4.0.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.20.25157.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”

1 Like
4

Thanks so much for sharing this!
With this I do realize there is a new geometry type we don’t account for in Rhino8 (Rhino.Geometry.Extrusion) . We’ve added it and it will be fixed in 1.9.9 .

However , I don’t get the error message you have with the grasshopper player inputs!
Did you by any chance have an older version of Orkestra installed prior to 1.9.8 ?

5

I only started working with Orkestra last week so 1.9.8 is the only version I’ve ever downloaded.

1 Like
6

Thanks a lot for all the valuable info! I am able to reproduce the issue with the latest version of Rhino 8 ( 8.20.25157.13001 , june 6th 2025) . Will update this thread shortly :slight_smile:

7

There was a change in namespaces in this last minor releases of Rhino 8 (!)
For example, “ContextualComponents.GetGeometryParameter” became “IOComponents.Contextual.GetGeometryParameter” . Not a hard fix because the methods etc. seem unchanged . We’re going to adress this and issue a new release.

1 Like
8

Alright so this explains everything you’ve been experiencing. The bake not working, the GH inputs faling to load etc.
We need to test this some more but you can expect a new release within this week fixing all of this.

1 Like
9

Alright @DomenicG here’s a test release (not fully tested so might have bugs here and there). It would be extremely helpful if you could try it out and would help us confirm that we have all related issues fixed.

I’d recommend uninstalling any version of Orkestra you have prior to installing this one :slight_smile:

Orkestra v.1.9.8.6.msi

1 Like
10

I’ve installed this new version, and everything seems to be fixed. Thanks for working this out so quickly!

1 Like
11

Awesome thanks so much for the prompt update! :slight_smile: This will help us accelerate the official release. :rocket: :rocket: