Page 1 of 1

converting standalone node data

Posted: Wed Jul 02, 2014 12:43 pm
by hdace
I've been trying to correctly interpret node data, for example in Glossy Material. If a node in the standalone says .5 and the same item in a node in the LW plugin (for instance, roughness) is a percentage, then I assume it'll work to enter 50. But what about specular? In standalone one can enter a decimal, but in LW one enters rgb values! So my guess is that in the standalone the range would be from 0 to 1, and in LW the range would be gray and between 0 and 255. So if standalone says .5, then one should set all rgb values to 127. If standalone says .75, then LW should have all three values at 191. Is that the idea?

Thanks, Hal

Re: converting standalone node data

Posted: Wed Jul 02, 2014 12:51 pm
by gordonrobb
Thats what I do yes, however, be aware that .5 in standalone, is not .5 in LW. there is a vast difference in the gamma that I cannot understand. I eyeball thins like colour and specular

Re: converting standalone node data

Posted: Wed Jul 02, 2014 12:54 pm
by gordonrobb
The other option is to use an Octane Float Texture as input for things like spec. It'll let you put a number between 0 and 1

Re: converting standalone node data

Posted: Wed Jul 02, 2014 3:29 pm
by hdace
I thought it was just me, but I think you're right about specular looking completely different. I should just eyeball it too. Weird. But if I want to use the standalone as a starting point, using the Float Texture node as the input would save me having to pull out the calculator all the time. Thanks for the tip.

Re: converting standalone node data

Posted: Wed Jul 02, 2014 7:34 pm
by gordonrobb
Also, don't make the mistake I make regularly and forget to match the Index number in Glossy materials :)

Re: converting standalone node data

Posted: Wed Jul 02, 2014 10:45 pm
by hdace
Yeah that's easy to forget. But it's a great feature and well worth mental note.