Notifications
Clear all

[Closed] guide to deploying scripts

Hi Brains trust coming from Houdini and its pure logical approach to tools and deployment I am having a hard time in figuring the simplest , most effective way to deploy a set of tools across multiple max users.

I have a number of tools to do some specific things attached to a floating tool bar / rollout. Which I can run right now from the max script editor. From articles I have read creating a separate menu along the lines of the main top menu is the way to go. What should I be looking at to incorporate the scripts I have at the moment into that sort of functionality, Any guides ?

B

3 Replies
1 Reply
(@gandhics)
Joined: 10 months ago

Posts: 0

What I usually do is… make each script as ms file and keep on network.
Then make companion macroscript which is calling that script.

Lets say you have a script for assign render path.
I save it as a assignRenderPath.ms in S:\maxpipeline\script.
Make the same name macroscript that has FileIn @“S:\maxpipeline\script”
Then user can make button, shortcut, menu whatever.
Or… nowadays I just use “X”.

You can make menu, but I rarely use menu in max.
Max is not a menu centric app.

There is some discussion on organizing your max scripts this thread
http://forums.cgsociety.org/showthread.php?f=98&t=1312522

menuman is the command to lookup for building menu items.
It’s a bit of a beast but careful reading and following the example code should give you the idea.
in order for anything to be launched form the menu it must first be a macroscript.

What I do is keep a folder of .ms files for all my tools, like the previous post.
and I have script that will create a macroscript for each tool that loads it with file in


macroScript MyTool category:"Mytools"
			(
				filein @"C:\Path\To\My\Tools\mytool.ms"
			)

once the macro script is created, it can be added to to menu with menuMan.add menu

Thanks for the pointers gents …

b