Package Details: maya 2024.2-1

Git Clone URL: https://aur.archlinux.org/maya.git (read-only, click to copy)
Package Base: maya
Description: Autodesk Maya 3D Animation, Modelling, Simulation and Rendering Software
Upstream URL: http://www.autodesk.com/products/maya/overview
Keywords: 3d Autodesk Maya
Licenses: custom
Submitter: aquarius
Maintainer: meepzh (ttc0419, aquarius)
Last Packager: meepzh
Votes: 21
Popularity: 0.000841
First Submitted: 2016-07-25 19:14 (UTC)
Last Updated: 2023-12-26 22:01 (UTC)

Sources (2)

Pinned Comments

meepzh commented on 2022-04-08 22:36 (UTC) (edited on 2024-11-09 17:44 (UTC) by meepzh)

We still investigating Maya 2025+. The licensing does not run [1] [2] [3].

Many thanks to ttc0419 for getting this set up and for writing these instructions originally.

Installation Instructions:

To download the latest version of Maya, go to your Autodesk account Products and Services and save the Linux tgz file to any location of your choice.

Extract the tgz file to any location of your choice.

Maya is now split into several packages as it is for the official rpm installation. You will need the following files from the extracted tgz file to build some other packages as well:

  1. (required) Packages/adlmapps*.rpm to build adlmapps
  2. (required) Packages/adsklicensing*.rpm to build adsklicensing
  3. (required) Packages/Maya*.rpm to build this package
  4. (optional) Packages/package.zip to build maya-arnold
  5. (optional) Packages/Bifrost*.rpm to build maya-bifrost
  6. (optional) Packages/AdobeSubstance3DforMaya*.rpm to build maya-substance, if you don't want to download directly from Adobe
  7. (optional) Packages/MayaUSD*.rpm to build maya-usd-bin, if you don't want to download directly from GitHub
  8. (optional) Packages/LookdevX.rpm to build maya-lookdevx

Packages 1 and 2 are required to use Maya and 4 to 8 are plugins that can be installed when needed.

You will need to move the rpm files to the directory containing the corresponding package's PKGBUILD file. Please refer to the AUR wiki for further installation details, since AUR helpers may or may not work with this package.

After installation, you may wish to enable the Autodesk Licensing service with systemctl enable adsklicensing.service. This service is started automatically one time when installing and removing this package.

Note that the install file will automatically register and deregister Maya with the licensing service if you are using the adsklicensing package. You may need to restart the adsklicensing service and reinstall Maya if adsklicensing was upgraded and running at the same time.

Launch Maya and log into your Autodesk account or enter your product serial to check out a license. Note that Wayland is currently not supported by the licensing software.

Please note that the Maya executable is patched to launch with the --single-process flag to address launch issues with the Application Home. You may try to opt out of this patch if this does not present an issue for you.

Troubleshooting:

If you are having the following font error, Failed trying to load font : -*-helvetica-bold-r-normal-*-11-*-*-*-*-*-iso8859-1 //, first try the Autodesk recommended commands with your normal permissions.

xset +fp /usr/share/fonts/100dpi
xset +fp /usr/share/fonts/75dpi
xset fp rehash

(source)

If you are still seeing font errors, you can try one or more of the following:

  1. Install xorg-mkfontscale and run mkfontscale in /usr/share/fonts. Then re-run the xset commands above.
  2. Try running the xset commands with superuser permissions.
  3. Try enabling and generating the following locales: en_GB ISO-8859-1 en_US ISO-8859-1

If you are having licensing errors, you can refer to this comment/forum post by mac666er recommending you to only use the en_US.UTF-8 locale or this comment by TheSunCat recommending you to disable Wayland.

If your launch process hangs at the OpenCL initialization, you may wish to check for OpenCL conflicts as mentioned in this comment by TheSunCat. You may also need to rename/delete the intel-openapi icd file in /etc/OpenCL/vendors as mentioned here.

Cheers

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 16 Next › Last »

