I know you've said it's not an insignificant feature to implement, but I feel as strong as ever that it could push the Revit plugin to a new level.
Agreed
I would love to implement this - however it needs Otoy to provide access to the LocalDb in the API. I've already put in two feature requests for this - but the more people that request it the more likely Otoy will push it up the priority list - so pls submit this request to Otoy.
I have placed this request within the general plugin support page. Hopefully this creates a bit more awareness.
On another topic Paul. When exporting a scene to an ocs file and opening it in the octane standalone, the complexity of the node system created is so great that my octane responds so slow to the point that it is unusable. After separating one of the paths (a tree) and seeing how it has been structured, it seems that is overly complicated in the amount of nodes needed to create the same result. (see attached images, I have made the obj model red for clarity)
- NORMAL EXPORTED OCS
. This tree is one that was being proxied within the revit plugin. Would it be possible to eliminate the excessive transformation and placement nodes during the creating of the ocs? and also the scatter node. As it seems redundant aswell. This proxy wasn't being scattered. And finally, this tree was used multiple times within the project at different scales and rotations, (that I manually entered when assigning the proxy). Rather than have duplicate obj nodes created and then each having their own separate placement node. Can each of the placement nodes simply be connected to the one obj. This would speed up the interface dramatically, and make replacing or editing in the standalone actually possible.
Regards,
Chris.