9

1016 G lossa ry
MAXScript first searches for .mcr (macroScript
definition files) in the ui\macroscripts directory.
These macroScript definitions are not compiled at
this t im e ; rather they are just scanned to identify
themacroScriptsthathavebeendefined.
MAXScript next searches for .ms, .mse,and.mzp
files in the plug-in path directories (defined on
the Configure System Paths dialog (page 3–810)
and Configure User Paths dialog (page 3–808))
and their subdirectories, and compiles these files.
Thebasesceneanduserinterfacehavenotbeen
createdatthispoint,sonoviewportorscene
commandsshouldbeexecutedinthesefiles.These
files should primarily define scripted plug-ins and
utility functions.
AnyutilityfunctionsusedbythemacroScripts
defined when reading the ui\macr oscripts directory
should be defined in a .ms or .mse file in one
of these directories. You can prevent a nested
directory from being scanned by placing its name
in parentheses, for example "(old-versions)",
allowing you to enable and disable scripts in handy
directory-based groupings.
At this point, 3ds Max creates the base scene and
user interface. Any macro scripts used by buttons
intheuserinterfacearecompiledatthistime.
The automatic loading of the following startup
script files can be deactivated by turning off the
Auto Start MAXScript option in the MAXScript
page of the Preferences dialog, as described in
MAXScript Preferences (page 3–834).
MAXScript first searches for a file named
startup.ms in the following directories, in this
order:
1. The Scripts directory (defined on the Configure
User Paths dialog > File I/O panel)
2. The Startup Scripts directory (defined on the
Configure System Paths dialog)
3. The3dsMaxexecutablemaindirectory
4. The Windows NT 32-bit system directory
(system32)
5. The Windows 16-bit system directory (system)
6. The Windows directory
7. The directories that are listed in the PATH
environment variable
MAXScript stops searching when it finds the first
occurrence of startup.ms.
MAXScript then recursively scans the Startup
Scripts directory (defined on the Configure
System Paths dialog) and any nested directories
for .ms, .mse,and.mzp script files and loads
them. In this pass, any script files with the name
startup .ms areignored.Youcanpreventanested
directory from being scanned by placing its name
in parentheses, for example "(old-versions)",
allowing you to enable and disable scripts in handy
directory-based groupings.
If you specify a script to run in the command
line (-U MA XScript scri p t_na me), t he script
is executed at this point. (See the MAXScript
Reference topic “Running Scripts from the
Command Line”).