Page 2 of 3
Re: Render to mplay problem
Posted: Wed Feb 03, 2016 5:02 pm
by Stassius
Sorry, i checked it. Houdini crashes when i change uv-scale on a displacement map.
Re: Render to mplay problem
Posted: Wed Feb 03, 2016 5:13 pm
by juanjgon
Thanks for reporting. Yes, I can reproduce this problem here. It seems a bug in Octane, because I can reproduce it also in the Standalone.
I will report it to the Octane team.
Thanks,
-Juanjo
Re: Render to mplay problem
Posted: Thu Feb 04, 2016 8:22 pm
by Stefan
Hi, this might not be a bug.
But I can`t get octane to render to mplay or to disk.
Only IPR is working so far. Am I missing sth.?
I use the latest alpha plugin.
Re: Render to mplay problem
Posted: Thu Feb 04, 2016 9:28 pm
by juanjgon
Weird issue, can you send me a sample scene with this problem?
-Juanjo
Re: Render to mplay problem
Posted: Sun Feb 07, 2016 8:30 pm
by Stefan
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.
Re: Render to mplay problem
Posted: Mon Feb 08, 2016 10:28 am
by juanjgon
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
Re: Render to mplay problem
Posted: Mon Feb 08, 2016 7:03 pm
by Stefan
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
Re: Render to mplay problem
Posted: Thu Feb 11, 2016 7:16 pm
by Stefan
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
Re: Render to mplay problem
Posted: Thu Feb 11, 2016 9:39 pm
by juanjgon
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
Re: Render to mplay problem
Posted: Thu Feb 11, 2016 9:49 pm
by juanjgon
Other question, are you working with Windows 7/8 or in Windows 10?
-Juanjo