VRay Preset Manager released

[plastic_]

get it here:

http://plugins.marclorenz.com

let me know if you understand the concept of the link button...
i hope the manual is understandable.


current limitations:

-) The current version does not work with 3ds max 4/VIZ4.

-) Filtering type (Area, Mitchel, etc...) currently can't be loaded from presets because the setting doesn't seem to be correctly exposed to maxscript.

-) Map slots will not be included into presets.


planned for future releases:

-) support for other renderers.
would be a matter of minutes. if cebas and splutterfish release unrestricted trial versions i will do it.

-) max/viz 4 support, with some restrictions...don't know...depends on the feedback.

-) support for expressions in the presets.

-) subfolder organisation of presets

-) maps support



have fun!

[natty]

fine job ....thanks

Natty

[thumpa]

fantastic work!

thanks a stack

[kamel47]

Nice job mate.

Cheers

[dbuchhofer]

Looks nifty.. the subfolders would help a lot I think.. Also would it be possible to have the settings saved in a custom folder? For instance we've got 5 artists here.. if we could all use a shared settings folder on the network that would be nifty.. (Niftier then the little batch file to copy the vray.cfg heheh.)

one Question/Suggestion.. Does it by chance, store the Object Settings information in the System rollout? This is one thing that would come in very handy in setting up various passes for rendering and that i've been meaning to make but haven't had time to

one of the other things I find missing would be an easy material replacement system a-la Brazils quick thing.. but thats a bit beyond your scope

and lastly.. i'm still very new at scripting.. but if the intention is to keep this as a free tool, i'd like to put forward as a little help

[RErender]

Great tool! Thanks Marc

[plastic_]

Also would it be possible to have the settings saved in a custom folder? For instance we've got 5 artists here.. if we could all use a shared settings folder on the network that would be nifty..

the location of the preset folder is stored in the file 3dsmax\plugcfg\ml_vraymp.ini
i'm not sure if network paths work...

one Question/Suggestion.. Does it by chance, store the Object Settings information in the System rollout? This is one thing that would come in very handy in setting up various passes for rendering and that i've been meaning to make but haven't had time to

good question
what the script does is blindly storing EVERY render parameter exposed by VRay. if the object settings are not stored right now, it might be possible with future versions of VRay.

one of the other things I find missing would be an easy material replacement system a-la Brazils quick thing.. but thats a bit beyond your scope

i'm not familar with the current version of brazil...
i did a material converter script (material replacer) but it's for standard materials only.


greetings, marc

[wrtyler]

Here's my vote for a Max4 version. Don't have Max5, nor does it look like I'll upgrade to Max6.

regards,
wayne

[gafl]

Hi Plastic !

It is very kind of you.
Thank you for the job.

Gafl

[nlo]

best vray script so far!
thanks.

[timmatron]

Will there be a version available for VIZ 4 in the near future?

[3dform]

A script that made it into production at the same day. Very good, I love the way to edit the setting by my self.
Anyhow, an interface for what to copy/overwrite would be nice.
Example: You save your setting but then, you just want to paste the Gi Settings... A small dialog would help.

best regards,

robert

[plastic_]

Will there be a version available for VIZ 4 in the near future?

i can't promise it.
i only received 3 requests for a max/viz 4 version so far...

Anyhow, an interface for what to copy/overwrite would be nice.
Example: You save your setting but then, you just want to paste the Gi Settings... A small dialog would help.

there is no simple way for the script to recognize settings groups, like GI settings. vray stores/exposes everything in a big array of variables.
i avoided version specific ways of parsing settings, to ensure compatibility to future versions of vray. (or other renderers)
in case of your example i would just edit the preset, delete all non-gi lines and save it into a new INI file (with different preset name, this is important)
i will try to improve this workflow, but i like the idea of editing INI files instead of working with complicated dialogs. it's a very fast way.


greetings, marc

[Arkitec]

add me to the list

id love to have a preset manager for Viz 4

thanx

Arkitec

[cocolas]

thanks Marc,

appreciate you sharing this


paul.