What new features can we expect over the coming months?

[electric_eric]

Hi

I was just wondering what features are planned for future updates of the Octane Lightwave plugin.

Features I would love to see implemented would be:

The ability to use more than one UV map per mesh.

A gradient node

A mixer node which has blending options such as multiply etc.

It would be great to hear if any of these are planned or even possible?

Thanks

[juanjgon]

After release the stable build using the Octane 1.20 SDK we are going to continue development from this point, but currently I can't say more about new features.

About multiple UV maps support, currently you can have more than one UV map in the same mesh, but problem is that you can't have more than one UV map in the same vertex.

Anyway it is a good idea to have a thread with feature requests for the next release. All LW plugin users can use this thread to post them

-Juanjo

[kostache]

Hi,

For me the most important thing is a motion blur! I'm really hope to use Octane in my animation pipeline, not only for stills. When could we expect it in LW plugin?

Also, it would perfect to have a dynamic booleans and edge shader, like in modo, but this is a problem even in the native LW (thanks to Denis Pontonnier, that we have at least his plug-ins) and I couldn't expect to get this abilities in LW octane soon, but, anyway, why not to ask?

[gordonrobb]

Dynamic booleans would be a Lightwave feature. For eedge shader, have you tried messing with the dirt node, with the invert normals ticked. Have a look, you can get some good results.

For me, (as if I've note gone on about it before )

Motion Blur, although I've found a work around.

Gradients, vital in my texturing pipeline.

I'm sure they will appear in this great software.

[FrankPooleFloating]

Here are some of the features I want:

[1] Invisible to Camera

[2] Unseen by Camera

[3] Render Priority (ability to turn of rendering of obj, but still visible to rays)

[4] Camera can't see Object Feature

[5] Ray Charles Render Option

[6] Option to make objects cast shadows and reflections - but not appear in image.


I will try to think of more features when I get a chance.

[electric_eric]

I'd also like to see Octane working with the 'Matte Object' settings in the object properties render tab, not sure how possible this would be?

[funk]

I miss a few things from the standalone that we cant do in the lightwave plugin:

1) In the standalone we can change the max samples and it continues to render. In lightwave, changing the max samples makes the render restart.

2) In the standalone, I can click any node to look at its values without restarting the render. In lightwave every time I press EDIT NODES to view a new surface, the render restarts. You can actually pause the IPR, click EDIT NODES and unpause it and the render won't restart, but this is not user friendly.

3) In the standalone I can use the surface picker even when the render is paused. In lightwave if the IPR is paused, shift clicking surfaces in the IPR doesn't select them in the surface editor.

4) In the standalone, I can save my render at any time and allow it to continue rendering. In lightwave the f9 render must be stopped before you can save an image.

5) In standalone, not only can I save at any time, but I can also save in multiple formats (PNG 8BPC, PNG 16BPC, OpenEXR Untonemapped and OpenEXR Tonemapped) without re-rendering. In lightwave I have to render the entire image again if I need a tonemapped (LDR) and untonemapped (HDR) image.

6) Also related to the point above, the IPR can only save JPG and TGA. The formats in the standalone are much more useful.

7) In standalone I can change the render priority even while rendering. In lightwave I must close the IPR/f9, change priority, then restart it

8) In standalone we have a white balance picker that allows you to click on the render. In lightwave we have to eyeball it using a standard color picker.

I have more, but can't think of them at the moment

EDIT: Updating as I think of more