ACU 3ds Max common mistakes
ACU 3ds Max · Understand the traps and how to avoid them.
When a tool stops responding as expected (for example, a transform gizmo disappears or selection is filtered), the candidate restarts 3ds Max or rebuilds the scene instead of checking the active state of the interface controls.
The 3ds Max interface is modal: Transform Gizmo toggles, Selection Filter, Snaps, sub-object level, and the Command Panel tab all change how clicks behave. Candidates learn tools in isolation and never build the habit of reading the current UI state, so a single stray toggle looks like a broken program.
What to do instead
Before any operation, run a fixed checklist: which Command Panel tab is active, which sub-object level is set, what the Selection Filter is, whether Snaps and the gizmo are on, and what is selected. Practice deliberately toggling each control and observing the effect so the state indicators become readable at a glance.
The candidate works in the wrong viewport or wrong coordinate system, so objects move along unexpected axes or are created on an unintended plane.
New users click into a viewport without confirming it is active, and they leave the reference coordinate system on View or Local without understanding how it changes axis directions. Perspective and orthographic viewports also behave differently for creation and transforms.
What to do instead
Confirm the active viewport by its highlighted border before acting, and consciously set the reference coordinate system (World for scene-wide alignment, Local for object-relative moves, View for screen-aligned work). Use the axis letters on the gizmo and the transform type-in fields to verify numeric values after each move.
The candidate builds a model from many separate primitives and never converts, attaches, or welds them, then discovers the mesh cannot be smoothed, subdivided, or UV-unwrapped cleanly.
Boolean-style assembly of intersecting primitives looks correct in shaded view but leaves open edges, coincident faces, and non-manifold geometry. Candidates judge the model visually and never inspect topology, so problems surface only at the rendering or unwrapping stage.
What to do instead
Decide early whether the asset needs editable-poly topology: collapse to Editable Poly, attach parts, weld coincident vertices, and check for open edges and flipped normals. Use the object's statistics and a wireframe or edged-faces display to inspect the cage before adding Smooth or Subdivision modifiers.
The candidate applies a Subdivision or TurboSmooth modifier to fix a shape, and the model collapses, shrinks away from its original silhouette, or develops pinching.
Subdivision surfaces pull toward the average of surrounding geometry, so unheld edges round off and long thin polygons crease badly. Candidates treat subdivision as a repair tool rather than a modelling decision that requires supporting loops and even quad distribution.
What to do instead
Add supporting edge loops near edges that must stay sharp, keep polygons roughly square and evenly sized, and use creasing or separate smoothing groups where appropriate. Toggle the modifier's display and render iterations to compare, and model the base cage at the level of detail the silhouette actually needs.
UVs are assigned by applying a single UVW Map projection to a complex or curved object and accepting the default result, producing stretching and seams that appear in the final texture.
Planar, cylindrical, and box projections each distort on surfaces that do not match their assumption, and candidates do not check the texture in the viewport with a checker pattern. They also unwrap at the end of the pipeline when geometry changes are still pending.
What to do instead
Apply a checker or grid map early and inspect it in the viewport, then use Unwrap UVW with deliberate seams and relaxed islands for organic or multi-part assets. Reserve simple projections for flat or single-axis objects, and re-check UVs after any geometry edit that changes the surface.
The candidate sets a material's diffuse colour or bitmap and assumes the render is wrong when the object still looks flat, or blames lighting for a material that never appears.
The relationship between material assignment, map channels, and the renderer's material type is not intuitive. Candidates also confuse viewport display of materials with the rendered result, and they assign maps to the wrong slot or forget to show the map in the viewport.
What to do instead
Verify the material is actually assigned to the selected object, that maps sit in the intended slots, and that the viewport is set to show shaded materials with maps. Render a small test frame after each material change rather than judging from the viewport alone.
The candidate adds many lights at full intensity to brighten a dark scene, and the render becomes blown out, flat, or full of harsh overlapping shadows.
Beginners compensate for poor exposure with more light instead of adjusting intensity, decay, and placement. They also mix photometric and standard lights without understanding units, and they never check where shadows fall from each light independently.
What to do instead
Start with one key light and set exposure or intensity to a correct level before adding fill and rim lights. Add lights one at a time, render after each addition, and use light attenuation and shadow settings deliberately. For photometric workflows, confirm the unit scale of the scene matches the light units.
The candidate renders a final image without ever testing render settings, and the output is noisy, missing shadows, or takes far longer than the time available.
Render settings interact: sampling, global illumination, ray depth, and output resolution all affect quality and time. Candidates leave defaults untouched, do not preview, and discover problems only when the clock is nearly out.
What to do instead
Render low-resolution, low-sample test frames throughout the session to confirm framing, lighting, and materials, then raise quality only for the final pass. Note the renderer in use and know which two or three settings most affect noise and time, and check the output resolution and file path before committing.
The candidate sets keys at the current frame without checking the time configuration or the active frame, so animation plays back too fast, too slow, or with keys in unintended places.
The scene's frame rate and the playhead position are easy to overlook, and the auto-key behaviour of the interface means any transform at any frame can create a key. Candidates then fix timing by dragging keys rather than correcting the underlying setup.
What to do instead
Set the frame rate and total frame range before animating, confirm the current frame number before every transform, and use explicit Set Key rather than relying on auto key. Scrub the timeline and open the track view or dope sheet to verify key placement and interpolation.
The candidate links or constrains objects in the wrong order, or animates a parent and child independently, producing motion that drifts, doubles up, or breaks when the hierarchy changes.
Hierarchy and constraint evaluation order determine the final transform, and candidates build relationships by clicking without checking the resulting pivot or the parent's transform at the time of linking. Offsets introduced at link time are then baked into the animation.
What to do instead
Plan the hierarchy before linking, align pivots to the intended rotation point, and link with the parent's transform in its rest state. Test by rotating the parent and observing the child, then add constraints one at a time and verify their influence and offsets before keying further motion.