I've been thinking about this while working with Maya. A lot of 3D work starts with a reference problem rather than a modeling problem. Before building something, I often want to understand what the real object does, how it is made, how its parts relate to each other, or how it is used. That's actually why I started paying more attention to ubergruber . It's a broader digital publication rather than a Maya-specific resource, so the useful part isn't necessarily finding a Maya tutorial there. It's finding information around the subject I'm trying to model. For example, if I'm working on a vehicle or industrial object, an article about the actual product, manufacturing process, materials, or technology behind it can give me reference information that a typical 3D asset site doesn't. I find that kind of background can affect the modeling decisions quite a bit — proportions, construction details, joints, surface breaks, materials, and even which parts should actually be visible. I'm curious how other Maya users approach this. Do you usually stay within dedicated 3D/CG resources when gathering references, or do you also use broader publications like Ubergruber when researching the real-world subject first? I'd be particularly interested in hearing what sources you find useful when the thing you're modeling isn't a common object with lots of ready-made references. Show More

If I intentionally create a benign cycle, I would like Maya to ignore it.  As it does for constraints.  Yes it's a performance hit.  But not everything is about performance.  Ease of use is also a factor that should be considered.  There must be an existing list because constraints don't cause a complaint. Show More

When I'm rendering in Maya using V-Ray's Frame Buffer, if I hit ESC outside of Maya (for instance if I'm then working in Photoshop whilst a render is running in the background), Maya will cancel the render.   Chaos have stated that it's an issue with Autodesk/Maya, and happens to all renderers. Please can Autodesk issue a fix for this?   https://forums.chaos.com/t/vray-stops-render-when-esc-being-used-in-other-apps/96804/4   It can cost me a lot of time if a render cancels halfway through and I have to restart it from scratch. Show More

1. Why are we here? The Crisis of Maya and the User Exodus To the loyal Maya community and the Autodesk Product Managers, I want to discuss a heavy but unavoidable topic: Is Maya truly in a healthy state right now? I believe many senior users share this sentiment: Maya's underlying architecture seems to be falling behind the times. We watch it become increasingly bloated, with modules from a decade ago stubbornly occupying our interface. And what is the result? We are witnessing a significant exodus of senior users—especially FX artists—who, in pursuit of higher efficiency and modern workflows, are reluctantly migrating to competitors like Houdini. Objectively, this is a dangerous signal for Autodesk's product ecosystem. Once users get accustomed to the sleekness and efficiency of other software and start making comparisons, Maya's future development will fall into a massive passive state. We don't want to lose Maya, but Maya must change. Otherwise, it won't just lose its lead; it will be left behind by the era. 2. Our Antidote: Maya Lightweight / Community Branch Instead of struggling in the heavy quagmire of the backend, let's travel light. I strongly propose that Maya should introduce a new branch, tentatively called "Maya Lightweight Edition" or "Maya Community Edition." This branch doesn't require earth-shattering backend refactoring. Its core selling point is direct and tempting: Thorough UI Modularization and the freedom of "out of sight, out of mind." Return Control to Users: We support users in freely hiding or marking any interface module. The "Legacy" Plugin Package: We create a dedicated "Legacy" plugin package to centrally manage those outdated functions. UI-Level Purification: Please note, we are not deleting these functions at the backend (that would be too radical and risky). We are simply "evicting" them from the UI interface. Imagine opening Maya and no longer being eyesore by modules you never use, like nCloth or old fluid effects. The interface is as clean as a fresh install. This experience of "hiding the useless" is the ultimate respect for the user. 3. A Victory for Realism: Why is this the Most Feasible Solution Right Now? I must candidly point out a fact that everyone tacitly understands: Maya's legacy code is heavily burdened. Undertaking a true large-scale refactoring is nearly an impossible engineering task, or the cost is simply unbearable. But this doesn't mean we are at a dead end. On the contrary, precisely because the backend is hard to撼动 (move), we need a "UI-level" lightweight solution even more. This proposal is not about forcing Autodesk into a bone-breaking backend revolution. It is about making Maya live more practically, longer, and more comfortably. This is a solution that is entirely feasible at this stage, with extremely low risk but high returns. It bypasses the most difficult backend code rewriting and strikes directly at the UI level—where user perception is strongest. This is the best path to "extend the life" of Maya and breathe new life into it under the existing architecture. 4. Smart Compatibility & A Data Goldmine: Reassurance for Product Managers I know what Autodesk Product Managers worry about most: Compatibility and Data Blind Spots. But this proposal perfectly solves both: Smart Compatibility, Seamless Switching: When you open a project file containing old features, the system will intelligently prompt: "Legacy data detected. Automatically enabling xxx Legacy Modules." Old projects run as usual, new projects run smoothly—no conflicts. The Most Authentic User Behavior Data: This is crucial! Currently, it is hard for the official team to know what users truly dislike. But in this branch, what users hide is the most authentic vote! The official team can clearly see: "Oh, 80% of users hid nCloth," or "Everyone dislikes that old render settings UI." This is far more accurate than any survey! It will guide Autodesk to use valuable development resources where they matter most, rather than blindly maintaining outdated code. 5. Playing to Strengths: The True Way Out for Autodesk To speak from the heart, Autodesk is not exactly efficient (or擅长) at grinding away at old backend code refactoring. Instead of consuming huge costs there, why not build a better "Container"? If Maya's modular architecture is robust enough, Autodesk can play the role of an "Integrator" in the future. Next time you see an excellent FX software or tool on the market, simply acquire it and plug it into Maya as an independent, modern module. This "Lego-style" ecosystem expansion is far more logical and flexible than patching and repairing. 6. Attitude & Ecosystem: Rebuilding the Cornerstone of Trust Launching a "Community Branch" is not just a feature update; it is a Declaration of Attitude. It sends a positive signal to all users: Autodesk has heard our voices. Autodesk is willing to change and make Maya better. We could even try offering this branch as a free value-added item in the subscription service, encouraging all users to experience it and provide feedback. To be brutally honest, Autodesk's current community and ecosystem construction is hardly satisfying. Every time I see Product Managers promoting Maya, proudly mentioning "We have an excellent community and ecosystem," as frontline users, we often find this statement laughable. A true ecosystem is not blown up by words; it is cultivated by an open, modular platform that respects its users. If these ideas can be implemented, they will provide a solid foundation for absorbing community plugins and third-party tools in the future. It will transform Maya from a "bloated beast" into an "open ecosystem." Maya users, we need this change. Autodesk Product Managers, please give us a reason to keep loving Maya. Show More

I feel like Maya's UI isn't bad (except for Hypershade ofc), but I think it could use a bit of consistency and overall a better design. First of all, the UI feels cramped and quite cluttered. I think you should organize these tools a bit more and give them a new set of icons. Secondly we have Hypershade. Nobody likes it, yet we still have it after a while. I am requesting a full overhaul for Hypershade with new node designs (I really like the look of the nodes in Maxon Cinema 4D) and much more useability for the artist. I would also like to see better value sliders (I personally like the ones in Blender over the ones in Cinema 4D or Houdini). I think we could also use the new node designs in LookdevX and Bifrost to be more consistent among Maya's Features. I think we could use a slightly redesigned timeline UI that looks like softwares like Cinema 4D (with the play, stop, reset, etc. buttons at the top rather than the side). Finally, I think that the animation scrubber thingy (idk what it is called. it's the little thing you grab to scrub between keyframes) should be consistent among all views.       Show More

