Page 2 of 3

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Tue Apr 28, 2020 1:44 pm
by juanjgon
liamclisham wrote:I've tried installing as I normally do a few times and keep getting this error: https://i.imgur.com/gILNvKn.png. It was fine on the previous 2020.1.0.6 build.


This seems an installation issue. Can you please attach your houdini.env file?

Thanks,
-Juanjo

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Tue Apr 28, 2020 8:47 pm
by pingovanderb
The Hydra plugin is another project not directly related to this main plugin. It is still in development, but it will be available shortly.

Thanks,
-Juanjo


-Juanjo you guys can not keep saying this, and meanwhile send us emails announcing it's implemented (srsly!) You're shooting this ball back and forth between departments. It's so frustrating to spend time constantly updating only to find out you still didn't do what you promised. Again! I think Octane for Houdini is great and you're making a lot of progress, but the Hydra delegate is SUPER important in regards to using Octane as a production render. Lastly it is bordering false advertising.

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Thu Apr 30, 2020 5:37 pm
by labmeta
Does this build have the indie 4k resolution restriction removed?

Thanks,

P

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Thu Apr 30, 2020 6:57 pm
by juanjgon
labmeta wrote:Does this build have the indie 4k resolution restriction removed?

Thanks,

P


Not yet. The next one will have it. We'll release it ASAP.

Thanks,
-Juanjo

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Thu May 07, 2020 5:22 pm
by matpr
Hey, can anyone point me to how to get rid of the following error?
Whenever I create a Render Target it gives me the warning about skipping those parameters.

Thank you!

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Thu May 07, 2020 6:31 pm
by juanjgon
matpr wrote:Hey, can anyone point me to how to get rid of the following error?
Whenever I create a Render Target it gives me the warning about skipping those parameters.

Thank you!


Yes, sorry. There is a problem with the RT HDA, that had not been updated to remove these deprecated parameters. I'll update it for the next build, but meanwhile, it is safe to ignore them.

Thanks,
-Juanjo

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Sat May 09, 2020 11:07 am
by obbiem
I'm using camera crop to render part of the image (to save the render time on the specific shot) and in this version, stops render at 60 samples (60/1000). It was fine in 2019.

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Sat May 09, 2020 5:44 pm
by juanjgon
obbiem wrote:I'm using camera crop to render part of the image (to save the render time on the specific shot) and in this version, stops render at 60 samples (60/1000). It was fine in 2019.

Have you checked the render time or quality between 2019 and 2020? I ask because I wonder if the problem could come from how Octane computes the samples while working with the render region enabled, reporting the number of samples / render crop surface.

If you think that the crop rendering has indeed only 60 samples (I mean, more noise, less render quality, very small render time ...) I'll take a look at what could be the problem.

Thanks,
-Juanjo

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Tue May 12, 2020 1:39 pm
by obbiem
Hi Juanjo,

I've checked the render quality looks like 60 samples when I use crop only along only one axis more than half the screen (0.5) render is going fine and I'll get full 2000/2000 samples...
( I've known you are referring to render region in IPR view which is a completely different story in terms of how Octane showing samples)

Thank you,
Obrad

Re: OctaneRender 2020.1 for Houdini Production build 2020.1.0.7

PostPosted: Tue May 12, 2020 2:07 pm
by Antoncromas
2020 release seems to be a bit halfassed across the board, c4d has HDRI BG rendering black, denoiser issues among other things and I see houdini release has a lot of issues and features missing as well. . . Honestly its better not to release at all and just keep it as an RC for longer.