Personally, I think AD should consider robust python implementation to be mission critical to the survival of 3DS MAX. Having moved from Maya tech Art stuff to Max tech art stuff, I feel pretty strongly that Maya wins, by virtue of its implementation of Python.

Python in 3dsmax, no matter in what form, will bring 3dsmax closer to companies again.

Fully agree, this is a good idea for max.

However it’s all about implementation. Max, for me, has a history of half ass’d implementation of things that could be cool (c# for me wasn’t what it could be). It’s sounds like this is CPython and not IronPython, which is great. I think it’s still unclear if it is a wrapper for the api, or something that sits on top of maxscript (oh god i hope its not the latter!)

Maya’s implementation of python should have been the blueprint for the max team on this…

i’m reserving my excitement until i see and use it… but definitely positive.

Meh, I’m in the ‘fix what you got first’ camp.

The day I can write a new animation controller without c++, or messy hacking, will be the day 3ds Max is ready for more extension from my point of view. Having said that, I don’t need stuck my stuff up anyone’s pipelines. Maybe i’d like it if i tried it.

Speaking out of complete ignorance, what does python give you that c#, and mxs do not? (Or are we just talking code reuse, and not needing to learn yet another language for those in the Maya world) I’m assuming python would need to tie into the SDK similarly to how c# does – Which still feels half finished.

i might be the only person who is not happy that Python is coming into MAX. i’m a big fan of c#. i’ve hopped that c# comes to be fully integrated in max code development. unfortunately the integrations is buzzed, and the attempt of the Python integration makes it more problematic and more unlikely.

Denis, you should be on the beta, your contributions would be priceless.

I would agree with better c#. My options in max to do tech work are Maxscript (jesus!), or low level api c#/ironpython/VB/C++… i’m ignoring 3rd part stuff like blur’s python purposefully.

Maya was in much the same boat before python. Mel and c++. that was it. Python fit in to the space between and took off. c#, python… i don’t really care. I want a fast interactive, robust language. So if they got C#(dot net languages) doing live compiling and an integrated ide, and a nice ‘scripter’ level wrapper… sign me up.

There are, i would say, a couple of advantages to python

1. its super forgiving syntactically and really fast to write… i’m sure you could get as fast at c# after a while python allows you to get fast quicker.

2. A lot of other dcc apps use python (i know maya just got c# too…). But if i’m implementing a tool/code, for let’s say, motionbuilder to max, It would be much better if i could just use python on both ends.

3. python being an interpreted language gives you the ‘type and stuff happens’ out of the box…

There are pros and cons for both, obviously. I just want better options to work with.

probably some of you think that i’m a kind of ‘pythonofob’. no. well, i don’t like Python but i know it and use it.
i’m just against its implementation into max… now. today.
do we not have any other more urgent issues?
why is the Python? is it because the Maya has it?
well… make your vote for ‘what maya has but max doesn’t’…

good NURBS

animated PIVOT

fast view redraw

XREF animation

fast SKIN

python

…
is the python the thing that you can’t really live without?

Python in top of http://3dsmaxfeedback.autodesk.com/forums/80701-sdk-and-scripting-enhancements/filters/top ADSK makes people happy who vote for this feature.
In my vision Python integrations allows use same part of code of script in maya, max, si, but what else can give a phyton?

 I want to follow up on Denis question  'what maya has but max doesn't'...
 #interactivity in viewport for many stuffs and off course especially for [this]( http://www.youtube.com/watch?v=M_KgbPCAENI);) 
 #hair dinamics system and all dinamics in global
 #they fixed boolean issues
 #"viewport2"
 # Alembic cache
 # Hypershade speed and functionality for Slate
 # HumanIK
 # Integration of plugins (no need to by all theses cool stuff)
 etc.
 Max has better modifiers, modeling tools, work space and MXS :)

I hope that they will seriously consider that list of suggestions for the next release:thumbsup: