Hi everyone, I'm just a simpel student and totaly new to this stuff. I read the specifications as soon as I could download it. Hopefully I can make it to set up the developing environment soon, becaus

Hello folks, In specification, it sais "Arbitrary derivatives without grids or extra shading points.", but I really confused how it works without explicit grid. Does it like the GPU, compute the deriv

"Radiance Closure" is definitely very neat idea. The concept of not executing the whole shader at once can be very powerful. From what I understand , closures save some shader local variables and exec

http://codereview.appspot.com/186244 This is the OSL-side change. On the renderer side, you still need to set the fields in the ShaderGlobals correctly. -- Larry Gritz l...@...

Guys, I just started looking into OSL. It certainly looks very interesting! Did I miss something or is it true that volume shaders are currently neither implemented, nor truly specified? I see that yo

Hi all, I've been looking through the OSL source a little, and I'm interested to see that you're using runflags for the SIMD state. I know that's a really conventional solution, but there's an alterna

Reviewers: osl-dev_googlegroups.com, Description: We were missing the derivatives in the I field which is important for background shader. This little patch fixes the problem. Please review this at ht

LGTM Having dev-osl@imagework usually works for me, but I don't see this mail. http://codereview.appspot.com/193063/show

I'm having some difficulty building OpenImageIO on macos (Snow Leopard), as a required pre-requisite for building OSL. The build of the external packages fails because libtiff doesn't build. Everythin

Reviewers: osl-dev_googlegroups.com, Description: Several additional warnings and some new errors occur when trying to compile OSL using g++-4.4.1. Errors were due to: - header rearrangements which ca

You could do what Google Protocol Buffers does and determine which hash map to use at configure time. It works with g++ 3.4.x all the way up to 4.4.x. See the m4 file at: http://code.google.com/p/prot

Reviewers: , Description: Many times I've been plagued by inexplicable crashes in loadshader.cpp, right at the call to boost::starts_with. I've wasted hours and hours and been unable to figure out why

Hi Larry - Just to be robust, would it make sense to make sure that source is at least as long as pattern? Also, is this the correct way to respond to a code review (in email)? Brian

Reviewers: , Description: It's possible to write a shader that has no instructions in the main program, but merely shuffles input params into output params (this is in fact done for certain "glue node

Reviewers: , Description: 1. Refactor "bind" to simplify the handling of globals. 2. Bug fix (exec.cpp:309) -- zero out local strings, the one place where uninitialized values in the heap can crash th

Reviewers: , Description: If you called context->execute() with a "sparse" set of runflags (such as if you were picking the subset of a set of rays that hit objects with the same shaders), it would us

Reviewers: osl-dev_googlegroups.com, Description: There was a problem with the sample function in beckman closure. A missing sqrt for sampling the tangent of theta. It was preventing reflections from

Reviewers: , Description: Bug fix: When a function's 'return' statement is not the last statement in the function body, we use a trick where we wrap the function in a 'do { ... } while (0)' and the re

Reviewers: , Description: This change allows a debug mode (set by attribute("debugnan",1)) that checks every value written by each instruction, and if any nan or inf values are found, issues a warning

You mean checking all the inputs? Sure. But let me check this one in first. -- Larry Gritz l...@...