OTOY Forums

face_off wrote:

Thanks Paul, yes this is how I'm managing at the moment and I'ts an ok workaround. If I have an existing scene, an interior scene for example, I can import this scene into my new scene and reuse all the furniture elements but also a whole lot of redundant items are also imported such as node chains, groups, materials (oddly sometimes even those not attached to the imported items), images and image groups etc. and the scene gets convoluted pretty quickly. Basically I have to go through and cull the pre-existing scene as best as I can to minimise the unwanted imported elements as much as possible, and If I make a mess of this cull process (delete elements only to find out many steps later I shouldn't have) I sometimes find myself having to revert the scene and start over. Would be so much easier to just have both scenes open at the same time and be able to drag objects across as needed, as we're used to doing pre octane.

Is there maybe some way you can collaborate with the modo dev team to make this possible? I realise each platform and associated plugin has their strengths and weaknesses but this would be a huge win for Octane for Modo.

I understand. It's definitely something I would like to get working better in the plugin, but need to get all the Octane 3 features in first. I will speak to TheFoundry about it.

Paul

ERROR: Detected octane.dll version does not match the plugin version.

When I duplicate one camera with octane viewport opened, Modo crashs.

MrFurious wrote:if I change certain imager attributes such as exposure, gamma, highlight comp, vignetting, actually pretty much all the flags in the imager.. the octane render restarts.