Getting Started with Unreal Engine

Unreal Engine is not a single file you download and run - it is delivered through the Epic Games Launcher, a free application that manages the engine, its versions, samples, the Marketplace (now Fab) and your library. So the first move is to make a free Epic Games account at unrealengine.com, download the launcher for Windows or macOS, and sign in. Everything after that lives inside it.

Inside the launcher, open the Unreal Engine section and find the Library tab. Click the plus to add an engine version and install it. Be warned: this is a serious download - the engine plus its core content runs roughly 15 to 30 GB, and it wants a fast connection and a good chunk of free disk. Put it on an SSD if you can; the engine reads assets constantly and a mechanical drive will make everything feel sluggish. Once it finishes, you have the full engine - editor, renderer, Lumen, Nanite, the Sequencer, Blueprints, VR support - all of it, free.

A word on cost, because it matters and gets muddled. Unreal Engine is free to download and free to learn, and free to use for the overwhelming majority of architectural visualization. Epic's royalty model is aimed at commercial games past a revenue threshold, not at archviz stills, films or client walkthroughs. For anything in this course you will pay nothing. As always, if you are doing something unusual and commercial, check Epic's current licensing for your exact case - but for learning and for normal practice, it is genuinely free.

While the engine downloads, it is worth knowing what else lives in that launcher, because you will return to it constantly. The Library tab holds every engine version you install and every project you create - your home base. A Samples and learning area offers free example projects, some of them archviz scenes you can pull apart to see how a professional set up lighting and materials. Fab (Epic's asset marketplace, which absorbed the old Marketplace and Quixel Megascans) is where you download free and paid meshes, materials and whole environments. And Twinmotion, the friendlier real-time sibling built on Unreal, installs from the same launcher. You do not need any of this on day one, but the launcher is the hub the whole toolchain hangs off, so a few minutes clicking through its tabs while UE5 downloads is time well spent.

The launcher will offer you several engine versions, and newcomers freeze here. The honest rule is simple: for learning, install the latest stable Unreal Engine 5 release the launcher recommends. UE5 is the generation that brought Lumen (real-time global illumination) and Nanite (virtualized geometry) - the two features that made real-time archviz look the way it now does - so you want to be on 5, not the older 4.x line.

Why not always the newest preview? Because Epic ships Preview and Early Access builds ahead of the stable release, and those can be buggy and incompatible with plugins. For a course, and for real work, take the newest number that is marked stable rather than preview. Multiple versions can sit side by side in the launcher - a real studio often keeps a project pinned to the version it started on, because opening a project in a newer engine upgrades its files and there is no clean going back. So the discipline is: learn on the latest stable 5.x, and once a real project begins, decide its version deliberately and stick to it.

One practical note for archviz specifically: much of the best free learning content, the Datasmith importers you will use in Module 2, and the Twinmotion content library all track recent UE5 versions closely. Staying current keeps those doors open. You do not need to chase every point release, but starting a course on a two-year-old engine only invites friction.

When you finally click New Project, Unreal asks what kind of thing you are making, and offers templates grouped into categories - Games, Film / Video & Live Events, Architecture / Engineering & Construction, Automotive, and so on. A template is just a pre-configured starting point: some settings, sometimes a sample level, sometimes helper Blueprints. Pick the Architecture, Engineering and Construction category if it is offered, or simply start from Blank - both are completely valid, and Blank keeps things uncluttered while you learn.

Two choices on that New Project screen matter. First, tick Starter Content (or add the Starter Content pack): it gives you a small library of ready materials, props and simple meshes - a fast way to have something to look at and light without modelling anything yet. Second, note the Blueprint vs C++ toggle: choose Blueprint. Blueprints are Unreal's visual, node-based scripting (Module 7), and no archviz project needs C++ to begin. You can always add code later; you almost never will.

Give the project a sensible name and a folder you can find again - a project is a whole folder on disk, not one file - and create it. The engine grinds for a moment compiling shaders, and then the editor opens with your level on screen. That is the milestone this lesson exists to reach: you are now inside Unreal, looking at a real-time 3D world, with everything the rest of the course needs already installed.

Unreal is demanding, and the most common beginner worry is hardware. Here is a straight answer. The single most important part is the GPU (graphics card): real-time rendering happens on it, and you want a dedicated card, not integrated graphics. To learn, a card with around 6 GB of video memory copes; to be comfortable on real archviz scenes, aim for 8-12 GB or more. For system RAM, treat 16 GB as a floor and 32 GB as the target once scenes get heavy with imported geometry and textures. A modern quad-core (or better) CPU and, again, an SSD round it out.

If your machine sits under those numbers, you are not locked out - you learn at lower quality settings. Unreal lets you dial back screen percentage, shadow and Lumen quality, and viewport resolution so the editor stays responsive while you learn the moves; you simply turn the beauty back up on capable hardware or at final render. Module 9 is entirely about keeping scenes running well on the hardware you actually have.

VR is the one place hardware gets stricter. A comfortable VR experience wants to hold about 90 frames per second with no dropped frames, which needs genuine headroom above what a smooth desktop view requires - because in VR the engine renders the scene twice, once for each eye, and any stutter is felt in the body as discomfort rather than merely seen. So the VR modules assume a stronger GPU. You do not need any of this to start; you need it before Module 8. For now, if you have a modern dedicated GPU and 16 GB of RAM, open the editor and begin.

One last reassurance for anyone on borderline hardware: the first shader compile when you open a new project, and the occasional recompile after big changes, are the heaviest moments you will hit - the machine may fall quiet and busy for a few minutes. That is normal and one-off, not a sign your computer cannot cope. Everyday editing is far lighter than that first grind. And if your desktop truly cannot keep up on a real project, Module 10 introduces pixel streaming and the cloud, where a powerful remote GPU does the rendering and streams the result to a modest machine or even a phone - a genuine escape hatch that keeps real-time open to you regardless of the laptop on your desk.