Re: OSL getmessage/setmessage
toggle quoted messageShow quoted text
I think getmessage is probably not the easiest way forward here. Generally we try to avoid calls that require holding onto state as much as possible (the trace call and getmessage being notable exceptions). In fact you probably noticed already that only the "trace" related getmessage calls will make it to render services. There isn't currently a form of setmessage that will invoke anything on the renderer services side.
It's a bit hard to say without knowing all the details of your use case - but perhaps you could take advantage of the "firstchannel" or "subimage" arguments to the texture call? This would allow you to return different values for different calls to texture3d. Or is there something about your use case that requires you to perform all the work in a single call to texture3d?
Can you give us a few more details about what you would like to pass in and out of the texture3d call?
On Wed, Mar 3, 2021 at 8:30 AM <elizabeth.bonnefoy@...> wrote: