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
Frames being Overwritten
Moderator: juanjgon
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
-
ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
Hi EyasArraf,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
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.
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.
-
ricky_otoy
- Posts: 289
- Joined: Mon Jun 19, 2023 6:34 am
We are still looking into this, I will get back to you on it. Again sorry for the inconvenience!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.