Camera exclude function

[jackieteh]

I try State Sets before, but it load slow on my pc, especially when doing batch render, may be it just me

[ChuckRT]

I try State Sets before, but it load slow on my pc, especially when doing batch render, may be it just me

Its very complicated to use them but it is possible to edit them in a better way than the scene states, but as I recall Scene states can save transoformations and Materials contrary to State Sets.
Its an old tool that hasnt been updated, but maybe you could give it a try too, until Chaos add the Camera exclude function to Vray

[jackieteh]

Its very complicated to use them but it is possible to edit them in a better way than the scene states, but as I recall Scene states can save transoformations and Materials contrary to State Sets.
Its an old tool that hasnt been updated, but maybe you could give it a try too, until Chaos add the Camera exclude function to Vray

ok, i will try it, thank you sir.

[hill_lam]

Can you tell me how you would use this feature?

Best regards,
Vlado

I switched from Corona to VRay workflow because of Vantage. I was shocked that VRay, such a full-feature render, didn’t have the camera exclude feature - a feature I use in almost EVERY project for interior visualization.

For example, in Cam1, I want to show the complete bathroom + WIR space, but the BIR and door will block it. Almost every space, every angle, needs to hide some objects.

I can't use 3rd-party plugins to manage and temporarily hide objects, because I use Vantage & Live Link, and I turn on "Render Hidden Geometry" by default - the .max file of the interior scene is usually 2-4GB in size, and if I don't hide most of the things, the 3ds max viewport will be very slow.
So my solution is to temporarily move the objects underground, and move it back in another angle, which is very annoying.

[dimitar_panayotov]

Camera include-exclude visibility is something that is on our list. It is registered under VMAX-13906.

[jackieteh]

Camera include-exclude visibility is something that is on our list. It is registered under VMAX-13906.

Great to know this, can't wait to try it.

[DanSHP]

Call me crazy, but I just use separate max files for each view I find It is less of a hassle this way.

This way I can alter material properties on a view by view basis, delete a toilet - add a plant, reduce the height of a building etc etc and its all self contained within that max file. There's no messing around with state sets, scene sets etc...screw all of that!

[ChuckRT]

Call me crazy, but I just use separate max files for each view I find It is less of a hassle this way.

This way I can alter material properties on a view by view basis, delete a toilet - add a plant, reduce the height of a building etc etc and its all self contained within that max file. There's no messing around with state sets, scene sets etc...screw all of that!

Thats ok when your scene is not really heavy, imagine having 3 gb file and create 10 files just for 10 different cameras, and what happens when the client want some changes, you need to be equally careful managing files as doing it with state set, pulze, or what ever,
I mean, its up to you, its better to have options that having nothing

[DanSHP]

Thats ok when your scene is not really heavy, imagine having 3 gb file and create 10 files just for 10 different cameras, and what happens when the client want some changes, you need to be equally careful managing files as doing it with state set, pulze, or what ever,
I mean, its up to you, its better to have options that having nothing

I deal with large architectural scenes.

I get your point, but having used both approaches I find it more straight forward using a separate file for each view.
An advantage is you can optimize the file, for example there's no point having a 1GB Revit import in the file if it's not seen in the view or in glassy reflections, I'd just delete it. The same goes for Forest Pack/Chaos Scatters amongst other things. It speeds up max/rendering/network data transfer etc . If the client wants to make some amends, as long as the scene is layered up correctly I can switch updated models in and out quite easily.

I loathe having one large clunky max file with all my cameras in. Far more control of each view using camera dependent max files.