Render to mplay problem
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)
Yes its weird.
The problem persists in every scene.
The only way I can see to start a non-IPR render is through the "Controls"- Window of the Octane-ROP.
I did a screen capture of the log in a simple test scene with just a cube and an octane-shader.
It says that the Mplay driver interrupts octane. All the while the IPR continues to work fine.
The problem persists in every scene.
The only way I can see to start a non-IPR render is through the "Controls"- Window of the Octane-ROP.
I did a screen capture of the log in a simple test scene with just a cube and an octane-shader.
It says that the Mplay driver interrupts octane. All the while the IPR continues to work fine.
- Attachments
-
Sorry, I cant reproduce this problem here 
Can you please send to me the full log file? This problem must be something related to your system or houdini configuration, but I can't figure what could be issue.
So if you render with the ROP "Render to disk" button, the render fails, but with the "Render" button in the controls window the render works fine, right?
What happens if you render using the Houdini main top menu Render->Render->Octane_ROP1?
Do you get the same behavior with the MPlay window already opened before press the "Render to disk" button?
-Juanjo
Can you please send to me the full log file? This problem must be something related to your system or houdini configuration, but I can't figure what could be issue.
So if you render with the ROP "Render to disk" button, the render fails, but with the "Render" button in the controls window the render works fine, right?
What happens if you render using the Houdini main top menu Render->Render->Octane_ROP1?
Do you get the same behavior with the MPlay window already opened before press the "Render to disk" button?
-Juanjo
Thanks for responding and trying!
The log in my previous post shows what happened after pressing Render in the controls panel.
Basically IPR is the only way I could initialise a render with octane. Unlike the mantra-ROP the octane-ROP has no "render to mplay" button and
I haven`t tryed yet initiating a render through the options in menu< render etc.
Can`t check it for now, as IPR is in progress (DL @ 0,09 MS/sec). I will come back to you with further tests and logs towards the end of the week.
S
The log in my previous post shows what happened after pressing Render in the controls panel.
Basically IPR is the only way I could initialise a render with octane. Unlike the mantra-ROP the octane-ROP has no "render to mplay" button and
I haven`t tryed yet initiating a render through the options in menu< render etc.
Can`t check it for now, as IPR is in progress (DL @ 0,09 MS/sec). I will come back to you with further tests and logs towards the end of the week.
S
So I tryed to initiate the rendering through the main menu, which didn`t make any difference.
After the log says "set render targer (target?) node" I can see the RAM usage rise and fall like it does before IPR but instead of rendering it stops then.
Which of course is annoying as i`d like to render both higher resolutions than IPR allows and imagesequences.
Btw. does IPR limit the ray depth?
hoping for help
Stefan
After the log says "set render targer (target?) node" I can see the RAM usage rise and fall like it does before IPR but instead of rendering it stops then.
Which of course is annoying as i`d like to render both higher resolutions than IPR allows and imagesequences.
Btw. does IPR limit the ray depth?
hoping for help
Stefan
- Attachments
-
- log_octaneROP_renderToDisk.txt
- (18.92 KiB) Downloaded 267 times
-
- log_Render_PreviewInMplay_octaneROP.txt
- (18.76 KiB) Downloaded 235 times
-
- log_Render_octaneROP.txt
- (18.92 KiB) Downloaded 287 times
Yes, it seems always the same problem, but it is something that I can't reproduce in any of my computers. Thanks for the logs, I will make more tests to try to reproduce this problem, or find a workaround.
Do you have any kind of custom configuration in MPlay? Perhaps you could install a clean Houdini version and try again to know if there is something in your configuration that could be related to this problem.
Anyway you should be able to render to disk stills or sequences if you disable the "Render to MPlay" option in the ROP node and you enable the output image files ... the only problem is that you can't preview the render in the MPlay window.
-Juanjo
Do you have any kind of custom configuration in MPlay? Perhaps you could install a clean Houdini version and try again to know if there is something in your configuration that could be related to this problem.
Anyway you should be able to render to disk stills or sequences if you disable the "Render to MPlay" option in the ROP node and you enable the output image files ... the only problem is that you can't preview the render in the MPlay window.
-Juanjo