Vray ToolBox

Submitted by SimonBourgeois on Fri, 2024-09-13 06:28

Version:

1.0.6

Date Updated:

11/11/2024

It is a Vray version of my script "Corona Automator" It has a lot of features for materials, bitmaps ,cameras, lights and proxies.

Its main goal is to automate property tweaking, and save time on repetitive tasks.

for now the material part is focused on Vray Materials , it won't work on other kind of materials like fastSSS or other materials.

You have different options to access the desired materials or bitmaps, either from selected objects or from the slate material editor selection nodes, you can also target a specific Material ID or apply to all Material IDs.

update 1.0.1: Some Camera properties where missing, and remove round edges wasn't working on single VrayEdgeText, though it was working when used in conjunction of a VraycompText that use an additional bump texture.

update 1.0.2: A preset system has been added, you can create a preset file that will set new default values for all settings.

update 1.0.3: Some Settings were not well stored in the saved preset, if you have already create some preset files with 1.0.2 version you should recreate them because some UI elements needed to have their name changed to make it work properly, if you experience problems just delete the preset files before launching the script. I also fixed the Self-illumination spinner where it wasn't possible to go above a value of 1.

update 1.0.4: BugFix, crashed when selection filter was set to SME (Slate Material Editor), and Color Correction was set to Maps. Also the random values buttons in Color Correction settings were applying a single random value to multiple nodes instead of random values for each nodes when multiple color correct nodes where found in a single slot, for example multiple color correct in a multitexture node. Another update has been made to the function that converts standard or physical camera to Vray camera, now it is also transfering animation (position ,rotation, roll_angle, field of view).

update 1.0.5: A few bug fixed...

update 1.0.6: Last saved preset is now loaded as default,Updated "Multiple Cameras To Single animated camera" and "Animated camera to multiple cameras" now keeps every property of each cameras, it used to keep only position, orientation and field of view, I Also fixed a few bugs here and there...

Version Requirement:

Tested on 3dsmax 2024 and Vray 6

Other Software Required:

Vray

Links

Homepage URL:

https://simonbourgeois6.wixsite.com/monsite

Download URL:

https://www.mediafire.com/file/a0544xjj4lcg4yr/SimonScripts-VrayToolBox_V1-0-6.m...

Comments

Submitted by SimonBourgeois on Wed, 2024-12-11 03:47.

If it works...it works :)

Although it's better if it's fast and stable...;)
I keep rewriting my scripts as soon as I learn stuff that would make them faster and more reliable. The problem I am facing with Vraytoolbox and CoronaAutomator is that they have become rather large scripts. It takes a while to test every function before a new release, and changes made to one function can impact another that I didn't test before release, so bugs appear where previous versions were working well...
As I consider myself a beginner, I keep all my scripts free. Thanks for pointing out that even though it is free, it works better than some paid ones :)

Submitted by trick on Wed, 2024-12-11 02:51.

Same for me. But if it saves

Same for me. But if it saves me days of work I am surely not going to nitpick some unnecessary long loops or occasional crashes ;) I have expensive subscriptions on scripts/plugins that are way (read: tears in eyes kind of) worse!

Submitted by SimonBourgeois on Tue, 2024-12-10 07:46.

Thx !

Glad i could help.
Although it's nice to be called "the best", I must point out that there are much better MaxScript programmers out there. I'm still a noob, and a rather messy one. My scripts would certainly make some professional programmers laugh.:)

Submitted by trick on Tue, 2024-12-10 02:15.

You are the best!

Submitted by SimonBourgeois on Sun, 2024-12-08 18:08.

You're welcome :)

I forgot to add the filtering type because it wasn't the same settings for vraybitmaps and 3dsmax bitmaps, i left it on the side and forgot i had to deal with this...
I will add those settings in next update.
If you need you can use almost the same code as earlier, this time to set filtering to none:

(
	local matArr = loadTempMaterialLibrary "C:\...\...\\test.mat"--replace with your matlib path, keep the double \\ before filename
	local btmArr =#()
	for m in matArr do join btmArr (getclassinstances Bitmaptexture target:m) --loop through every materials and collect every bitmaptextures 
	makeuniqueArray btmArr --remove nodes that might have been collected multiple times, not always working, you can use a custom function to do a better filtering if you need to speed things up
	for m in btmArr do --loop through every collected bitmaptextures
	(
		m.filtering = 2
	)
	saveTempMaterialLibrary matArr "C:\...\...\\test_output.mat" --this will output a new Matlib with modified materials
)

Submitted by trick on Sun, 2024-12-08 16:50.

Thanks:) That will ehlp my

Thanks:) That will ehlp my rusty programming brain.

One more little thing missing in your tool is the filtering method (Pyramidal, Summed Area, None). With high res textures I mostly set filtering to none, because the other methods require a lot of memory.

Submitted by SimonBourgeois on Sun, 2024-12-08 16:10.

...

You can use this small script:

(
	local matArr = loadTempMaterialLibrary "C:\...\...\\test.mat"--replace with your matlib path, keep the double \\ before filename
	local NrmArr =#()
	for m in matArr do join NrmArr (getclassinstances VRayNormalMap target:m) --loop through every materials and collect every VRayNormalMap even if they are embeded in some complex materials like VrayBend, multisub, wrapper, override,etc...
	makeuniqueArray NrmArr --remove nodes that might have been collected multiple times, not always working, you can use a custom function to do a better filtering if you need to speed things up
	for m in NrmArr do --loop through every collected VRayNormalMap
	(
		if m.normal_map != undefined do m.normal_map.coords.blur = 0.1--here you can change blur value for normal maps
		if m.bump_map != undefined do m.bump_map.coords.blur = 0.5 --here you can change blur value for bump maps
	)
	saveTempMaterialLibrary matArr "C:\...\...\\test_output.mat" --this will output a new Matlib with modified materials
)

Submitted by trick on Sun, 2024-12-08 09:05.

I tried your method but there

I tried your method but there is a limit on the number of materials you can load. I am editing material libraries that have 500-1500 materials,each at least with 6 8K bitmaps in different channels. Loading these in SME simply crashes Max (or it takes at least more than a working day to load), even with 256G RAM. I think the fastest way for that is to write a script myself. Thanks for listening.

Submitted by SimonBourgeois on Sun, 2024-12-08 04:18.

Thx for the feedback :)

You are right, if you target bump slot, in Bitmap selection rollout, it will affect any maps that are in the bump slot of selected objects materials, if you need to change independently normal bump or additional bump map, you 'll have to use "SME-Selection" and choose "Maps" that way you can load multiple materials in slate material editor and select only maps nodes that needs to be modified (use ctrl to select multiple nodes), it will then target only those selected nodes. This is true for most case scenario where selection filters doesn't fit your needs, there is still a few case where it doesn't work well, even with SME selection, for example, maps that are used as mask in a vrayblend aren't tweakable by my script, i need to work on it...maybe in next update.

Submitted by trick on Sat, 2024-12-07 06:39.

Great tool !! ... just one tiny miss

I love this tool and I am using it all the time.

One thing is hard: when there is a VRayNormalMap in the bump channel that has both a Normal Map and Bump Map it is impossible to mass-change values of these texture maps (for instance the blur-value) seperately. Or am I missing something? Would be more great if this would be made possible. Under Bitmap Selection there should be a choice for Normal Map: this way the Bump map whether alone in the Bump Channel or as option in the VRayNormalMap, could be adjusted seperately from the normal map.

About this site