Hi,
Does anyone know if there is a limitation within the C4D Octane plugin when using an image sequence for projection mapping?
For instance, is there a maximum frame count that it can hold?
The viewport for both C4D and the Octane renderer work fine when projecting single frames as a texture via the Emission node.
You can then have the plugin / texture tab determine the frame rate and range by pressing 'Calculate' within the Animation tab.
However, once it starts rendering a sequence, the projection breaks both in the preview and the actual render.
It's as if it can't handle projecting a large sequence back onto geometry (approximately 200 frames).
If I stop the render, press 'Calculate' again, it works fine for a single frame and the projection fixes itself.
I'm wondering if I'm missing a step in my workflow or if I have to use another node for projecting image sequences?
Any help would be appreciated.
Thanks!
Camera mapping
Moderators: ChrisHekman, aoktar
Solved.
It was the aspect ratio that was mismatched from projection camera in the texture projection node.
And then a numerical value of -4 in the Z scale, which seems kind of random.
I only happened upon it by searching here on the forum for other camera mapping entries.
It was the aspect ratio that was mismatched from projection camera in the texture projection node.
And then a numerical value of -4 in the Z scale, which seems kind of random.
I only happened upon it by searching here on the forum for other camera mapping entries.