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.
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.
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.
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)
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).
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
Talking about multiple cameras handling, I think it would be more time for someone (Chaos ?) to develop a true / complete / robust Batch Render utility …
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.
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.
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.