FAQ
Technical Questions. Direct Answers.
Explore the most frequently asked questions in the 3D animation domain, specifically related to our Autodesk Maya animation services.
Why build a studio around a single piece of software?
Because mastery of one tool produces better results than competence in many. Maya’s technical depth—its node architecture, simulation systems, scripting access, and rendering integrations—rewards deep specialization. Our team’s focus on Maya exclusively means we encounter, solve, and learn
from every technical problem this software presents. That accumulated knowledge is directly visible in production quality.
What version of Maya do you work in?
We maintain current version licenses alongside three previous releases. Most production work runs in the current version, but we can work within older version constraints when pipeline compatibility requires it. Version requirements are confirmed during technical consultation.
Can you import our CAD files into Maya for product animation?
Yes. We handle CAD import from common formats including STEP, IGES, OBJ, FBX, and application-specific formats where converters are available. Post-import, we reconstruct geometry for production-quality rendering and animation, which typically involves retopology to appropriate polygon structures.
What's the difference between your rigging and what a general 3D animator would produce?
A general 3D animator might produce a functional rig—one that can produce animation output. Our rigging is built to production standards: clean deformation through the full pose range, corrective shapes addressing known problem areas, space-switching for animator flexibility, and documentation describing the rig’s architecture. The difference becomes apparent in production, where poorly-built rigs create constant interruptions.
Can you work with an existing Maya rig that has problems?
Yes, and we’ve done this frequently. Rig troubleshooting and optimization is one of our technical consulting service areas. We assess the existing rig, document problems and their causes, and either repair the existing system or recommend rebuilding specific components.
What rendering engines do you use with Maya?
Primarily Arnold, which ships with Maya and represents the production standard for most applications. We also have production experience with V-Ray and RenderMan. Render engine selection is determined by project requirements and any downstream compatibility considerations.
Do you deliver source files?
Yes. Maya scene files, texture files, and associated assets are delivered per contract specifications. We can deliver clean, documented scene files suitable for use by other production teams. Source file delivery is a contract item—confirm requirements during scoping.
Can you develop custom Maya tools for our pipeline?
Yes. Python-based Maya tool development is part of our technical consulting service. Custom tools for workflow automation, asset validation, batch processing, or specialized export requirements are scoped on a project basis.
What is your position on Blender or Cinema 4D for projects similar to your work?
Both are capable applications appropriate for many use cases. Our position is not that they are inferior—it is that deep Maya specialization serves our clients better than medium proficiency across multiple packages. If a client’s existing pipeline is built on Blender or Cinema 4D, we are transparent about the fact that our specialist advantage diminishes in that context.
How do you handle scientifically or technically sensitive content?
Scientific and engineering content goes through accuracy review protocols. For medical animation, this involves cross-referencing published anatomical reference and, where scope warrants, engagement with clinical consultants. For technical product animation, accuracy is validated against client-supplied engineering documentation. Deliverables are not finalized until accuracy review is complete.
Technical question not covered here?