Recovering a Cluttered Scene Under a Deadline
A junior artist hands you a scene file with 2,400 objects and asks why it is slow. The viewport crawls at 3 fps when orbiting. The layer manager shows 40 layers, several named 'Layer001' through 'Layer012'. The Scene Explorer is sorted by name, and the artist cannot find the three hero props. Selection is set to 'Select by Name' mode, and the artist has been clicking objects in the viewport and accidentally moving them. Autosave is enabled at 5-minute intervals, writing to the same file the artist is editing. The scene uses a single daylight system, and every object has a high-poly turbosmooth modifier. The artist needs to deliver a turntable render in two hours.
1. Diagnose the two most likely causes of the viewport slowdown and propose an ordered fix plan that does not destroy the artist's existing work.
Read the worked answer
The two dominant costs are almost certainly geometry density and display overhead from sheer object count. Every object carrying a Turbosmooth modifier multiplies polygon count at every display refresh, and 2,400 separate objects each incur per-object draw and selection overhead. A single merged high-poly mesh can render faster than thousands of small ones in many viewport configurations.
Ordered plan:
- Save a versioned copy before touching anything, and disable autosave to the working file so a 5-minute save cannot overwrite a recovery point mid-edit.
- Switch the viewport to a shaded mode with reduced display quality and set Turbosmooth's viewport iterations to 0 or 1 while keeping render iterations intact. This buys speed without changing the final output.
- Use the Scene Explorer with filters to isolate hero props, then freeze and hide everything else by layer so orbiting touches far fewer objects.
- Consolidate redundant layers and rename them by content category so the artist can navigate.
- Only then consider collapsing modifiers on background objects, keeping hero props editable.
Locking the transform on background objects prevents accidental moves while the artist works in select-by-name mode.
2. The artist wants to keep clicking in the viewport to select objects. What interface and selection settings would you change, and why?
Read the worked answer
Clicking in a crowded viewport is unreliable because overlapping geometry means the click hits whatever is frontmost, and a drag can unintentionally transform the selection. The safer workflow is name- and list-driven selection.
Recommended changes:
- Use the Scene Explorer or Select by Name as the primary selection method, filtering by name or type so the artist targets exact objects.
- Enable selection lock so a stray click does not drop the current selection, and consider locking transforms on background geometry.
- Turn on selection highlighting and set the selection bracket or outline color to something that contrasts with the scene so the current selection is obvious.
- Use named selection sets for the three hero props so they can be recalled instantly.
- If the artist must click, use region selection or window selection rather than point clicks to avoid grabbing the wrong object.
The reasoning is that in a 2,400-object scene, precision beats speed. Name-based selection removes ambiguity, and selection lock plus transform locks convert an accidental drag from a destructive edit into a no-op. That directly addresses the symptom of objects being moved by accident.