OctaneRender™ for LightWave™ 2.0 DAILY BUILD

[juanjgon]

Juanjo,

i just did the test with the last build and unfortunately
it still crashes.
I've just sent you the test files, if you could take a look
Thanks a lot

Oliv

Thanks for the file. I can reproduce the crash here and I will fix it as soon as possible.

As workaround I think that if you add at least one small triangle to the points cloud object, the scene could work fine without crash Layout.

-Juanjo

[juanjgon]

Hi Juanjo,

when instancing an object with a points reference object
(for exemple a cloud of points created in modeler)
Octane does render with no problem but crashes as soon as i move
the reference object or if even if i just open the instance tab.
Do you have the same issue?
Thanks

Oliv

This bug is fixed for the next release. Thanks for report it.

-Juanjo

[CANDITO]

Thanks Juanjo
By the way, do you think the problem with
the color gamma of the lightwave 11.6 color picker
could be fixed too?
Thanks again for your great work!

Oliv

[MrFurious]

I'm having an issue with the latest daily build.. with region render when using F9. Rather than refine the given region, it will start re-rendering that section ie: goes grainy then starts to refine. Also, if the render region touches the border of either side, or top/bottom all sorts of weird things happen and rendering starts again but outside the render region selection.

[juanjgon]

I'm having an issue with the latest daily build.. with region render when using F9. Rather than refine the given region, it will start re-rendering that section ie: goes grainy then starts to refine. Also, if the render region touches the border of either side, or top/bottom all sorts of weird things happen and rendering starts again but outside the render region selection.

I am testing the region render here and all works fine. Can you please test it again with other scene? ... if you have a scene with the problem, please send it to me to test it here.

Other question, are you using the network rendering?

-Juanjo

[MrFurious]

I'm having an issue with the latest daily build.. with region render when using F9. Rather than refine the given region, it will start re-rendering that section ie: goes grainy then starts to refine. Also, if the render region touches the border of either side, or top/bottom all sorts of weird things happen and rendering starts again but outside the render region selection.

I am testing the region render here and all works fine. Can you please test it again with other scene? ... if you have a scene with the problem, please send it to me to test it here.

Other question, are you using the network rendering?

-Juanjo

Thanks Juanjo, the scene I'm working on is on the heavy side, I'll try and reproduce the problem on a lighter scene. No network rendering.

Cheers

[BorisGoreta]

The new feature to load images from the Octane texture node does not refresh IPR when the image is loaded.

[MrFurious]

I'm having an issue with the latest daily build.. with region render when using F9. Rather than refine the given region, it will start re-rendering that section ie: goes grainy then starts to refine. Also, if the render region touches the border of either side, or top/bottom all sorts of weird things happen and rendering starts again but outside the render region selection.

I am testing the region render here and all works fine. Can you please test it again with other scene? ... if you have a scene with the problem, please send it to me to test it here.

Other question, are you using the network rendering?

-Juanjo

Thanks Juanjo, the scene I'm working on is on the heavy side, I'll try and reproduce the problem on a lighter scene. No network rendering.

Cheers

I've stripped the scene down to a single object and nothing at all connected to the render target. And the bizarre render oddity persists. If I start a new scene and load the bin object all is good, there's something inherent in the scene causing it but darned if I know I've tried everything I can think. Possibly a corrupted render target?

Cheers.


EDIT: I've tried swapping a fresh render target into the old scene, and vice versa: tried the scene render target into a fresh scene and it has no effect. Looks like it's not the render target.

[juanjgon]

I've stripped the scene down to a single object and nothing at all connected to the render target. And the bizarre render oddity persists. If I start a new scene and load the bin object all is good, there's something inherent in the scene causing it but darned if I know I've tried everything I can think. Possibly a corrupted render target?

I think that your problem could be that you have the LW native region render enabled in this scene and set to full screen ... I am not sure now, I should test it in deep, but could be problems if you have a LW region enabled and later you try to use the preview window "Region" feature. If you disable the LW render region in this scene, all should works fine with the preview window region tool.

-Juanjo

[gordonrobb]

Can I just check is this daily build the latest version of the plugin, and is it based on the 2.0.4 SDK otoy put out?