I’m attempting to create a script for Grasshopper Player that generates new walls and connects them to existing ones. However, I’ve discovered that the Context Bake component appears to function only on a single object at a time.
Here, you can see two wall objects whose geometry needs to be replaced with a new one. In a grasshopper test I have two objects and two replacing geometry.
However, it only works for the single wall. Here you can see baked result from Grasshopper Player. I attempted to reverse the objects list, but they just switched their sides, and one wall remains not replaced.
my first thought is that you might be missing something
I’m not a superuser of the new Rhino components yet, just studying them from time to time, but if you reference one Model Object (from a layer or whatever) then you change the geometry linked to that single Model Object with multiple geometries, you of course Pushing it will repeatedly overwrite the very same model object and only the very last one will show up in Rhino
simple example, the Sphere gets overwritten by the first box, then from the middle one, then from the top one, and that is because you are rewriting the very same Model Object the sphere was:
I’d share a script but there are 300 nodes which may bring more confusion, so I made simple test to recreate a problem which you can see at the last screenshot
No, in my last test with cubes, I used three different objects and provided for each new geometry. The Content Cache component works well and replaces both objects. However, I can’t use CC with Grasshopper Player because it overwrites objects in real time, creating a mess. Additionally, it makes the viewport laggy since it updates each millisecond.
You should not be constantly pushing in such a case. Only display a preview while the user in providing inputs for your grasshopper player command and keep your content cache at the end of the script with a simple boolean gate
Try replacing the content cache with a context bake component, it will work exactly like a push but only execute at the end of the command. I faced a similar issue as you described (speed issues, the original object being lost if you exit the command, etc) and I solved it by using context bake. It works exactly like the content cache when you give it a model object with an existing GUID.
EDIT: I just noticed you are using Query Model Objects and not the Grasshopper Player’s ‘Get’ Components. I think that is what is causing the issue… If you used Get Geometry instead that it will work fine and bake all three spheres with the added caveat that you will have to manually select the boxes each time. This is strange. Even if its not a bug, this doesn’t feel like intended behavior.
Yeah I need to select all walls from a level therefore I use a Query Model Objects, but I did a trick using blocks and now seems works well, but not tested enough yet.
