OTOY Forums

When using a hou.frame() Python expression instead of the Hscript '$F' in the 'image file path' parameter, the python expression is evaluated as 1 for all frames and results in frames being overwritten on one another.
This problem does not occur in other ROP nodes like Mantra or Karma.

* Currently using:
Windows 11
Houdini 20.0.590
Octane 2024.1.2.0

EyasArraf wrote:When using a hou.frame() Python expression instead of the Hscript '$F' in the 'image file path' parameter, the python expression is evaluated as 1 for all frames and results in frames being overwritten on one another.
This problem does not occur in other ROP nodes like Mantra or Karma.

* Currently using:
Windows 11
Houdini 20.0.590
Octane 2024.1.2.0

Hi EyasArraf,

you mention $F not $FF, I think the equivalent is hou.intFrame() - does that give the same issue for you?

Actually hou.intFrame() equals = int(hou.frame()) and I tried both. Still the same problem. Both python expressions evaluate as "1" to every frame in the animation. Only happens in OctaneROP.
The reason I use Python instead of Hscript in this OctaneROP is that python is much more versatile and powerful when automating exporting frames.
I actually don't know if I'm the only one having this problem or what but I hope it gets fixed.
Thanks for your efforts.

EyasArraf wrote:Actually hou.intFrame() equals = int(hou.frame()) and I tried both. Still the same problem. Both python expressions evaluate as "1" to every frame in the animation. Only happens in OctaneROP.
The reason I use Python instead of Hscript in this OctaneROP is that python is much more versatile and powerful when automating exporting frames.
I actually don't know if I'm the only one having this problem or what but I hope it gets fixed.
Thanks for your efforts.

We are still looking into this, I will get back to you on it. Again sorry for the inconvenience!

I just downloaded Octane 2023.1.3.0 version. Thanks for fixing the issue. Appreciate it.