Which feature do you need the most? Tweet

[fantome]

extend support for color vertex attribute and float vertex attribute to
- curves object
- particles object

[scooternva]

For the LightWave plugin, it would be nice if Octane's nodes were more closely integrated with the standard LightWave nodes.

1. The LightWave "Input" and "Instance Info" nodes have all kinds of useful data points that would be invaluable as inputs for Octane material and texture nodes where randomness and/or instanced objects need to have their textures/materials varied based on position, distance from the camera, etc.
2. The LightWave Math nodes would greatly expand on the limited math functions available in Octane.

[Goldorak]

For the LightWave plugin, it would be nice if Octane's nodes were more closely integrated with the standard LightWave nodes.

1. The LightWave "Input" and "Instance Info" nodes have all kinds of useful data points that would be invaluable as inputs for Octane material and texture nodes where randomness and/or instanced objects need to have their textures/materials varied based on position, distance from the camera, etc.
2. The LightWave Math nodes would greatly expand on the limited math functions available in Octane.

This could be solved with OSL state and utility nodes. They exist, but we plan to bake them in by 2019.2 RC1

[scooternva]

Re the OSL nodes: It would be nice if the OctaneRender plugin for LightWave behaved more like standalone OctaneRender as far as the user interface is concerned. Simple example: your own Mandlebrot example (https://docs.otoy.com/osl) in the online documentation. In standalone OctaneRender there's a nice set of sliders for the numeric inputs. In LightWave, all you get are the connection pins. This is especially a problem with enum-type inputs (e.g., "mapper"), and it makes using string inputs (e.g., to select a filename) impossible. This really needs to be addressed.