Hops - R8 - Content Cache Support?

Hello,

Does hops support R8 Content Cache and/or data types? @AndyPayne @kike ?

Graph Space:

1. Object reference not set to an instance of an object.: component "Content Cache" (5908058c-6b6d-4114-ac2d-00c3a6821d4f)

Inside the “Floor Boundary Lines” hops component:

I’m wanting to split up a 9,000 component definition into respective hops functions for code management and performance reasons but if Content Cache isn’t supported I’ll need to wait until it is as my definitions rely heavily on this feature.

Alternatively, I attempted to pass the Model Curves (in this case) directly to the Context Bake output but that results in the component being stuck in the solving… state on a very simple definition if the Query Model Objects component is active inside of the hops function.

Then I simplified further by querying outside of the hops def in the main script but the Model Curves are passing empty to the context bake output as seen in this snip (though the data tree structure is correct):

image

And here’s what that hops function looks like:

Thanks for your responses and clarity you can bring!

1 Like

I’m away from my computer this week… but right now Model Objects won’t work with rhino.compute. We do have a solution for this but there’s a few internal things that I need to test before it’s released. As for the Content Cache… I haven’t tested that yet either but once the model objects are supported, we can try to look at the content cache. I’m not sure if it could even work because compute works in a headless environment where there is no document… so I’m not sure if it’s even possible… but will have to investigate.

1 Like

Thanks @AndyPayne, in testing further I would be perfectly happy with model object support only for now. I mean cache support would be great but at the very least being able to run complex functions in hops while keeping their meta data/attributes in tact and then simply cache or preview the output in a main script would still work well for most use cases i can think of.

Does the Model Object support you are working on extend to the Query and Filter components as well? Or would that be a separate undertaking like the Content Cache? I imagine Query and Filter also need an active document reference?

Thanks for your response and enjoy your time away!

Again, I haven’t tested the Query or Filter components specifically but more than likely they will not work unless we modify them in some way.

1 Like

Understood, thanks for clarifying!

I would also very much like to work this way - in the manner showed in your screenshots.
I am also going to be waiting for this functionality with content caching and querying model objects.