1.14 - Now built on .NET 6.0

MXSPyCOM has been updated from .NET Core 5.0 to .NET 6.0.

.NET Core 3.1 & Switching from imp to import lib

Later versions of Python deprecate the imp module for the more modern importlib module. MXSPyCOM will not detect which major version of Python is being used (2 or later) and will pick the correct module to prevent a deprecation warning from being generated.

MXSPyCOM is now built against .NET Core 3.1.14, as .NET Core 3.0 is now unsupported.

Python re-import pathing fix

This release integrates a reimport pathing fix as suggested by community member Vulthur.

Python 2.7 support fix

A slight update to ensure the module re-import code works 100% of the time on Python 2.7.

Now with Python module reimporting. Built on .NET Core 3.0

An updated MXSPyCOM.exe built on the new .NET Core 3.0 libraries. This release also adds automatic re-importation of Python modules so that any in memory copies of modules you edit in your IDE are updated when you execute the script from your IDE into 3ds Max.

This is also the first official release of MXSPyCOM by its new maintainers, Tech-Artists.org

Suppressible Error Dialogs in 3ds Max

Thanks to work by Gary Tyler MXSPyCom can now be called with the -s flag instead of -f to execute code in a running instance of 3ds Max but suppress any and all error dialogs that may appear. Instead, any error information is printed to the Listener.

The Encrypt Script Command Now Encrypts Scripts

Many thanks to user Feranti for catching a copy/paste bug that resulting in the encrypt script command option behaving identically to the edit script command option.

Now, with binaries!

MXSPyCOM

A modern version of MXSCOM, to allow for editing & execution of 3ds Max MaxScript and Python files from external code editors.

In 2005 Simon Feltman released the first MXSCOM, a small Visual Basic 6 application that took commands and sent them to Autodesk's
3ds Max's internal COM server. This allowed users to choose their own external code editor for editing MaxScript and to be able to
have their MaxScript code execute in 3ds Max by way of having the code editor utilize MXSCOM to send the file into 3ds Max and have it
executed. Modern versions of Windows can not use Simon Feltman's old MXSCOM.exe program due to it being ActiveX based.

MXSPyCOM is a C# based replacement for MXSCOM. It offers the same functionality as MXSCOM but can run on modern versions of Windows.
It also supports editing of Python files and having them execute in versions of 3ds Max, starting with 3ds Max 2015, that support Python
scripts.

To Use:

• Put MXSPyCOM.exe on your harddrive.
• Put the initialize_COM_server.ms file in %localappdata%\autodesk\3dsmax<Max Version><Country Code>\scripts\startup
  for instance, %localappdata%\autodesk\3dsmax\2017 - 64bit\scripts\startup
• In your editor of choice add an external tool.
  For instance, in UltraEdit (www.ultraedit.com) go to Advanced \ User Tools \ Configure Tools
  • On the Tool Configuration dialog insert a new command.
  • Set the Menu Item Name to something like, "Execute Script in 3ds Max".
  • Set the command line to the path where MXSPyCOM.exe is located, a -f command switch and "%f", which UltraEdit replaces with the
    filepath of the current document. E.g. C:\Program Files\MXSPyCOM\MXSPyCOM.exe -f "%f"
  • Click OK to add the command.