OTOY Forums

frankmci wrote:

MyDearestHao wrote:It has been reproduced, and the highlights even turn black

I can confirm this. It seems like every Chaos node writes to the same texture address space, so that every time one has to re-calculate, it overwrites any previously generated output.

Yes, here we have a glitchy case that's not working fine with current export structure. We'll look for it

The UI seems to be just knackered in the latest C4D. The drop downs have no names next to them.

Octane Sky is just broken the tab where you actually edit the texture is just completely missing.

Examples here: https://imgur.com/a/1yvKUbJ

gazhowgate wrote:The UI seems to be just knackered in the latest C4D. The drop downs have no names next to them.

Octane Sky is just broken the tab where you actually edit the texture is just completely missing.

Examples here: https://imgur.com/a/1yvKUbJ

Looks like something wrong on installation or version requirements?

Hello,

On Mac version, when I use an octane gradient and I undo, its very prone to crashes. In general undo while using the gradient seems to not be working as intended.

Cheers!

Octane native color GUI type has strange behavior when it is set to HSV mode - setting S ( saturation ) to zero reset Hue value too so we need to enter hue value again which is little difficult if we had stored exactly value here. It works different than C4D native one.

Octane Float Slider from User Data using in xpresso doesn't update in realtime. Mouse button must be released to update values :

Hello,

When subdivisions are applied (either via tag or generator) octane has a lot of lag in the updates. In fact sometimes doesnt update at all eg. if I drop a new material in there, I have to resend the Live viewer.

Have you noticed something similar? My object is not very heavy it must be less than a mil polys.

SSmolak wrote:Octane native color GUI type has strange behavior when it is set to HSV mode - setting S ( saturation ) to zero reset Hue value too so we need to enter hue value again which is little difficult if we had stored exactly value here. It works different than C4D native one.

Yes I this is a bit annoying I would appreciate if this was fixed.

Now you have to use sliders in very specific order and its not convenient. If value=0 u cant move the other sliders at all and thats weird cause our brain starts working from top to bottom and top is the Hue

Hello, I would like to know when the 2022 new function help document will be updated for a more comprehensive study.

thanulee wrote:

SSmolak wrote:Octane native color GUI type has strange behavior when it is set to HSV mode - setting S ( saturation ) to zero reset Hue value too so we need to enter hue value again which is little difficult if we had stored exactly value here. It works different than C4D native one.

Yes I this is a bit annoying I would appreciate if this was fixed.

Right, but the most annoying sliders behavior is that if you move too fast to 0% or 100% value, Octane can't update that fast and if you stick on 0 or 100% it still display value like 60-80% and not update until you move mouse back to values between 0-100%. I mean that Octane stop updating if slider is physically under 0% or above 100% but it internally has still values between the whole range and display wrong values because of this updating lag.

LUT Reload button after changing LUT's path in Octane settings window doesn't work until window is not closed and reopened