Vray ToolBox

THANKS VERY MUCH FOR THE TOOL! SO IT LL BE GREEAT TO HAVE SOMETHING LIKE FOR FSTORM ENGINE! THANKS IN ADVANCE!

You can find FStorm version here: http://www.scriptspot.com/3ds-max/scripts/fstorm-toolbox

best!

Maybe you can make option "open undocked", and save window position?
So we can open it on second monitor, bacause script has wide interface, and on my 14" he is too big )

I've updated the script.
In preset tab there is now a Dock option, you need to save a preset so that next time you open it, it will be docked or not, the default is docked. It will also save the dialog position, so when you save your preset first undock the script and put it where you want it to be next time you launch it.

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!

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 :)

You are the best!

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.:)

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.

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.

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.

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
)

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.

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
)

all in one tool

thank you so much it is working good and help to modify material value and more . . .

Thx for the feedback, glad you like it :)