OctaneRender™ for LightWave™ 2.0 - build 2.0.10

[alexos]

Aha, thanks, J.
Another quick note - I'm just messing around with the new features: the rounding trick doesn't seem to work when you mix materials with the "material mixer" node. I have a glossy and a diffuse both set at 7% roundness but the result from material mixer is (apparently) zero. I didn't expect it to work, actually, cos it seems too bloody difficult, but just in the remote eventuality you weren't aware of this, there you go...

ADP.

[Escelce]

Thank you all so much for the hard work that's gone into this. So impressive. I was blown away by and have been using nothing but octane 1 since I found it and now its so much better. Worth the wait and the support on here by the team is fantastic.

-Steve

[Tommes]

Isn't the Network Rendering imnplemented yet?

I just have upgraded to 2.0.
Installed the plugin and enabled some GPUs over the "Network Options" button. But there are no GPUs in IPR neither in F9 render.

Yes, this could be a windows firewall problem in your main workstation. Sometimes I need to open the firewall advanced options panel and delete all the Lightwave/Layout outbound rules.

-Juanjo

Well, I don't know if that's the case. Deleted some Octane entries, but didn't helped at all. Btw. I have tested it before with the Standalone version and that worked like a charm.

Ok, disabling the Firewall helped. Now I have to check the entries ...

Edit: After manually adding some entries it worked.

But: Is there support for network rendering in IPR?

[vipvip]

just beginning to test some features and it is very promising ( displacment is just awesome ). As far as i used this new version, just 2 points i was doubting about:

. for transformation motionblur, blur lenght seems to be controled by the % in the lightwave camera props ( between 0 & 100%, no more apparently ) but the motion blur steps, inside octane rendertaget parameters, seems to be not effective ( if =0 -> no MB, and >= 1, full mb but the same, whatever the values so the step number apparently doesn't affect the blur smoothness ). Is there something wrong here ?

. about network rendering, 'render Q' works well for a list of scene to render but i encounter problems with LWSN command line: the process is launched normally but the output pictures are grey so it seems to be not working: is it a bug or is it planned to add it after because this function is VERY usefull...

anyway, congrats for your work, excellent as usual...

[juanjgon]

Edit: After manually adding some entries it worked.

But: Is there support for network rendering in IPR?

Yes, the IPR also supports the network rendering ... there is some information about the network state in the Layout information text line. Perhaps I should add also some kind of information about the network rendering to the main IPR window.

-Juanjo

[juanjgon]

just beginning to test some features and it is very promising ( displacment is just awesome ). As far as i used this new version, just 2 points i was doubting about:

. for transformation motionblur, blur lenght seems to be controled by the % in the lightwave camera props ( between 0 & 100%, no more apparently ) but the motion blur steps, inside octane rendertaget parameters, seems to be not effective ( if =0 -> no MB, and >= 1, full mb but the same, whatever the values so the step number apparently doesn't affect the blur smoothness ). Is there something wrong here ?

. about network rendering, 'render Q' works well for a list of scene to render but i encounter problems with LWSN command line: the process is launched normally but the output pictures are grey so it seems to be not working: is it a bug or is it planned to add it after because this function is VERY usefull...

anyway, congrats for your work, excellent as usual...

Yes, the motion blur lenght is controled by the camera blur lenght parameter. The motion blur steps are only useful to avoid artifacts in high speed rotating objects, but the default value should work fine.

How do you use LWSN from command line? ... if LWSN works with renderQ or with the LWSN Layout controler, perhaps there is some kind of problem with the command line parameters.

-Juanjo

[vipvip]

thanks for your answer

i've tried another test, and this time it works !
So i've to find why the 2 previous tests where not working.

i was wondering: perhaps the 'grey' rendered picture are the result of an over-exagerated DOF, defined by a wrong parameter of the camera target when rendering with command line LWSN: is it something like that possible ? ( a question of CFG environment file path perhaps...)

[juanjgon]

I think that LWSN can't change any kind of rendering parameter AFAIK.

-Juanjo

[vipvip]

ok thanks

[TheMightySpud]

Hi all,

Loving Octane 2.0 so far. juanjgon, you sir are a genius.

Trying to get my head around the network rendering side, which I think I have, but need an answer to a question.............

Is it possible to enter a new entry for 'Daemon Scan Subnet' (Basically changing the subnet which is being scanned)? Current the only entry is 192.168.0.0/24 and would like to be able to change this to something else. (The documentation for standalone shows a number of entries)

Also, and this is just a curiosity, what is the /24 part of that value? lol.

Thanks
TheMightySpud