Among the Upcoming Total Environment Projects in Sarjapur Road, this development is positioned toward buyers who prefer premium residential communities with thoughtful planning. The project is expected to include spacious homes, landscaped areas, recreational facilities, and community spaces. Its location near the Dommasandra side of Sarjapur Road provides access to several established and emerging infrastructure facilities. The surrounding area has become increasingly popular among IT professionals due to connectivity with Bengaluru’s technology hubs. Buyers should review official project information regarding approvals, configurations, pricing, and availability before making an investment. Total Environment Sarjapur Road is designed around the idea of combining contemporary urban living with nature and spacious surroundings. The development aims to provide residents with comfortable homes complemented by landscaped areas and lifestyle facilities. For families, the combination of larger residences, recreational spaces, and access to schools and healthcare can make the project an appealing choice. Professionals may also benefit from its position within Bengaluru's expanding technology corridor. The project can therefore appeal to buyers who want a premium residential environment without losing access to the conveniences of the city. The Upcoming Total Environment Apartments in Sarjapur Road are attracting attention among buyers searching for premium homes in East Bengaluru. The development is planned with spacious residences and lifestyle-oriented facilities suitable for modern families. Sarjapur Road has witnessed significant residential and commercial growth because of its proximity to major technology corridors. The proposed project aims to combine urban convenience with open spaces and greenery. Buyers can explore the planned configurations, floor plans, amenities, location advantages, and pricing before deciding on a residence. It can be an interesting option for those planning their next home in Sarjapur Road. Show More

