Will Soft2Octane be compatible with Octane 2.0? Tweet

[manalokos]

Will Soft2Octane be compatible with Octane 2.0?
It is very important!

Kind regards
Filipe

[face]

There should be nothing changed with the command line.
So it should work, at least with normal geometry.
But i don´t know how hairs can be saved within the obj file format...

face

[adrencg]

When Octane 2.0 comes out, will the Octane4Softimage plugin be updated also? I'm a little confused about the difference between the export plugin and the actual Octane that works inside of XSI. As it stands now, which version Octane is being used when inside XSi?

[face]

When Octane 2.0 comes out, will the Octane4Softimage plugin be updated also?

Short answer, yes.
But i don´t know something about the pricing/update process.
We will see how Otoy will handle this...

I'm a little confused about the difference between the export plugin and the actual Octane that works inside of XSI.

The exporter is only a program which exports all geometry to an obj file and fire a commandline to the Octane standalone with some parameters. Then you can create your scene inside Octane and render it. So the exporter should work with all versions of Octane so long the commandline parameters are the same.

The internal on the other hand, must be compiled with every new version of the SDK which comes out.
This not means to only compile it with the new SDK, sometimes new functions must be implemented or at least, the complete shader generation must rewritten because there are massive changes in the SDK.
It is also massive integrated into Softimage.
I must check what is changed when the renderer is refreshed. If the mesh is changed, i delete the old one and transfer the new to the render engine.
The same is with the materials, cameras, environment shaders, output shaders or render options.
This checks aren´t simple because the Softimage ones aren´t so good as they should. So i have to write self a checking system.
When you animate, as example, the U value of a sphere between frame 10 to 20. For Softimage, this mesh is changed over the whole scene, also at frame 5 or frame 3000.
I would also send this mesh at every frame to the render engine. This make no sense.

There are also some differences between the standalone and the internal version.
And this is also the background, why ICE isn´t supported for now. First i want to make the internal version stable, then i will implement new features.
It can also take more time to hold the plugin up to date, as the time to integrate new features.

As it stands now, which version Octane is being used when inside XSi?

For now, the internal is working with the 1.20 and the exporter should work with the last one.


I hope this will answer your questions...
face

[Alul]

Any news about Octane2 for OctaneRender?