Principal question about the inner workings of Max Creation Graph

[Tupaia]

Hello!

Trying to get a better understanding about what's really happening in MCG...

If one creates a graph in the Editor and evaluates it, a .ms (Max Script) file that handles the new tools' UI (parameters and layout) is generated, as well as the corresponding .maxtool file (XML).

The 'initialize' function in the script references the .maxtool file which is loaded when the new modifier/geometry etc. is invoked on the stack.

Then, I suppose the actual graph is constructed from it internally, and evaluated...

How? What's the actual engine behind the scenes doing? Is this superfast C++?

What is MCG capable of, speed-wise?

Thanks!!

[Swordslayer]

---

@Tupaia wrote:
What's the actual engine behind the scenes doing? Is this superfast C++?

---

Currently it's mainly C# with a bit of P/Invoke added to the mix - using the .NET API, you can replicate most of the functionality. For details, check the MaxPlus library. Note that this can change anytime, and the documentation explicitly states that the MaxPlus methods and classes can change anytime, so basing a tool on them is not the greatest idea.

[Tupaia]

Sounds pretty good, thanks!

Looks like there's 2 node-paradigm programming languages now:

http://fabricengine.com/fabric-3ds-max-final-beta-come-give-spin/