OTOY Forums

Thanks Paul, I updated the sample scene sorry there was a problem with the last one as well.

With your screenshot and testing please ignore the openGL viewport as this is glitchy with camera projection. Instead compare the Modo preview render with the Octane viewport ie:



The octane viewport on the right has a -2mm camera offset.

Is it possible to add this to the next plugin release, really much needed for ArchViz renders.

Cheers,
Dino.

Hi Paul I'm having trouble with 'Border Mode' in Texture Images in the node editor. When I first load the scene it will default to 'wrap around'. Once I select 'clamp' in the floatimage texture node, it appears as it should. Any update to the Octane IPR will revert it back to 'wrap around'.





Sample scene attached.

Cheers,
Dino.

Hi Dino

Hi Paul I'm having trouble with 'Border Mode' in Texture Images in the node editor. When I first load the scene it will default to 'wrap around'. Once I select 'clamp' in the floatimage texture node, it appears as it should. Any update to the Octane IPR will revert it back to 'wrap around'.

The Border Mode is being set from the Texture Locator Horizontal and Vertical Repeat. In theory, the Octane Image Border Mode combobox should be ignored in this instance, however the "listener" is picking up that it's being changed, so I will fix this so these changes do not get through to the Octane scene.

Paul

Thanks Paul, so the Octane Image Border Mode only works with octane projection nodes. Rather than disable the Texture locater horizontal and vertical repeat modes would it be difficult to make that connection to the Octane Image Border mode?

Also did you see my last post about camera projection mapping?

Cheers,
Dino.

Thanks Paul, so the Octane Image Border Mode only works with octane projection nodes. Rather than disable the Texture locater horizontal and vertical repeat modes would it be difficult to make that connection to the Octane Image Border mode?

I agree this is a confusing implementation. It would be better if the Texture Locator also plugged into the Border Mode pin, so it was more obvious what was driving the Border Mode value in Octane. I will investigate this further.

Also did you see my last post about camera projection mapping?

Thanks to some analysis work by Funk, the next release of the plugin will apply the Modo Camera Film Offset to Front Projections.

Paul

Awesome, and awesome.. Look forward to the next release.

So looking forward to proper Modo Camera Film Offset to Front Projection support.

I've just prepped 4 complex scenes with 5 different cameras per scene and in the 11h learned that the projections don't currently follow the Modo Camera Film Offset. Basically I have to ditch Octane completely at this point and rebuild my shaders in MODO renderer.

Any news when this next version will be out? possible to push out a patch with just this feature to save me?

Any news when this next version will be out? possible to push out a patch with just this feature to save me?

I will post a WIP 3.08 build of the plugin in the next 24hrs, which should resolve your issue.

Paul

face_off wrote:I will post a WIP 3.08 build of the plugin in the next 24hrs, which should resolve your issue.
Paul

Awesome that will be a huge help. Really looking forward to that.

I noticed a second, different issue with projections. If I project an image with say Camera B and then render the scene with Camera A, camera projections currently only seem to respect the render camera. That means that the projected image will use Camera A instead of Camera B. In MODO internal this sort of thing works fine. Wondering if it would be possible to have in Octane. Not as big of an issue as the Film offset problem.

thanks

I will post a WIP 3.08 build of the plugin in the next 24hrs, which should resolve your issue.

I am really sorry - but I have found some issues with the modo plugin and Octane 3.08 TEST 4 which are shop-stoppers, so I won't me able to release a test version today.

I noticed a second, different issue with projections. If I project an image with say Camera B and then render the scene with Camera A, camera projections currently only seem to respect the render camera. That means that the projected image will use Camera A instead of Camera B. In MODO internal this sort of thing works fine.

This may be possible. I will investigate.

Paul