This would be great. I am hoping that we will be able to access a local drive of material files the same way we acess LiveDB. That way we can create, store & access our own materials.
I thought I saw this announced somewhere but could not find it. So I think possibly it may have been a comment made by Jules Urbach in one of the future Octane presentations(?)
At the moment the Octane API supports loading and saving materials to OCS (and therefore maybe OCM), but I don't think any of the plugins yet implement it, because it is very new, and requires some shuffling of nodes within the scene. Also - I'm not sure you if the plugins will be able to access the Octane Standalone LocalDb - bit if so, that would be another way to share materials.
Apologies for bringing this up again (ahem) but the ability to import OCS files as proxies may help here since it should import the OCS materials... That's still no. 1 on my O4R feature wishlist.
Again, the latest version of the Octane API actually supports loading an OCS into the plugin Viewport (as a proxy), but as above, this is very new, and would require some re-structuring of the plugin to implement. So changes like this will need to be looked after all the Octane 2.0 goodies have been implemented.
Paul