// Octane engine log:
CUDA error 201 on device 0: invalid device context
-> failed to allocate device memory
device 0: failed to allocate preview buffer

I had this issue as well and I'm using the latest stable version. I had to close adobe illustrator which was apparently interfering with octane ...

The values for material setup are colour managed making it difficult to fine tune properties. For legacy compatibility I propose to implement a checkbox for disabling colour management on a value.
Not sure what you mean here,
as far as I know, values itself in Octane Material are not color managed ...

Hey Guys,

I know this is still a test version, but we are very excited about the adaptive sampling feature, from which we would benefit a lot. So far we have not dared to test the new plugin. What are the current major issues that still remain with this test version?
Thanks a lot!

nedan wrote: Please, it will be very useful if this can be activated in a command line parameter, also.

I second this. Our internal render management systems only needs this for full usability.

I was referring to some of the basic material setup options such as specularity, roughness where the color picker isn't available.

A simple test of dialing in 0.5 values for any if these properties will not result in a 50% calculated value. If you compare specularity of .5 to 1 you'll only notice a ...

much appreciated, thanks!

#1 BUG
- There is a serious and easily recreated bug in the octaneGradientTexture node.
If a "color entry list" item has the property "RGB color" value of 0, It will become invisible/unreachable upon next load.

- The position values are normalized.

#2 UI update request:
Please implement a visual ...

This is a serious issue in our workflow. Please let me know if you need sample files to recreate.
Thank you!

The values for material setup are colour managed making it difficult to fine tune properties. For legacy compatibility I propose to implement a checkbox for disabling colour management on a value.

This is not a new bug, but I have noticed it's not listed here.
Currently there is no way to apply motion blur to instanced nparticles. (without instance the particles are not even rendered)