OTOY Forums

1.) Local DB feature is long overdue. You have all the widgets & functionality already coded for the Live DB, you just need to adapt it to look for .ocms into some folder on the local HDD. Local DB could be a huge time-saver for users.

2.) Another useful thing is the ability to open some .ocs scene graph in the outliner & drag&drop stuff (nodes) from it in the active project. This way the user doesnt need to first open the other .ocs, then export the needed nodes into .ocm files, then re-open the working .ocs and re-import the .ocms there...

User time spent on working with the program is more precious (=expensive) than render time. So, features that speed up our work with Octane are at least as important as engine optimizations. Show 'em some love

1) is on the TODO list.

For 2) you don't need to export stuff to OCM files, but you can open the other scene in another Octane instance and copy/paste across the two scenes.

--
Roeland

For 2.) opening an other Octane instance is a better solution than exporting to .ocm, but you still have to go through the unnecessary "loading textures / voxelizing" process (which means you have now two possibly big scenes in RAM). For the purpose of copying nodes you just need the xml description, which could be shown in the outliner the same way as the structure of the current .ocs is.

But, ok, this is not a super important thing, just something that could be useful in certain cases (when you are making a new / different version of some project, or you want to re-use lots of settings from another .ocs). The more important thing is that Local DB is on the TODO list...