Vray 3dsmax State Sets Compatibility

[White Wizard]

Are there any known limitations between Vray and 3dsmax state sets (specifically using render settings and render elements)?

Another big concern is rendering different openexr sequences for each state set.

[Art48]

I've tried them briefly and was so extremely disappointed by the instability and issues like partial incompatibility with VRay. This is such a huge issue in 3ds max (talking about 2014 here, don't know if they improved much...). There are plugins though like Onion (Was that the name?) etc which handle render sets.

[Moriah]

State sets is really bad. Use RPManager. It saves EVERYTHING related to vray.

[White Wizard]

State sets is really bad. Use RPManager. It saves EVERYTHING related to vray.

Maybe in the future. It looks very useful, but I'm already bankrupting myself on all of the various plugins I need just to do the most basic stuff, let alone the learning curve involved in figuring out how to use all these different programs.

[vlado]

The render elements thing might be fixed in newer versions of 3ds Max; as far as I remember the trick is to use the "vrayVFB" parameter to enable and disable elements, instead of their normal "Enable" checkbox.

Best regards,
Vlado

[White Wizard]

The render elements thing might be fixed in newer versions of 3ds Max; as far as I remember the trick is to use the "vrayVFB" parameter to enable and disable elements, instead of their normal "Enable" checkbox.

Best regards,
Vlado

I did a quick test of this and state sets doesn't save the vrayVFB checkbox.

[Svetlozar Draganov]

According to my tests with 3dsmax 2017 and V-Ray 3.40.02 both Elements Active and vrayVFB options are handled correctly by the State Sets:

[kagemaru]

I did a quick test of this and state sets doesn't save the vrayVFB checkbox.

Same here. To be honest we haven't tried with 3ds 2017, but last time i checked on 2016 state sets were still unreliable on my tests.
I need to be able to check/uncheck the vfb because i still can't save render elements in a separated folder with it (btw will it ever happen?).
It would be very nice to start using them.

[NicoC]

As an additionnal solution, far less expensive than RPManager and more user-friendly (IMO only :P), you can try Reindeer. Still in beta, but very promising tool.

[Vizioen]

As an additionnal solution, far less expensive than RPManager and more user-friendly (IMO only :P), you can try Reindeer. Still in beta, but very promising tool.

Looks quite nice.

[White Wizard]

According to my tests with 3dsmax 2017 and V-Ray 3.40.02 both Elements Active and vrayVFB options are handled correctly by the State Sets:
[ATTACH=CONFIG]30974[/ATTACH][ATTACH=CONFIG]30975[/ATTACH]

I've been using 2016 but I may upgrade if it means I can use state sets. Your screenshots show the elements active checkbox registering but can you confirm being able to enable/disable separate render elements in different state sets via the individual vfb checkboxes? (Since Vray disables the standard enable/disable)

As an additionnal solution, far less expensive than RPManager and more user-friendly (IMO only :P), you can try Reindeer. Still in beta, but very promising tool.

This looks great. Although I have to imagine it's not compatible with rebus farm. I'll send them an email and find out.

EDIT: Well that was fast. Received this response from rebus:

I am quite sure we don't support this one.
But to make sure you might create a trial user, install our software and use the 10 Free Render Points to check with a small scene by your selfs. Our smartcheck normally tells you about any incompatible plugins.

The plugin claims it supports online render farms through scripts. I'm curious if it could possibly be scripted to work with rebus.

[White Wizard]

Got a very fast response from the guys behind Reindeer:

I also use Rebusfarm occasionally so I'm working on a submit script for automating submission to their farm.
Reindeer doesn't do anything special with the scene so it can't be incompatible with Rebusfarm. But it can greatly simplify submission.

-One way that already works is to simply press the "preview state" button to preview the scene and then run their own submit script.
-Also In the "Preview" state you can just save a copy of the max scene for submitting at a later time. This can be automated.


I would like to automate this further of course so we have a true "One click solution" and I've contacted them in the past but they haven't been very helpful. The main problem is that their submit script is GUI only, so there's no simple way to take a perfect max scene and submit by code. I have to write code that pretends to push the buttons in their interface. It works but is not elegant.


If you and other users can ask them to implement a simple submit function that's accessible by maxscript that would be the best solution.

Something like:
fn SubmitToRebus autoupload:true autostart:true =(
--Take the current scene and try to submit to Rebusfarm. Returns true on success and false on failure
)

[NicoC]

I'm glad you got an answer from David, the Reindeer dev. I've been in touch with him for several months, beta testing Reindeer. He's a very skilled guy, very kind and enthusiastic. On top of that, Reindeer is IMO a great answer to several production constraints - very powerful and flexible. And the price ... well ... I guess David deserves the community support to keep on enhancing this already great tool.

[Svetlozar Draganov]

I've been using 2016 but I may upgrade if it means I can use state sets. Your screenshots show the elements active checkbox registering but can you confirm being able to enable/disable separate render elements in different state sets via the individual vfb checkboxes? (Since Vray disables the standard enable/disable)

I mentioned in my previous post but here it is again.
Individual Render Elements are handled correctly via vrayVFB switch.

[jstrob]

Cool to know. It may be time for me to try the state sets again. in the past i tested them and they were too buggy. I will check reindeer too but I'm becoming allergic to plugin even if they are free. Cause when there is a bug it is difficult to find the source of the bug and you have to contact every plugin developer one by one to ask if their plugin cause be the cause... My bank account is also allergic to plugin. Also plugins always use their own way of thinking and each adds to the learning curve. And thats' why I want so badly to switch to Houdini as my main app (but for sure i will then use max as a second app).