VRay version of Maxwell Camera Listener

I was at a conference last week, and one of the presenters was talking about Maxwell. There was this script (not sure if it was a part of Maxwell or something they had written themselves) called Maxwell Camera Listener.

Essentially, it listed all cameras in the scene with exposure values, focal lengths and render sizes. Damn useful.

Could this be added to VRay?

I’ll write it if ChaosGroup isn’t planning something similar to “VRayLightLister”, but I don’t know about “Render Sizes”, that seems scene dialog resolution dependent.

There was a request about this a while back, to have a “Camera lister” the same as the light lister. It is on the “to do” list.

Best regards,
Vlado

Yeah! Good to hear Vlado.

In the meanwhile I use my properties copy/paste script to copy camera/object properties from one object to another (it includes an include/exclude list), it was written specifically for normalizing camera settings.

http://www.scriptspot.com/3ds-max/scripts/copypaste-object-properties

Interesting. Scene render size is one of the critical things for us. Rarely are two cameras in a scene the same size.

I’m sure there is something like state sets, scene states, scene sets or whatever built into max, but I’ve never quite got my head around it.

Batch render can store different resolutions per camera if that would work for you, all the sets/states features are for more complicated things (and as such make something so simple super complicated)

I wish batch render would let you save V-Ray raw image file’s… so you could save multichannel exr’s

boom

No, resolution sizes we won’t do; the output size is handled by 3ds Max, if we attempt to meddle with this I can see only trouble. We can do it if you use the VFB, but it can be potentially cause a lot of confusion (i.e. you set up one size in the Render Setup dialog thinking this will be final size, only to realize in the morning that you had camera overrides and something else came out).

Best regards,
Vlado

I’ve have written a camera lister and put it on scriptspot http://www.scriptspot.com/3ds-max/scripts/vray-camera-manager

I’m actually going through a bit of a re-write so if there are any features that you might find useful I’ll try to add them.

Hello,

FYI a french VRay user developped this script : http://share.mattguetta.com/X4oU/1cZOhxyp
This allows to set a different output size for each camera, relying on custom attributes … very very (did I say “very” ??) useful !!!

We already use your camera manager, Daniel - very useful. Maybe a few things here and there to improve, but nice tool for us since we regularly render more than 10-15 cameras per project :wink:
Talking about multiple cameras handling, I think it would be more time for someone (Chaos ?) to develop a true / complete / robust Batch Render utility …

Regards.

sounds great. I will take a look…

Mmm. Just tried this but I now get a script error every time I create a camera: something about Unable to convert: OK to type: Boolean.

There’s always this one…http://www.scriptspot.com/3ds-max/scripts/vraycamlister. I used it for a while to list the cameras but got tired of the interface so I updated it a bit with a bit more functionality…

It’s been very useful for me but still most of the code is based on Track’s hard work so I’d rather not post the script. Just an idea for future interface reference.

Weird - this hasn’t been reported yet AFAIK. Could you please give a bit more details (3dsmax version for example) so that I can transmit to the dev ?

Max 2014 SP5

I’ve removed it now as I didn’t really have the time to troubleshoot. Basically, I opened up a fresh session of max, clicked to drag a camera (max or vray) and as soon as I did the script window appeared with the error.

For us, render size is the critical element.

Hi Tricky :slight_smile:
I’ve just transmitted your problem to the creator of the script … let’s see what he’ll come back with :wink:

Cheers.

Thanks Nico for the script.
I installed it and first I had the same problem with Richard but then when I installed into enu-application data, it runs without any problem.
Sad part is that it doesn’t work on old cameras but just newly created ones.
Now I have to re-create all.

Hello Pixela :slight_smile:

Yes, custom attributes aren’t added to existing cameras :frowning: I’ll ask SugaR if he can do something about that !

Cheers.

Is it just render size you would need or are there other settings that you would like to set for each camera?