FOV value isn't accurate from what I can tell

[radiance]

yeah, you need to correctly convert your host's camera transform to a lookat transform.

octane does'nt use a matrix transform for it's camera, but a lookat transform.
if you change the position, the camera will rotate as it's always looking towards the lookat point.

you need to transform the point, this then becomes the new point of the octane camera,
then you need to make a 2nd point that the camera points to.

i'll have to describe this in detail tomorrow as i'm exhausted.

Radiance

[face]

So, i have now match the camera from Softimage to Octane.
Thanks to radiance for help, but i have found, that i become the right up-vector from softimage self.
(the second row in the transformmatrix was the right up-vector und the third the direction. I have interchanged that)

The first image is a simple camera x/y rotation.
The second one use the x/y/z camera rotation.
And the last one uses x/y/z camera rotation and the FOV angle.

Sorry for the animated images, but i think so you can better see the result.
When you hit esc, than it don´t flash...

The current status for the plugin, you can pick the octane.exe, pick the camera, select the location of the rendered image and hit the render button.
Some values eg width, height, samples and exit after rendering are also implemented.
Future plans are to generate a simple ocs (working), use that to render (working), pick objects to render (working), use GPU (soon) and batch.
Some not implemented working features have little erros in the layout logic. Also read checkbox input than do that and not that...
Alltogether, it should not take long to finsh it.

[radiance]

So, i have now match the camera from Softimage to Octane.
Thanks to radiance for help, but i have found, that i become the right up-vector from softimage self.
(the second row in the transformmatrix was the right up-vector und the third the direction. I have interchanged that)

The first image is a simple camera x/y rotation.
The second one use the x/y/z camera rotation.
And the last one uses x/y/z camera rotation and the FOV angle.

Sorry for the animated images, but i think so you can better see the result.
When you hit esc, than it don´t flash...

The current status for the plugin, you can pick the octane.exe, pick the camera, select the location of the rendered image and hit the render button.
Some values eg width, height, samples and exit after rendering are also implemented.
Future plans are to generate a simple ocs (working), use that to render (working), pick objects to render (working), use GPU (soon) and batch.
Some not implemented working features have little erros in the layout logic. Also read checkbox input than do that and not that...
Alltogether, it should not take long to finsh it.

so the final RC2.1 has solved the issue where you reported that the camdera positon relative to the film is±25 pixels horizontally ?
i fixed it last thursday and it's added to beta 2.1

Radiance

[jipe]

yeah, you need to correctly convert your host's camera transform to a lookat transform.

octane does'nt use a matrix transform for it's camera, but a lookat transform.
if you change the position, the camera will rotate as it's always looking towards the lookat point.

Just curious, is this going to affect support for importing animated cameras in the future? I might be totally visualizing it wrong, but if I animate a camera in Maya without using the aim target, would it still be imported properly into Octane? Apologies if I'm totally misunderstanding your description of Octane's "lookat transform".

[face]

so the final RC2.1 has solved the issue where you reported that the camdera positon relative to the film is±25 pixels horizontally ?
i fixed it last thursday and it's added to beta 2.1

Sorry, i don´t reported that

Just curious, is this going to affect support for importing animated cameras in the future? I might be totally visualizing it wrong, but if I animate a camera in Maya without using the aim target, would it still be imported properly into Octane? Apologies if I'm totally misunderstanding your description of Octane's "lookat transform".

You don´t need that. But when you will render with the focus or DOF or rotate your scene in Octane, than would it be usefull. The target is the base to calculate that things...
When you have the POI from maya, then you can calculate the target. But without scripting or programming experience it is impossible...

[face]

Sorry, error. You need it. You don´t need it, when you can input the rotation angles or the direction in Octane. Than with limited effects (DOF, Motion blur...)