Call for Submission
NAB 2012 Best of the Best Show Reel
Submit your work today!
Theme color:
  • 1/3
Don't use the SDK when MAXScript will do.

Don't use the SDK when MAXScript will do.

A common mistake that I and others make is to use the SDK, when MAXScript can accomplish the desired task in a few lines.

Posted: Sep 15, 2009
Views: 8052
Published by: Christopher Diggins
Users comments (5)
Posted by Christopher Diggins on Apr 07, 2010 at 10:00 AM
Hello hedphelym, I replied to your post on the forum. We can continue the discussion there.
Posted by stig atle on Apr 01, 2010 at 03:44 PM
I tried this function in my code, but keep getting errors when trying to run maxscript through sdk..

area.autodesk.com/forum/autodesk-3ds-max/sdk/get-environment-maptexture-name-and-calling-maxscript-functions-problem/
Posted by Christopher Diggins on Oct 13, 2009 at 09:05 AM
These are excellent points. I am researching ways to simplify and explain function publishing so that it is easier to extend MAXScript with new functions and objects. Your suggestions help push this higher up on the priority list.
Posted by Martin Breidt on Oct 12, 2009 at 05:50 AM
Good advise, but maybe there should be more documentation on how to interface between MAXScript and the SDK.
Examples: How do I develop a new MXS function, using the SDK? How do I call MAXScript from C++/SDK? How do I pass variables between them? How do I expose my SDK functions to MXS? Documentation and a set of examples (from simple to complicated) would be nice.
Posted by olaffinkbeiner on Sep 16, 2009 at 04:34 PM
Hi Christopher,
this is a very good advice. Maxscript is very powerfull in many situations. Have you documented how to extend maxscript in the SDK Documentation? It seems very complicated as quite a lot of stuff is missing in Maxscript and some 3rd party plugins cant be controlled properly via Maxscript...

kind regards

Olaf

Comments
My Comment:
Notify me of follow-up comments?