Yes, thank you. Fixed now.I think you made a copy/past error from the other thread here. It should say 3.0.6.99, right?
Paul
Moderator: face_off
Yes, thank you. Fixed now.I think you made a copy/past error from the other thread here. It should say 3.0.6.99, right?
The next release will allow you to export an Octane Override as ORBX - so you could save then reload from the Octane LocalDb.Right now, what is the best way to store materials in a bank or sharing between projects!
Render Region is working in the next release.give to us one version with render region please.
This is complex to implement in the Modo plugin - since from my initial testing, vertex motion vectors where not working in the Modo API. However it is possible this has been fixed, so I need to retest it to see if it is now possible. So at the moment, the octane.saveAnimation command is the best way to render with vertex motion blur (ie. render the resulting ORBX/OCS in Octane Standalone).is it possible to render mesh motion blur on the plugin with the new release. I am asking this because it is hard or imposible to export/freeze dynamic replicator to the standalone for rendering.
At the moment OBJECT motion blur from animated replicators is not supported in the plugin (again - you need to octane.saveAnimation to render motion blur in this situation). However this is something I could implement in the plugin. If you have a sample scene which demonstrates motion blur in this situation, pls send it to me and I will see what can be done.is it true that dynamics replicators and replicators animation does not have any motion blur effect when exported to octane stand alone ?. I exported a simulation, all is ok except the fact motion blur is not exported like these items are different items for each frame, and not moving ones.