The Viewport & Real-Time Workflow

The core control is one you already half-know from games. Hold the right mouse button (RMB) in the viewport and it switches to fly mode: moving the mouse looks around, and while you hold it, WASD moves you - W forward, S back, A and D strafing left and right, with Q down and E up. Roll the mouse wheel while flying to change your speed, so you can dart across a site or creep through a doorway. Let go of RMB and you are back to selecting. That single combination - RMB plus WASD - is how you spend most of your hours in Unreal, and it becomes second nature within a day.

A handful of navigation moves make you fast rather than merely mobile. Select an actor and press F to frame it - the camera flies to centre it, invaluable when you lose yourself in a big scene. Hold Alt and drag the left mouse button to orbit around the selection, like turning an object in your hand. There is also a first-person, gravity-free flythrough for reviewing at human eye height. And two quality-of-life toggles: G for Game view hides the editor gizmos and icons so you see the scene exactly as a client will, and F11 goes fullscreen immersive. None of these is complicated; together they turn stumbling around into confident, purposeful movement through the design.

A small but real comfort point: fly speed is the setting beginners most often get wrong, and it makes the difference between control and nausea. Too fast and you shoot through walls and overshoot every room; too slow and crossing a site takes forever. The wheel-while-flying speed control is the fix - drop the speed to creep through a doorway or inspect a detail, raise it to travel - and you will find yourself adjusting it constantly, the way you change gear driving. Getting comfortable with variable fly speed early is what makes navigation feel like second nature rather than a fairground ride.

The viewport can show your scene through several view modes, and switching between them is a core diagnostic skill, not a gimmick. The default is Lit - the full, beautiful real-time render with Lumen lighting, materials and shadows, the way the design is meant to be seen. Unlit strips lighting away and shows only the raw material colours (albedo), which is how you check a material or a texture without light muddying your read. Wireframe shows only the edges of the geometry - the polygons themselves - which is how you inspect model density, spot messy imported meshes, and understand how heavy a scene really is. There is also Detail Lighting, which shows lighting on a neutral grey so you can judge light and shadow independently of colour.

Beyond those, Unreal offers a stack of optimization view modes you will lean on in Module 9 - Shader Complexity (a heat map of how expensive each pixel is to draw), Lightmap Density, Nanite visualizations, and more. You do not need them yet, but it is worth knowing they exist, because they turn the viewport into an instrument for understanding a scene, not just admiring it. The habit to build: when something looks wrong, change how you are looking at it. A material reading oddly? Switch to Unlit to see its true colour. A scene running slowly? Wireframe and Shader Complexity tell you where the weight is. The same live view, interrogated four ways, is one of real-time's quiet superpowers.

Flying the viewport is a designer's-eye view; Play-In-Editor (PIE) is the occupant's. Press the green Play button on the toolbar (or its shortcut) and Unreal runs the level as an experience - dropping you in at a Player Start actor with a first-person or walking view, gravity, collision, and any interactivity you have built. Now you are not floating a camera through the scheme; you are walking it at eye height, bumping into walls that stop you, climbing stairs, feeling corridor widths and ceiling heights with something close to real embodiment. Press Escape or Stop to return to editing. This is the single most persuasive thing you can do with a design early: hand someone the controls and let them be in the building.

PIE is also where the scene stops being static furniture and becomes responsive. Once you reach Blueprints in Module 7, Play is when your doors open, your lights switch, your day-night slider works and your material configurator responds - because Play runs the level's logic, not just its geometry. And PIE is the natural rehearsal for VR: the walking, collision and eye-height framing you feel in Play are exactly what the headset delivers at full presence in Module 8. For now, the move to internalise is simple and powerful - build looking down like a designer, then press Play and stand inside it like an occupant. Switching between those two vantage points, constantly and for free, is a way of testing a design that neither CAD nor offline rendering can offer.

A practical caution keeps Play honest. What you experience in PIE depends on the level having the pieces an occupant needs - a Player Start so you spawn somewhere sensible, collision on your geometry so walls actually stop you, and reasonable eye-height framing. Imported models sometimes arrive without proper collision, so you walk straight through a wall in Play; that is a fixable setting, not a broken scene, and Module 2 covers getting collision right on imported geometry. The point to hold now is that Play is a test, and like any test it only tells the truth when the setup is right - a habit of checking you spawn where you mean to and are stopped by the things that should stop you is part of using it well.

Everything above serves one shift that is easy to state and hard to overstate. In CAD and offline rendering, there is a gap between making a change and seeing its consequence - you edit, you set a camera, you render, you wait minutes or hours, you look. That latency quietly shapes behaviour: because looking is expensive, you commit to decisions on paper, you test fewer options, and you discover problems late, when they are costly to fix. Real-time collapses that gap to about sixteen milliseconds. You move a wall and the light through the room updates now; you raise a ceiling and the proportion is right there; you swap a stone and judge it instantly. The feedback loop that design actually runs on - propose, see, judge, adjust - stops being throttled by render time.

That changes the kind of designing you do. When seeing is free, you explore more - ten material studies instead of one, three ceiling heights walked in a minute - and you find problems early, while the design is still soft and cheap to change. You judge with your body: a sightline, a pinch point, a too-low soffit that a plan hides but a walk exposes immediately. And crucially, you can put a client inside that loop, letting them change options themselves and understand the design at full scale - which builds trust no static image earns. This is the payoff the whole first module has been building toward. The engine is installed, the editor is legible, the scene is organised - and now the viewport lets you move, see and judge without waiting. Master that loop, and you are no longer producing pictures of buildings; you are designing inside a live, walkable, changeable one.