OTOY Forums

I see this being discussed here: viewtopic.php?f=34&t=75763&p=389650&hil ... nd#p389650 but I had a different method that I'm wondering why it doesn't work.

Attached is the modo scene and a screengrab of my setup.

What I have is workspace the gets the current frame and makes a string with the filepath for an image sequence. Then I have that value being fed into the "Background image Filename (Octane)" channel. There are a few questions & comments I have about this

1. If I load one of the images directly in the Octane kernel settings, it loads and I can see it. I have alpha enabled and I can confirm the file is loadable as a background, just not animated.
2. When I create this channel link, Octane doesn't complain. If I intentionally mess up the filename feeding the background image filename, Octane gives the "Error loading background image" alert. So it does seem like Octane is seeing a file to load and attempting to load it; however, the background is black.
3. The Background image Filename (Octane)" channel when I hover in the schematic editor says it's a gradient? I haven't found a gradient that this channel seems to accept. The only way I was actually able to link the string to that channel is by using the channel links editor and making a direct link. Again, it seems like Octane accepts this, but it doesn't want to make it easy.

I've tried clicking around in the kernel animation panel to load textures each frame or any related things but it doesn't seem lik it wants to load my image.

Any ideas on if this can work without some complex plane with a texture mapped to it transforming with the camera?

Hi

The Background Image is read from frame 0, so I don't think this approach will work.

Instead, use the latest Octane 2021.1 version, with a node setup similar to: Thanks

Paul

Oh cool. Will this work with Octane X PR8 Modo?

fform wrote:Oh cool. Will this work with Octane X PR8 Modo?

Octane X PR8 is based on Octane 2021.1.5, and doesn't support the features you need to use the above approach.

Paul

Ah, bummer. Any idea when this might be part of Octane Modo? I saw there was going to be a big change for octane X soon, is Modo going to be ready for that?

I've been looking around for a single page that just lists what versions of everything are based on and the dates. Does that exist?

fform wrote:Ah, bummer. Any idea when this might be part of Octane Modo? I saw there was going to be a big change for octane X soon, is Modo going to be ready for that?

I've been looking around for a single page that just lists what versions of everything are based on and the dates. Does that exist?

I suggest to ask OTOY for an update on Octane X. The Octane version that a particular Modo plugin support is in the version number (so plugin release 2020.1.5.164 is built with Octane 2020.1.5). Octane X uses a difference version numbering, but hopefully OTOY will align this with the normal Octane version numbering at some point in the future.

Thanks

Paul