Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I use Maya to process 3D scan data for psychology research, I need to batch process groups of scans and data before moving them in to Unreal for experiments. I have python scripts set up that deal with as much of the workflow as possible and it saves me hours. They involve dealing with filenames, metadata, avoiding monotonous button clicking for dealing with the meshes, having a UI and a bunch of other stuff that would be impossible or difficult to do in LT without Python. Being self employed means I'd much rather be using LT than paying the extra for full fat Maya.
I just subscribed thinking I'd be able to use a tool written in python. I thought it was something I was doing wrong... I must have missed that missing feature in the comparison chart.
My daily driver is Houdini- I only use MayaLT for character animation. Maya's great for animation but not $200/month great. I can use humanIK and that's fine but the company I freelance for has a really great rigging tool that I can't use now.
While I'm at it... can we PLEASE import/export alembic? FBX works but alembic (or heck even USD) would be much smoother.
I already paid for the month but I'll be switching that off when this project is done (probably in a few weeks- well within my subscription term). If it had these additional features I'd be more likely to just keep it running or pay for a full year, but as of now it's just for when I need to do character animation a few times a year. TBH I'm looking for another animation tool- LT will do in the meantime.
@Anonymous I agree with you and all comments above. there are many good scripts I want it to use it but its all in python + even Mel, some scripts doesn't work because "The script is using expressions". all I hope they add new plan for indie and called Maya indie. there is discussion about this : https://forums.autodesk.com/t5/maya-ideas/hobbyist-indie-pricing-for-maya/idi-p/7958966
Just adding another voice to the chorus, I'm a week into the 30 day Maya LT trial at the moment, will not be subscribing without python support, I don't even use python, but need it for Mixamo's auto control rig script.
Yea, I looked at all these and there are no solid use cases here beyond hey, I use x app I need to work with python, oh well fix it.
Autodesk is not gonna compete with the flagship product so, needs to be better use cases here for python beyond I use x app and x app uses python, because if that is it, I think your better off looking for another app. If your unable to write the same functionality in MEL then I would just move on.
Python is very need for people who use Maya LT are largely hobbyists and just want to make cool things like me. I watch a lot of youtube videos for Maya and other 3d apps a minimum for all apps are that they have python scripting. Some go as far to offer other languages like c++ or javascript but very few have there own languages. This is because they know people already know python and will likely have no desire to learn a language that they can not use outside the app. Also python is incredibly easy to use and I believe is likely why most apps include this and why the full version does. Most tutorials I watch they talk about this python script they wrote to help with (insert mundane task here) and they link it in the description as they are very nice people and want to help but I can't use it cause there is no python support in Maya LT. I would say take out mel scripting and give me Python save mel for the full version of Maya. Give us a standard language so that we may use tools made by other and make our own to share with the community. Being able to use scripts in a standard language such as Python makes more people want to use and evangelize to everyone they know why they should be using Maya LT or Maya and not the others looking at you blender 2.8 and modo.
maxburger, gotta have a solid use case here beyond hey, I use x app I need to work with python, oh well fix it.
Autodesk is not gonna compete with the flagship product so, needs to be better use cases here for python beyond I use x app and x app uses python, because if that is it, I think your better off looking for another app. If your unable to write the same functionality in MEL then I would just move on.
Maybe you didn't read my full post please review it again. It's not a matter of I use x app and x app uses python so should Maya LT. It is that python is a STANDARD LANGUAGE and is much easier for someone to use than some proprietary language that will not be used outside of the application. I would encourage you to fully read a post and consider its point of view before hastily replying without fully considering the post you are replying to. There is a reason they have python in the full version and why most scripts are written in python. Its because its is a standard language that is used everywhere from CLI (command line interfaces) to apps like Fusion 360. In order to make Maya LT more user friendly and in so doing so increase adoption it is necessary to have a standard language like python for scripting.
maxburger, I'm fully aware of what python is. I did read the post, granted I thought it was long winded. I'm cutting straight to the point and will reiterate because it appears you didn't read my post. Autodesk is not willing to put python into MayaLT, because the flagship product already has it in there. Bottom line, Autodesk gotta make money. So now that we have gotten that out of the way. Autodesk isn't willing to waste the engineering resources on it.
If you are really about python as a standard language then use another 3d app. You don't need MayaLT, either go grab the student version and work out of that, or buy the full version. If that doesn't suit you then you gotta find another app to do it in. Otherwise your stuck with MEL, unless you plan on cranking out code samples to show the difference in functionality.
Furthermore MayaLT has been out for what 6 years now...and Autodesk hasn't added it yet. I'm fairly confident that your beating a dead horse.
It was very disappointing to find out that MayaLT does not allow even running the python scripts that were created in the full version of Maya. This is a very poorly thought out implementation at best. SideFX got it right when they allowed their "Houdini Core" version to access the tools written by their "Houdini FX" version. This allows studios to buy both the full and light versions of the software. Since my client uses a game engine for rendering, I was planning to recommend this model; however, since python is not even accessible in the LT version, I will likely recommend that all artists go to LT and that the developer will have to make do with what is accessible in LT as well. So to be clear, instead of recommending 5 full versions and 8 LT versions all 13 licenses will now go to LT. Not only will Autodesk lose money from this particular company, they will be less committed to the Maya pipeline and more likely to switch to a solution like Blender.
If someone can hear in Autodesk, you need soon to either update Maya LT and add such much needed features like Python support, or make Maya Indie a real product available to everyone with competitive pricing. Currently the full Maya is too expensive and Maya LT is too limited in features, so between Houdini Indie and Blender 2.8 there is little room left to support sticking to Maya for much longer.
I can't believe that Autodesk after all these years did not listen to the community and did not add python support to Maya LT. It's needed to be connected with all features to UE4 Editor.
So, I will still stick to blender until Autodesk add Python Support to Maya LT. I hope the rest of people who are waiting for this will do the same.
Adding to the dogpile begging for Python in MayaLT.
I really want to stick with MayaLT for my projects, but there are so many useful plugins out there that I'm essentially locked out of or can't write myself because the lack of Python support.
If you have saddled yourself to an all python workflow and you can't illustrate or give any remote use case on going over why python is needed in mayaLT outbeside, hey I just want it because that's my flow...then you might as well find another software...
and plugin wise either find a mel version of it or move to another software.
@Anonymous : Yo do not need to comment every post here with your opinion, which no one else who post here wants to hear.
Your messages don't help anyone either.
Many people, same as me, still think that Python Support should be supported by Maya LT, even when you do not need it or even when you have the full Maya version.
And it's totally Ok, that we complain about this in this forum. We hope Autodesk change his mind about this.
I also do not see an official statement of autodesk in this thread, that they will never consider it.
Full Maya Edition will have other features, which make it better as LT. But simple python suppport should not be the case, because python is simply needed to use Maya with other third party tools/plugins, which support Maya only with Python support. To strip Python support will not make us buying the Full Maya Edition, but it's simply making us buying no Maya Edition.
And we post here because we would like to work with Maya LT and still in a production pipeline with the rest of the tools we need. And for that, Python support is needed. And Full Maya edition is not option in most indie studios or other start ups.
And again, the same thing give an actual use case instead of "hey, I want Maya because that's just my flow." When you finally figure that out, maybe that's when Autodesk will listen to you. Stop beating a dead horse.