Integrate Mudbox into maya. Request since 2018 ! Mudbox is now End of Line, but my support for it has been rewarded by killing it. Couldn't support it by getting the full package, but I subscribed to what I could afford. Now I have to replace it with something else, and pay few more month to convert all the mudbox projects. Instead I should have bought some other solution instead of paying for Mudbox. What is the strategy here, I really don't understand.  Punish the customers ? At least Refine feature could really be included in Maya. Support mudbox project import into maya ? Show More

- a procedural composting system - a 2D animation tools system  - a stackable modifiers system like 3Ds Max's  - anime creation and rendering tools and fx - newer motion graphics tools for 2D and 3D  - a real-time renderer  - a motion tracking system  - nodes and tools for texturing and procedural texturing ..  - new procedural tools for simulation .. vdb and more  - newer and stronger UI  - more tutorials on youtube    this is what i believe that Maya must have .. i love Maya and want it to stay at the top .. adding these features and making them strong, procedural and easy to use are a must in my opinion .. Show More

- Real-time renderer - Vulkan 3.0 viewport  - Built-in Compositor  - Non-destructive modifiers stack system  - 2D Animation integration in viewport and rendering ( like Blender's Grease pencil )  - Motion Tracking, camera built-in solver - Better motion Graphics tools  - New UI, improving the UI as a whole  - Easier installation method  - Preset Libraries, Materials, base meshes ... etc. Show More

Maya should add the capability of emailing and/or texting a phone number when rendering fails or is completed.  Show More

Hello Autodesk Team,   I would like to request a built-in "Blender" interaction mode (Keymap and Navigation preset) in Maya. Currently, many artists and students are transitioning between Blender and Maya, but the difference in navigation (orbit, pan, zoom) and fundamental hotkeys (G, R, S vs W, E, R) creates a massive friction and cognitive load. While Maya has standard navigation, allowing users to toggle a "Blender-style" mouse tracking and shortcut preset directly in the Preferences would significantly lower the barrier to entry for Blender users and improve overall workflow efficiency in multi-software pipelines. Thank you for considering this feature.     （日本語訳：Autodeskチームへ。Mayaに標準機能として「Blender」のインタラクションモード（キーマップとナビゲーションのプリセット）を追加することをリクエストします。現在、多くのアーティストや学生がBlenderとMayaを行き来していますが、視点操作や基本ホットキーの違いが大きなストレスと負担になっています。プリファレンスで「Blenderスタイル」に一発で切り替えられるようになれば、移行の障壁が下がり、複数のソフトを併用する現場での作業効率が劇的に向上します。ご検討よろしくお願いします。） Show More

Hi, It's been a while since I posted an idea. But this one is something that would be very useful to the team I'm currently. I work at a studio where characters get loaded in from different referenced files, so exchanable items (i.e cloth) can be loaded separately. And all the connections the need be made between the files get stored as code separately. We are currently having the problem, that a few very specific attributes are getting cycle checkend when those connections from code are being made, but don't cause cycle checks when being fully connected. With the current cycle check warning there is virtually no possibility to exactly know where it comes from, how to fix it or if it will cause problems down the line. It would be cool if instead of "-e off", cycle check also had the option "-e whole" or something along those lines, to show the whole cycle for people with more experience. So problems like the one we are experiencing, where a cyclecheck warning gets thrown during a script, can be better analysed. I think this shouldn't be too hard to implement, since cyclecheck has to run some kind of analysis where it finds the whole cylcle anyway, right?  Boring as it may be. This is my current Idea, and it would help me, my team and probably a lot of other tech savy people a lot.  Thank you for considering. Show More

I have a great idea! Here's what I think: Autodesk should add its own comment to each suggestion posted here. And they should be honest about what they think of the idea and what they plan to do with it. Or they should take this page down if it doesn't matter anyway. Please upvote this; otherwise, this “Ideas” section just doesn't make any sense. Show More

If I want to dynamically drive the limit of say translateY, don't have Maya report an error because the channel is locked or connected.  Please Show More

I have been using Maya for 17 years. I’ve seen the industry transition from complex proprietary pipelines to Python integration, to Arnold/USD, and now into the AI era.   I am reaching out because I want to keep Maya as my "home base" for production, but I am finding that to handle modern generative/AI creative workflows, I am currently forced to jump out of Maya into external ecosystems like ComfyUI.   **The Strategic Gap:** Right now, there is a disconnect. I am building 3D assets in Maya, but the "lookdev exploration," "texture variation," and "concept iteration" are happening entirely outside the DCC environment. This creates a fragmented pipeline.    **The Opportunity:** I believe Maya has a massive opportunity to lead here, rather than following. I am not suggesting Autodesk ship a raw, unstable generative tool, but rather an **"AI Orchestration Layer"** within Maya.   **The Vision:** Imagine a native Bifrost graph or a "Generative Node Graph" that allows us to:   1. Connect Maya render passes (Depth, Normal, AOV) directly to generative conditioning nodes.   2. Manage AI-assisted texture/lookdev iterations as non-destructive nodes.   3. Keep the creative exploration inside the Maya project context, rather than having to export to third-party tools.   Maya already has the best node-based system in the business (Bifrost/Node Editor). We have the logic, the data, and the pipeline. The next logical step is to bridge that with the generative AI models that are becoming industry-standard.   I love Maya and I want to see it stay the center of the production pipeline. I would love to see Autodesk lead this charge rather than leaving it to fragmented, outside workflows.   I would be happy to participate in a beta or research discussion regarding how this could work in a production environment.   Sincerely, Sgornippon   Show More

https://research.nvidia.com/labs/sil/projects/kimodo/ Kimodo is a kinematic motion diffusion model trained on large-scale optical mocap data. It is controlled through text and constraints to generate high-quality 3D human and robot motions. It seems to run on 17GB VRAM, but I hope this can be done on less, like 7 GB for example ? Alternative make it work in a cloud as a new edition to the character creator ? Add metahuman format to character creator ? Etc. Show More

Hello Autodesk Team,   I was wondering if there are any plans to support Autodesk Maya natively on Linux ARM64 platforms, such as NVIDIA DGX Spark. Since Maya already has native Apple Silicon support on macOS, it seems like ARM support is already part of the direction for Maya. It would be great to see that extended to Linux ARM as well, especially as more ARM-based systems are being used for AI, rendering, and workstation workloads. Right now, Linux support appears to be limited to x86_64. Native Linux ARM support would make Maya much more accessible on newer ARM hardware and would help studios and developers exploring ARM-based infrastructure. Thanks for considering it! Show More

For whatever reason, Autoupdate can't be changed to be driven by another control, which is fine. But it seems because of that it's also unable to allow that attribute to drive other attributes. It would be really helpful to have certain things only visible when I have a version of the rig that is dynamic and evolving so I could basically have features that are built solely for modifying the rig and then when I turn Autoupdate off, they simply go away  Show More

Hello everyone, why, even though there is an important tool in Maya called Quad Draw, it is not possible to snap it to the vertex object reference when drawing a vertex? Please help. Thanks to all.Shahriar   Show More