Reviewers: dev-osl_imageworks.com, osl-dev_googlegroups.com, Description: When using the new SHADE_LOOP_BEGIN/END macros in runspans mode, we actually use two nested loops which means a simple "break"

Right. Duh. OK, all fine then. -- Larry Gritz l...@...

Reviewers: dev-osl_imageworks.com, osl-dev_googlegroups.com, Description: Adds new form of spline in which the user can specify the number of knots to use in a supplied array. For example: spline(basi

OSL is applying to be a GSoC organization and as part of this process, we would like to point out to people that we have created an ideas page. Even outside of the scope of GSoC, there maybe some proj

Reviewers: , Description: First stab at runtime optimization of OSL bytecode, based on the actual instance parameters. This is a pretty big refactor, in that it moves quite a bit of compiler infrastru

Reviewers: dev-osl_imageworks.com, osl-dev_googlegroups.com, Description: Here are some fixes to get OSL to compile with gcc-4.4.2. Some of these fixes I shamelessly lifted from Chris.F's patch from a

Minor oversight on my part: Cliff, please don't commit the change until we get a signed CLA from Chris. I've sent it to him as well as posted it in the "downloads" section of the google code web site.

Hello OSL-folk! I've been thinking about our shading system and how it maps to OSL, and am curious what y'all think. First, our shaders inputs are evaluated in a very lazy fashion. For instance, if a

Reviewers: , Description: Significant additional work on "runtime code optimization" introduced recently. Quick run-down: * New constant folding for additional ops: neg, aref (was previously commented

Reviewers: , Description: OK, trying to explain this. Ci *= color_C is legal Ci = 0 is legal as a special case (clear the closure) but X *= (zero valued thing) gets optimized to X = (zero valued thing

Reviewers: , Description: In practice with our production shaders, were were often getting Ci's with many components that were duplicates. We figured this wasn't great for performance and also wouldn'

But then if somebody forgets to provide a closure subclass with a mergeable method, it will revert to the parent class, which will be wrong, wrong, wrong, it will say it's mergeable without being awar

Reviewers: osl-dev_googlegroups.com, Description: Now get_light_side returns the actual light side of the closure regardless of the singularity. And I have added albedo functions to all the bsdf's to

Reviewers: , Description: This round: * Constant assignment where the types didn't match (like R_float = A_int_const) were previously a dead end, since it couldn't directly alias R to A. But now we co

Reviewers: dev-osl_imageworks.com, osl-dev_googlegroups.com, Description: Adds a new closure that holds the real volumetric properties of a homogeneous medium. This isn't quite what is intended for vo

Sorry for such a mundane topic here, but I'm stuck getting this to build. I got ilmbase, openexr, boost1.42 and oiio built, I believe sucessfully, and everything is found after a minor amount of hacki

Hi, I'm looking to apply for a YafaRay (a free raytracer) GSoC project that aims to implement OSL support. I am wondering how this can be achieved. Is there any documentation for the OSL libraries? Ha

Reviewers: , Description: At long last, this patch switches from the old (intended to be temporary) behavior -- computing derivatives on all non-constant, non-int, non-closure symbols -- to correctly

Reviewers: , Description: Missed a couple: * Two spots where we asked the renderer for stuff and asked for derivs anytime it was float-based, instead of when the destination symbol had them. * Always

Reviewers: osl-dev_googlegroups.com, dev-osl_imageworks.com, Description: This is similar to a patch I've submitted to OpenImageIO. I'll cut-n-paste the same patch description here: This review allows