OTOY Forums

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

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.

scooternva wrote: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

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.

1) Splash Screen on Load, with a racing sound.

2) Also, visible moving flames around the render speed while render is taking place. The render speed itself (font) could pulse between white and glowing red.

3) Finally, when you activate RTX mode in Preferences, a deep dramatic voice that would say "R-T-X....ENGAGED"

fantome wrote:Nested Dielectric

pic3.JPG

for the love of god, please add this. there are SO many issues working with dielectric surface interactions that it's not even funny. other render engines have had this for years...YEARS

in the scatter node of Octane Standalone, ability to edit the default input field

Code: Select all

M00 M01 M02 M03 M10 M11 M12 M13 M20 M21 M22 M23

To be able to add :
1 - vector v attribute for motion blur computation of each instance or compute the motion vector pass correctly

Code: Select all

M00 M01 M02 M03 M10 M11 M12 M13 M20 M21 M22 M23 V

2 - custom attributes that will be accessible with an instance color data or instance grayscale data node. for exemple we could add C1 for color attribute and F1 for float attribute.

Code: Select all

M00 M01 M02 M03 M10 M11 M12 M13 M20 M21 M22 M23 V C1 F1

on Scene import,
FBX Morph Shapes, aka Blendshapes

I think also a Rules of third overlay....will be nice for complex scene!