Octane 3ds max to Standalone Dreams
Posted: Mon Jan 27, 2014 1:47 pm
Hi Octane team
This is what I am dreaming about:
- I set up a scene in 3ds max with the integrated plugin as I am doing it already. I will use Octane materials, name them correctly etc., do some test renderings eventually, setting up lights of course, animating a camera path. I use instances set as movable proxies. I also want to use forest pro.
- When I am nearly finished I hit an export button and save an Octane standalone scene. The instance information has not been destroyed by the export process. All material nodes would be properly set up.
- I can now work with the standalone GUI refining materials, setting up new camera nodes etc.
- I can go back to 3ds max, adding more geometry/materials and then export to another file.
- Back to my Standalone Octane scene I can merge the altered scene and choose what to replace (geometry only for example), newly created materials will be added if not present already.
Don't get me wrong, this is maybe not the intention of the integrated version and of course I am quite happy with what we have right now.
We used a quite similar workflow using Arion a while ago. It was a bit of a hassle to save the altered materials from the standalone out to a file and then load it into 3dsmax, but it worked.
The good thing was: We were able to let the standalone doing their job (for example a final rendering) while working on another scene/project in 3ds max.
Like said, this is just a dream, I am just interested if other users would also vote for such functionality.
As I understand the current development on the standalone is all about this alembic format but as I understand there is no definition which acts like instances in 3ds max, or am I wrong?
cheers
boris
This is what I am dreaming about:
- I set up a scene in 3ds max with the integrated plugin as I am doing it already. I will use Octane materials, name them correctly etc., do some test renderings eventually, setting up lights of course, animating a camera path. I use instances set as movable proxies. I also want to use forest pro.
- When I am nearly finished I hit an export button and save an Octane standalone scene. The instance information has not been destroyed by the export process. All material nodes would be properly set up.
- I can now work with the standalone GUI refining materials, setting up new camera nodes etc.
- I can go back to 3ds max, adding more geometry/materials and then export to another file.
- Back to my Standalone Octane scene I can merge the altered scene and choose what to replace (geometry only for example), newly created materials will be added if not present already.
Don't get me wrong, this is maybe not the intention of the integrated version and of course I am quite happy with what we have right now.
We used a quite similar workflow using Arion a while ago. It was a bit of a hassle to save the altered materials from the standalone out to a file and then load it into 3dsmax, but it worked.
The good thing was: We were able to let the standalone doing their job (for example a final rendering) while working on another scene/project in 3ds max.
Like said, this is just a dream, I am just interested if other users would also vote for such functionality.
As I understand the current development on the standalone is all about this alembic format but as I understand there is no definition which acts like instances in 3ds max, or am I wrong?
cheers
boris