Page 5 of 18

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Sat Nov 08, 2014 8:09 am
by Builtdown
I think I solved this :
I tried to save to a folder with european letter in it. Saving was not succesful.
Then I saved to an another folder with no european letters and it saved normally.

It´s weird that when the image is rendered to completion, it saves normally to a folder with european letters but when trying to save in the middle of rendering, it does not.
Any chance to fix this?


- Builtdown

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Fri Nov 14, 2014 4:55 pm
by BorisGoreta
When I press play IPR does not update animation, when scrubbing it updates fine, I am talking about fast rendering scenes which render realtime, something like Brigade.

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Fri Nov 14, 2014 7:31 pm
by tyrot
Juan just thank you for new beta - It is awesome..

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Sun Nov 16, 2014 2:13 pm
by atnreg
Juanjo, I have two problems:
-when using HDRLS button with HDR Light Studio everything looks exact in IPR. And when I render the env image in HDR Light Studio and use it in Octane environment, the IPR looks the same (except for huge resolution improvement of course). Then when I do F9 render, the LW preview during the render looks the same but when the actual rendered image appears in LW image viewer, it is notably darker :O I have all CS settings in LW as Linear. And without env. image that does not happen, the preview looks exactly the same as the final rendered image. Any idea why this happens? :)
-this is old problem but it is so serious that I now make the max. samples to use way over needed and then always do Abort+Cont because if I let the render go to the end, LW gets in not responding state often (the 99% problem), not always but too often.

Other than these I have no problems with Octane :)

Antti

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Sun Nov 16, 2014 5:44 pm
by juanjgon
atnreg wrote:Juanjo, I have two problems:
-when using HDRLS button with HDR Light Studio everything looks exact in IPR. And when I render the env image in HDR Light Studio and use it in Octane environment, the IPR looks the same (except for huge resolution improvement of course). Then when I do F9 render, the LW preview during the render looks the same but when the actual rendered image appears in LW image viewer, it is notably darker :O I have all CS settings in LW as Linear. And without env. image that does not happen, the preview looks exactly the same as the final rendered image. Any idea why this happens? :)
-this is old problem but it is so serious that I now make the max. samples to use way over needed and then always do Abort+Cont because if I let the render go to the end, LW gets in not responding state often (the 99% problem), not always but too often.

Other than these I have no problems with Octane :)

Antti
If all the LW color settings are disabled, perhaps the problem is that you have the "Get Full linear HDR image" option enbled in the render target. Check it.

I have tested several times your 99% problem here without luck, but I will try some things again tomorrow. Are you working with the last daily build?

-Juanjo

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Mon Nov 17, 2014 4:04 am
by BorisGoreta
Are procedural texture nodes supposed to move the texture with deformable objects ? Now I can't see this behaviour.

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Mon Nov 17, 2014 8:06 am
by atnreg
juanjgon wrote: If all the LW color settings are disabled, perhaps the problem is that you have the "Get Full linear HDR image" option enbled in the render target. Check it.
YES! That was it, thanks! :mrgreen:
The manual only says "Enable to get the full HDRI no clipped and no tone mapped Octane frame buffer.". That I understand but what does it mean in practice? When should I use that feature?
juanjgon wrote: I have tested several times your 99% problem here without luck, but I will try some things again tomorrow. Are you working with the last daily build?
-Juanjo
Yes I know this is hard to fix if it does not happen for you, therefore thank you very much for still working on it :). I am using 2.12.1 - 28/Oct/2014.
Earlier I thought it had something to do with my particular scene but now I started new scene completely from scratch (of course used same Octane settings and Render Target settings) but the result was the same - if I let it try to finish the render, the result is mostly LW not responding at 99% when the remaining time is 1 or few seconds.

I always use PMC Kernel for max reality but could it be that some setting I have can cause this? Just in case, I attached my current RenderTarget (had to rar it, .dat is not allowed here), it uses env map but as the problem occurred earlier without one, I didn't include the image (it's big). I hope that will help you solving the problem :)
In case you wonder, there are couple of nodes not connected as I might need them some time and they keep the settings even if not connected so that way I have options for easy access.

And of course if there is anything strange in any of my settings that can cause problems and/or render quality issues or are just 'wrong' in your opininion, please let me know, I have tweaked the settings quite a bit to get fast but clean renders :)

Thank you very much again!

Antti

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Mon Nov 17, 2014 9:20 am
by juanjgon
BorisGoreta wrote:Are procedural texture nodes supposed to move the texture with deformable objects ? Now I can't see this behaviour.
As far I know Octane procedurals currently are working in object space only at transformations level (translations, rotations and so on), but they don't support mesh deformations. You need to use conventional UV maps to fix the textures to the mesh deformations.

-Juanjo

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Mon Nov 17, 2014 9:23 am
by juanjgon
atnreg wrote: The manual only says "Enable to get the full HDRI no clipped and no tone mapped Octane frame buffer.". That I understand but what does it mean in practice? When should I use that feature?
With this option enabled you get the full linear, not tone mapped, HDR image. This linear image can be useful to be used in post if you want to apply your own tone mapper, gamma or color corrections and so on.

-Juanjo

Re: OctaneRender™ 2.1 for LightWave™ - Daily builds

Posted: Mon Nov 17, 2014 10:54 am
by atnreg
juanjgon wrote:
atnreg wrote: The manual only says "Enable to get the full HDRI no clipped and no tone mapped Octane frame buffer.". That I understand but what does it mean in practice? When should I use that feature?
With this option enabled you get the full linear, not tone mapped, HDR image. This linear image can be useful to be used in post if you want to apply your own tone mapper, gamma or color corrections and so on.

-Juanjo
Ok, then I'll keep it off at least for now, I don't do post processing :)
Good luck with finding the 99% problem with my RenderTarget :)

Antti