Is it possible to store geo made in SOPs in an APEX graph?

I understand how to use geo as an input to an APEX graph that can be provided when it is invoked. I'm wondering if there is a way to store geo made with ordinary SOPs nodes in a Value<Geometry> type in an APEX graph. The geo there could then be manipulated by editing the graph down the line and when the graph is invoked at the end, the SOP geo would not need to be provided.

I have attached a .hip file with a simple box as an example. the first example is of a graph that simply outputs a default box when invoked with a box used as an input. the second example is a failing attempt to store the box in a graph and then invoke that graph with the stored box as output.

Maybe there is a node that would make what is stored in the Value<Geometry> node graph compatible? if you look in the geo spreadsheet there appears to be something stored in the parms of the Value<Geometry> node. It looks like some kind of encoded file.

Thanks for any advice,
Sky

Your example will work in the next major release because there were some gaps in H20.5's infrastructure that was missing for this. I'm of two minds about this workflow though. It still makes more sense (to me) to add it to the APEX Scene packed folders as its own separate "file" and will then get invoked when the rig is evaluated. Because then it's a lot more open.

edward
Your example will work in the next major release because there were some gaps in H20.5's infrastructure that was missing for this. I'm of two minds about this workflow though. It still makes more sense (to me) to add it to the APEX Scene packed folders as its own separate "file" and will then get invoked when the rig is evaluated. Because then it's a lot more open.

Thanks for your reply. That is great news!

I have been using APEX more experimentally with SOPS and not for rigging. I can see how it might be best as it is for rigging, as nothing is really being modified except for the rig. Why store the mesh, for instance, if it is not going to change via rig components, right?

I investigated how custom controller objects are added but it seemed pretty involved.

I'm interested in being able to store a mesh in the graph with tags and then later edit the graph via tags and change up the mesh.