Which of the following is a common pitfall when exporting 3D assets from external tools to Unity?

• A. Scale/units mismatch
• B. Lighting settings not exported
• C. Animation import settings can cause incorrect animation timing or root motion issues if not configured properly
• D. Sprite atlas reconfiguration

Answer: (C)

The key idea here is how animation data is brought into Unity and how Unity interprets it. When you export 3D animations from another tool, the timing and movement Unity plays back depend on the export/import settings that control how keyframes are sampled and how root motion is handled. If the frame rate or sampling rate in the export doesn’t match Unity’s expectations, the animation can play back faster or slower, causing timing drift. Likewise, root motion—the movement of the model’s root bone—needs to be exported in a way Unity can read and enabled on import; if it isn’t baked into the animation data or if Root Motion is not enabled/configured, the character may appear to move incorrectly or not at all, even if the poses are right. These configuration details directly shape how the animation behaves once it hits Unity, making them a common pitfall. The other options involve lighting exports or 2D sprite atlas work, which don’t influence how 3D animation timing and root motion are interpreted in Unity.