theMaizeOfficial commented on 2021-09-08 14:51 (UTC)

@costashatz https://help.autodesk.com/view/MAYAUL/2018/ENU/?guid=GUID-D2B5433C-E0D2-421B-9BD8-24FED217FD7F

I think this might help, i saw some one here was posting on the autodesk forum about the libiff but this has all the other info if you need it. its for 2018 but im sure if there is is this one there will be a 2022 version of this link some where, if this helps id like to know the results and process. cheers

theMaizeOfficial commented on 2021-09-06 12:59 (UTC)

i think i just accidentally deleted my comment, for me its coming to a screaming halt searching for libtiff.so.5 then displaying Segfault (a bunch of crap only aliens can read) (Core Dumped). so to me it seems like those two issues are going hand in hand together. i am just trying to solve it because i need this system to be up and running with maya... like yesterday lol

costashatz commented on 2021-09-06 05:01 (UTC)

@theMaizeOfficial the libtiff issue is different from the segfault. Check here: https://bugs.archlinux.org/task/71330?project=1&string=libtiff. Also the libtiff issue does not prevent you from using Maya.

costashatz commented on 2021-09-05 17:40 (UTC)

@ozzy1202 I am getting exactly the same behavior here... Now not even Maya 2018 or 2020 that were working before are working, no matter what I try. With strace I managed to fix a few issues with locale (that could possibly create some issue), but never got rid of the segfault. For me this is either GPU-related, Qt-related or Adsklicensing related. But as you, I have ran out of ideas.

ozzy1202 commented on 2021-09-05 17:15 (UTC) (edited on 2021-09-05 17:16 (UTC) by ozzy1202)

I tried gdb maya 2020 and 2016 that were working before,

#0  0x0000000000000000 in ?? ()
#1  0x00007fffec8dca0c in TinputDeviceManager::createDeviceList() () from /usr/autodesk/maya2020/lib/libExtensionLayer.so
#2  0x00007fffec65c758 in Tapplication::create(bool) () from /usr/autodesk/maya2020/lib/libExtensionLayer.so
#3  0x000000000040f35e in TmayaApp::create() ()
#4  0x000000000040eea1 in appmain() ()
#5  0x000000000040d476 in main ()

These are the results (in both of them they look similar), but I can't find a solution based on that.

ozzy1202 commented on 2021-09-05 15:21 (UTC)

@costashatz no, I didn't. I tired a lot, even downgraded all packages that I have in my system effectively bringing it back to what it was some time ago when everything worked and it still segfaulted this time... I tired to follow it with strace but I am not skilled enough to figure it out that way. I kind of gave up on it for now because I run out of ideas. It is extremely strange issue, especially as it seems like it happens to just some people and seems to not affect others on the same OS... I also tested mayapy as you mentioned it works for you, it also works for me.

costashatz commented on 2021-09-04 22:46 (UTC)

@ozzy1202 @Tanghe did you figure out the segmentation fault? Maya was working fine until I updated a few days ago and now I am getting a seg fault. mayapy works ok. So it should be a Qt-ish issue that I cannot find (but I am not 100% sure). @galaxy0419 any ideas on what can be wrong with Qt or something else?

ozzy1202 commented on 2021-08-26 16:45 (UTC)

@Tanghe did you figure out the segmentation fault? I experience it too and I don't know how to get over it and I kind of need to run maya. I even tried it on maya 2020 that was working last month and it is also segfaulting now even old install of maya 2016 was segfautling. After some googling I also found someone on manjaro forums that has encountered segfault with maya 2018 4 days ago after update. I know manjaro is not arch, but maybe his case might be somehow related to mine and yours?

ttc0419 commented on 2021-08-14 12:19 (UTC) (edited on 2021-08-14 12:20 (UTC) by ttc0419)

@Tanghe Please make sure you follow the instructions in the pinned comment. if you want to start Maya in the command line please use the start script in the same folder instead of the binary directly. This version works fine on my intel machine.