OSL environment hdri per camera?

[josh.sarantitis]

Hi, love the OSL environment shader but any recommendations to save OSL environment hdri per camera view so I can have different settings in each?

thanks!

[madsd · Accepted solution]

You can wire up multiple maps to the Color Array map, and drive the input with an integer.

So when you change camera, you just click the integer so it matches the camera and you are done.

It can be done in multiple ways however, and you can write a custom shader setup that works for your special case.

Small illustration.

[josh.sarantitis]

Nice solution, thanks, I guess I can try to save this in material settings in the scene states in order to batch render? Will it save the the number settings?

[madsd]

If you can reach the Integer node, which is like any other map, from within statesets, then yes.

Im not a state sets guy, I use Arnold Operators instead.

[josh.sarantitis]

hmm, I stay away from state sets usually myself. Really like the scene states for batch rendering.

I tested it and scene states/ materials does not save the integer change. No way to link up a camera view instead of an integer huh? I guess I can put in frame number and have one for each camera (bit of a pain though)

[madsd]

cameras[] is an array of scene cameras.

if you pick cameras[1] it will pick your first camera on the camera array.

You can wire this up in a scripted controller that is attached to the integer ( or index of the OSL array map )

[josh.sarantitis]

OK, way too simple, I just have to save the scene state environment setting for each hdri.

Then I can batch it easy!

Thanks!

[madsd]

Excellent

Also, I missread, thought you meant StateSets, not the batcher.

[josh.sarantitis]

I've never done scripting, this sound like maybe a good way to start. Would you be able to share any links that could be helpful. Thanks a bunch!!!

[madsd]

The links has to form in the brain, there is no shortcut to conforming ideas into concrete functional code.

No programmer has any solution before it's done, nor does the programmer have the ability to forsee all corner cases or special rules, better interop before start.

Its a process where you identify the initial parts and investigate properties around them and establish link through code to obtain a result in the end.

And you use the manual as only reference, for when you are stuck.

Only resort to broad general video material if you fail to understand a general concept, or details you cant get working while looking at the documentation. You need to get familiar with the syntax and manual and how to search for things you think that gives meaning, in any or all particular cases.

And first of all, start to look at, read, consume, understand every single character in a random script, then the next then the next, the content is irrelevant, the important thing is that you brainwash yourself to look at the code in no particular order and you will then start to see patterns, structures and then you have come far.
Do this for as long as it is needed, so you feel confident explaining a random script, pretending you are at an examn.