OctaneRender™ 3.0 for LightWave™ - Test build 3.08.0.9 RC3

[BorisGoreta]

This could be the case.

Any news on making IPR react in object changes from modeler or new object loading while it is rendering ?

Changes to parallel samples, max tile samples and minimize net traffic in path tracing are not invoking IPR render reset.

I'm not sure, but I think that these parameters are changed on the fly without initializing the rendering. Standalone has the same behavior.

Thanks,
-Juanjo

[juanjgon]

This could be the case.

Any news on making IPR react in object changes from modeler or new object loading while it is rendering ?

Not yet, sorry. I'll work on this LW2018 limitation (and the fiberfx materials updating) for the next build.

Thanks,
-Juanjo

[BorisGoreta]

Ok, if we can help by sending bug reports to LW let us know. They seem to be listening much better now.

[sauloarruda]

Thanks Juanjo!

[FrankPooleFloating]

Juanjo pal, is there a reason why default refraction index went from 1.0 to 1.3 on glossy mats?.. 1.0 seems to make more sense, and I often use 1.0, unless doing exotic materials... Or am I missing something, with the new stuff of late? I haven't dived too deep into new features, and have barely touched new metal mat, etc... In other words, what is special about 1.3?

[juanjgon]

This is the default value for the index of refraction in Standalone, and usually, all the plugin should match the defaults available in Standalone, that are also the parameters default values provided by the Octane SDK.

Thanks,
-Juanjo

[FrankPooleFloating]

Hmmm.. okay. Thanks buddy.

[BorisGoreta]

I've just stop watched the scene I am working on and it takes 4 minutes from the moment I hit render until it actually starts rendering. I heard that this part is accelerated up to 30 times in Octane 4. Has someone tested this in standalone and could confirm it ?

[BorisGoreta]

Often IPR is not reacting at all to changes I make in node graph. For instance, I disable some input to some node, nothing happens, so I have to connect it and disconnect it again for IPR to "pick it up". This also happens when changing values in some of the nodes, I need to scrub the value twice or I need to enter a value and hit enter twice. I would say this happens 1 in 20 times when interacting with nodes, it is not reproducible but it is always present.

[juanjgon]

Often IPR is not reacting at all to changes I make in node graph. For instance, I disable some input to some node, nothing happens, so I have to connect it and disconnect it again for IPR to "pick it up". This also happens when changing values in some of the nodes, I need to scrub the value twice or I need to enter a value and hit enter twice. I would say this happens 1 in 20 times when interacting with nodes, it is not reproducible but it is always present.

In LightWave 2018, or can you see the same problem in LW2015?

Thanks,
-Juanjo