41 comments

• Thirstydevil commented  ·  March 1, 2013 9:10 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'm a Maya TD with years of experience with python. I moved to softimage and started where I left off. Then moved to Max and Maxscript and feel like I've had my hands tied. All that language knowledge lost for a TD. To be able to write agnostic tools across multi platforms and deploy is a must. Python is everywhere now. Houdini, Nuke, Massive Pro, Maya, Softimage, Modo...

• Mambo4 commented  ·  February 21, 2013 8:58 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  As a technical artist transitioning (painfully) from Maya to Max, I'd say that Python support will keep Max competitive. Max script is useful, but not extensible, and there is much it does poorly or not at all that python has already covered in its many modules. Plus python has become the de facto standard scripting language for technical artists in general.

• jedie commented  ·  July 10, 2012 5:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  See also: http://area.autodesk.com/blogs/maxstation/n142-api-wishlist-surveys-for-autodesk-products

• javabeans commented  ·  June 2, 2012 11:02 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Cpython integration rocks! Since Max and Maya as a product line,why not keep the scripting things consistency with each other?

• Sebastien commented  ·  April 2, 2012 6:00 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I also lean more toward CPython. Though I probably could live with IronPython I guess.
  As long as it can be hooked to an external IDE (API inspection/completion etc...), which is what is annoying me with the Blur implementation despite its awesomeness.

• Jens commented  ·  March 29, 2012 2:05 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Seems that Python isn't included in max 2013, isn't it?

• Anonymous commented  ·  March 15, 2012 1:33 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Python support in 3ds Max, would make things really intresting. Developing tools with ease with support of the awesome already existing Python modules to make it even more powerfull. Imagine, creation of assets liberaries, submitters or extend with functionalities to get the best out of your reanderfarm. With no knowledge of C# and the horrible Max script, but just Python, it just works. I would love to see this feature in 2013 a.s.a.p.

• Ravichandra Seveelavanan commented  ·  December 26, 2011 8:21 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Python!

• Lukas Dubeda commented  ·  December 5, 2011 11:53 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  CPython, that is. IronPython just isn't good enough in the global-scale, long-term.

• Johanna commented  ·  December 5, 2011 11:24 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Yes ! Python in 3ds Max !

• Antoine commented  ·  December 1, 2011 3:39 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please finally add Python inside 3ds Max

• Anonymous commented  ·  November 16, 2011 9:46 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I would love to have Python in 3ds max.

• Videep commented  ·  November 8, 2011 10:43 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  YAYYY!!! Python in 3ds Max!!!

• Anonymous commented  ·  November 7, 2011 2:17 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  pyhton, yay

• Anonymous commented  ·  October 30, 2011 8:21 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please, make python support in 3ds max

• Anonymous commented  ·  October 30, 2011 8:20 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please, make python support in 3ds max

• kubi commented  ·  October 15, 2011 7:21 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Please, make python support in 3ds max as it is already in maya!

  Thanks for your products!

• Christopher Diggins commented  ·  September 29, 2011 9:30 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I would like to see this request broken up into two separate requests:

  1) IronPython support
  2) CPython support

  This way we can get a more empirical sense of how important CPython integration is to people over IronPython (which is massively easier to support).

  I think the reference to Py3dsMax is not particularly relevant. It is only one of many possible approaches to supporting Python via CPython.

  Note: for those interested in IronPython please take note of the new .NET SDK enhancements in the 3ds Max 2012 Subscription Advantage Pack (http://area.autodesk.com/blogs/chris/net_sdk_enhancements_in_the_3ds_max_2012_subscription_advantage_pack).

• James commented  ·  September 14, 2011 8:44 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Well, since Autodesk's other product Maya uses PyQt, I do hope that they care us enough to use a version of Python that also support the PyQt, so studios can spend time on just one single tool UI that would work for both Maya and Max.

• kingmax.res@gmail.com commented  ·  September 7, 2011 6:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  However, I am absolutely NOT against IronPython and C#. You see the .NET framework is absolutely fabulous and leveraging it would make a lot of sense. Also, since Max is strictly a Windows application, .NET integration and therefore IPy integration would be the most logical step. But again, native CPython integration would certainly be better. We can always go for Python.NET modules if we really need to. ;)