OTOY Forums

atnreg wrote: But I don't understand the UVMap change completely. I understand if Octane can now use the first three UVMaps (of course names are definitely needed to be sure) but what happens if an object has more than 3 UVMaps? Will Octane crash, refuse to render...? The manual does not explain this, it only says "each object can have now up to 3 UV sets" so please clarify

juanjgon wrote: Currently only the first three UV maps are available to be used in Octane, all the other UV maps are ignored. Anyway I will try to add a global scene option to work with the old behavior, using the first UV map available in each vertex.
-Juanjo

atnreg wrote: Thank you for explanation, then at least I'm happy and it seems to use first one by default so it is working like before if you don't change that setting So, at least in my opinion, there is no need to make that separate option.

The only thing I hope are the names of the maps or is there some logic in the order of them? Are they in same order as they are in Modeler or Surface Editor's T layers?

BTW, why exactly three? Why not all there are?
Of course in most cases one is enough but as the maps are in object, why they cannot be all used?

Antti

juanjgon wrote: The new multiple UV maps system doesn't work like before if your object has more than one UV map because you need to select the UV map to be used in the texture image node, and only the first three UV maps (in the same order that you can see them in the modeler) are available now.

juanjgon wrote: They are three because currently Octane doesn't support more UV maps.
-Juanjo

Lewis wrote:

abstrax wrote:It's all explained in the 2.20 Standalone release thread: http://render.otoy.com/forum/viewtopic.php?f=33&t=44232

I woldn't call that and "all explained" so that's the main reason why i asked it here since i don't understand that explanation.

It says this:
"The option "keep environment" got removed from the render kernel nodes. This option never really made sense, since blurry effects like DOF don't work with it. With the modified environment render pass you can now compose something between the environment and the scene."

Maybe I don't understand what's explained there (english is not native language ot me so that might be part of it, sorry for that), So my question still remanins, is there a way to see environment as befor at IPR/render wotut addin extra step complexity of passes/layers ? All i get now at IPR is BLACK Backgorund . Also WHY removing feature ? You could just leave it there and not turn on checkmark if it didn't like feature or it didnt' work for your/somene elses' workflow, no need to remove it an dpossibly break other peoples workflow - right ?

Thanks

abstrax wrote: If you want to see the environment for setting up stuff, just disable the alpha channel. If you want to have alpha plus the environment render an environment pass.

abstrax wrote: "Keep environment" was always broken, because you can't use a simple alpha channel to cut out the environment from a normal render with environment. The border pixels around the cutout will always be a partial mix between environment and foreground which looks like wrong when you compose it onto a different background.

BorisGoreta wrote:Editing material in FiberFX node editor is not responsive, it lags a lot compared to editing the same fibres amount freezed to 2 point polygons and using normal nodal editor ( FiberFX disasbled ).

What I wanted to say is that there is a lot more unnecessary stuff going on under the hood then LW just sending surface update to Octane. ( my guess )