OTOY Forums

itsallgoode9 wrote:

aoktar wrote:I can be away from topic if you wish to hear words from Otoy not me.

no, it's fine! it's just first i'm trying to understand the meaning as a non developer, first, before we get to questions beyond the very basic meaning of that. I didn't want to put the cart in front of the horse, so to speak.

even you, as a developer, could probably answer this basic question for me that nobody from otoy has ever done.

It means that will allow to get more custom nodes to users. I'll pre-made scripted nodes to plugin. It will be not different to users than how is current nodes atm. Only problem is to wait for an osl release.

aoktar wrote:

itsallgoode9 wrote:

aoktar wrote:I can be away from topic if you wish to hear words from Otoy not me.

no, it's fine! it's just first i'm trying to understand the meaning as a non developer, first, before we get to questions beyond the very basic meaning of that. I didn't want to put the cart in front of the horse, so to speak.

even you, as a developer, could probably answer this basic question for me that nobody from otoy has ever done.

It means that will allow to get more custom nodes to users. I'll pre-made scripted nodes to plugin. It will be not different to users than how is current nodes atm. Only problem is to wait for an osl release.

Thankyou Aoktar.

So if I ask for a feature and I get a response of "when OSL is working, it is possible" I should take that to mean "we are not making that feature natively in octane. If a users decides to write that feature themselves, then it is available, otherwise, we have no plan to implement the requested feature"?

OSL is a standard, what this means is that you could download or purchase OSL texture files and they should work the same in every product that you use (if they support it). This is a huge advantage as otherwise you, as now, will have to convert your textures as you move your project from application to application.

For people who know how to code OSL, it opens up many more options for texturing in Octane (and the other apps that support it). OSL is a mini language in it's own right, some people have even written ray tracers using the language, it's that powerful. Hope this helps

Jason

I should add that what I'm excited about is the Blender already supports OSL. Once Octane supports it too, I will be able to use native Cycles textures without having to convert them to Octane's format.

thanks for helping clear that up. Being not a programmer, it was never clear to me.