Skip to content

The viewport

The viewport shows the cooked result of the node currently flagged for display. This page covers walking through your scene in first person and following a long cook.

Press P over the viewport, pick First Person in the camera view menu, or click the green Play button while you edit a Blockout, to drop into the scene as a player and walk it the way a game would. An orthographic view (Front, Top, …) switches to perspective first.

First you choose where to drop. A see-through figure the player’s size follows the surface under the cursor:

  • Gold means you can stand there. Click to drop in on that spot, facing the way the camera faces.
  • Red means you can’t: the spot is a wall, or the space is too low to fit (under a table, say). A click there does nothing.
  • P or Enter drops you straight below the camera instead, onto the first surface under it.
  • Esc cancels and leaves the camera where it was.

The camera still moves while you choose: right-drag to fly, middle-drag to pan, Alt+drag to orbit, scroll to zoom.

Once you’re in:

  • W A S D walk at 4 m/s, Shift sprints at 6 m/s, Space jumps about 1.2 m.
  • The mouse looks around with no button held. The browser hides the cursor and shows a short press Esc to show your cursor note.
  • Esc or P leaves. The normal camera picks up where you were standing.

The player is the size of Unreal’s default character: 180 cm tall, 70 cm wide, eyes at 165 cm. To check your level against a different character, set Eye height (50–300 cm; the player stands 15 cm taller) and Walk speed (50–1500 cm/s; Shift sprints at 1.5×) in the Walk section of the Camera menu at the top right of the viewport. They’re remembered between sessions, Reset puts them back, and a change applies at once, even mid-walk. You stand on every mesh you can see and on the ground grid (y = 0, or lower when your geometry reaches below it), climb steps up to 45 cm and slopes up to 45°, slide off anything steeper, and stop at walls. So a doorway that is too narrow, a step that is too tall or a ceiling that is too low shows up the moment you walk into it.

While you walk, the view looks like a game: no grid, gizmo, labels or wireframes, and a wider field of view. Any viewport editing tool you had open, such as the Blockout editor, pauses and comes back when you leave. If the geometry changes while you walk, you walk on the new geometry, and if it now overlaps you, you are lifted on top of it.

When a cook runs for more than a moment, after a file pick, a parameter change upstream of a slow node like Bake or Polyreduce, or a new display, a card slides in at the viewport’s top right and shows what the cook is doing:

  • The header says what is happening (Cooking, Sending, Drawing, Done), for how long, and how far along the graph is, such as 6 of 9 · 3 cached. Nodes already cooked with the same inputs are served from the cache and counted, not listed.
  • One row per node that cooks, in order: a check and its time when done, a gold bar and a running time while it cooks, dimmed while it waits. A node that reports its own progress shows a percentage and a filling bar.
  • A subnet lists its inner nodes under it while it cooks, and folds them away when it finishes.
  • After the nodes come Sending to viewport (with Computing tangents and its percentage on a normal-mapped mesh) and Drawing, until the result is on screen.

Click a node row to select that node and open its parameters. That is the quickest way from Bake: 102 s to Bake’s settings. Inside a subnet, a click selects the node on the level you are looking at. If you change something while a long cook is running, the card says Your latest change cooks next: the running cook finishes first, then yours starts.

Quick cooks, such as dragging a slider on a cheap node, never bring the card up. It leaves a moment after the result is drawn. Hover it to keep it open, or click × to hide it until the next cook. If a cook fails, the card stays open with the failed node in red and the error message under it.