OctaneRender 4 for Modo [OBSOLETE]

[MrFurious]

Hi Paul there's a problem with the resolution override in the latest version 4 plugin... keying these values in the timeline doesn't work. Octane uses the resolution override values for only the first keyframe and ignores subsequent keyed resolution values.

Cheers,
Dino.

[MrFurious]

One other issue I found.

I have the modo camera Focus distance driven by the Octane focal depth. In the latest version 4 build this causes the Octane IPR to restart when any changes are made to the Octane Camera (all tabs; camera, stereo, imager, post process). Did not have this issue with any previous builds. Happy to upload a scene if needed.

Cheers,
Dino.

[face_off]

Hi Paul there's a problem with the resolution override in the latest version 4 plugin... keying these values in the timeline doesn't work. Octane uses the resolution override values for only the first keyframe and ignores subsequent keyed resolution values.

I think this has always been the case.

I have the modo camera Focus distance driven by the Octane focal depth. In the latest version 4 build this causes the Octane IPR to restart when any changes are made to the Octane Camera (all tabs; camera, stereo, imager, post process). Did not have this issue with any previous builds. Happy to upload a scene if needed.

Can you upload the scene please Dino?

Thanks

Paul

[MrFurious]

Thanks Paul, please find attached...

As soon as you open the scene you can change the exposure in the imager and notice it reloads IPR each time. Actually any parameter change in the octane camera (camera, stereo, imager, post process) will cause IPR to reload. In the schematic view there'a workspace called 'Focus distance'. If you disconnect the cameras focal distance node, IPR behavior returns to normal:

dof node.jpg (10.31 KiB) Viewed 4480 times

mech.zip

(3.88 MiB) Downloaded 245 times

[MrFurious]

Hi Paul there's a problem with the resolution override in the latest version 4 plugin... keying these values in the timeline doesn't work. Octane uses the resolution override values for only the first keyframe and ignores subsequent keyed resolution values.

I think this has always been the case.

Could well have been.. I think this is the first time I've done this in a modo/octane scene. I tested this in the previous stable build [4.02] with the same result. Would be immensely useful if this could be implemented. For Archviz it's quite common to use keyframes not for animation, but to have alternate camera options for a scene.

Cheers,
Dino.

[face_off]

I have updated the stable installers at the top of this thread with:

4.04.0.144
- Fixed performance issue there "Refreshing Materials" was taking too long when updating a Modo material
- Fixed bug where "Add Nodegraph" could not be enabled
- Fixed bug where Modo would crash if you deleted a group locator whilst rendering in Octane
- Slight improvement to the speed with which geometry is loaded into Octane when the "Refreshing Octane Geometry" dialog is shown

Thanks

Paul

[MrFurious]

Thanks Paul glad the 'refresh materials' bug is fixed. Have you had a chance to look at my scene?

[face_off]

As soon as you open the scene you can change the exposure in the imager and notice it reloads IPR each time. Actually any parameter change in the octane camera (camera, stereo, imager, post process) will cause IPR to reload. In the schematic view there'a workspace called 'Focus distance'. If you disconnect the cameras focal distance node, IPR behavior returns to normal:

This is fixed in the next release.

Thanks

Paul

[MrFurious]

Nice.. looking forward to that. Keyable camera resolution would be nice too

[MrFurious]

An issue I found with the latest V4 build. Changing the cameras White Point does not update in IPR.

edit: same for sky color, sunset color, ground color, stereo left filter and right filter.