DEVELOPER FIELD GUIDE • UNREAL ENGINE 5.8
The exciting part is not that Unreal can show you a city. It is that you can inspect the rules that make one—and change them.
For a small team, “build a city” can sound like a request to spend the next year placing windows. Epic’s updated City Sample offers a more useful way into that problem: a free learning project built around procedural content generation, with roads, buildings and vegetation driven by editable systems inside Unreal Engine.
This is not a review based on running our own benchmark. It is a guide to what the sample contains, where the official documentation draws the line, and how a developer could turn an impressive download into a useful experiment.
One download, two generations of city-building
The August 27 update adds UE 5.8 PCG levels while retaining the original Houdini-built city. The new material includes a full city and a simpler example, graph references, building and road grammar assets, assemblies for features such as rooftop plazas, and vegetation content. Its central change is that the procedural construction takes place inside Unreal rather than requiring the original external generation pipeline.
That matters because the learning object is not just a finished environment. It is the relationship between an input and what appears in the scene. A designer can ask a more interesting question than “can I use this building?”: can the rules create the kind of street, silhouette or neighborhood our game needs?
Three boundaries to understand before importing anything
A generated city is not a complete simulation. Epic’s PCG documentation says the new main demo lacks the original level’s Mass AI traffic and pedestrians, and has no traffic-light system. Its basic mode lets you walk and fly, but it is not set up as the same playable experience. That distinction is easy to miss when older City Sample descriptions mention crowds and vehicles.
World Partition does not mean streaming is ready by default. The PCG demo starts with streaming disabled and generated content unpartitioned. The documentation describes additional partition, collision and streaming configuration. A world that is quick to regenerate for an artist and one that streams correctly for a player have different requirements.
The workflow has an order. The main city uses 18 interdependent graphs. Changing an early stage can rebuild later stages; Epic recommends pausing generation while editing and using available debug modes. The lesson is not “procedural work is effortless.” It is that dependencies become part of the tool you need to understand.
Try one block, not an entire metropolis
Our suggested first exercise is deliberately small: decide what one street should do for the player. A chase route, a market square and a combat arena may all use urban assets, but their sightlines, travel distances and interruptions should not be interchangeable.
- Write a testable intention. For example, create a route with a recognizable landmark, a short alternate path and enough width for the intended camera. This is an editorial example, not an included mission.
- Begin with the simpler PCG example in a separate project. Keep an unchanged copy. Identify which graph owns the specific dimension you want to alter before changing several systems at once.
- Make one controlled variation. Compare the original and changed layout. Record whether the change improved navigation, merely added visual density, or broke something downstream.
- Bring gameplay into the evaluation. Test the camera, collision and movement at player height. A beautiful overhead layout can still be an unreadable level.
- Measure before scaling. Record generation time, editor responsiveness and runtime cost on your target setup. A successful screenshot is not a performance budget.
This approach gives even a developer who never ships a city something reusable: a better understanding of how to expose meaningful controls to designers. The strongest procedural tool is not necessarily the one with the most parameters. It is the one that makes the desired variation easy and the damaging variation difficult.
MCP is optional; control should not be
Epic designed the new sample to work with its Unreal MCP workflows, but PCG can be studied without an AI model. The sample includes Experimental and Beta systems, and some need to be enabled explicitly. A free project download also does not imply that any external model service you choose is free.
The current Unreal MCP documentation labels the plugin Experimental and warns that its APIs can change. It exposes editor tools over a local connection; the documented server has no authentication layer and is not safe to expose beyond the local machine. Those are operational constraints, not details to skip because a demo makes the workflow look convenient.
For an initial experiment, we would prefer a narrowly defined request—inspect a graph or change one known parameter—followed by a human check of the resulting assets. Keep source control and review in the loop. If the person running the experiment cannot explain what changed, producing the scene faster has not necessarily made the pipeline easier to maintain.
Free to download still has a cost of adoption
Fab lists City Sample as a complete project and currently links the Standard License. Review the terms attached to the assets you acquire; do not assume “free” means public domain or unrestricted redistribution. The listing also offers links to separate buildings, vehicles and crowd packs if you do not need the whole sample.
Hardware is another reason to start small. Epic’s general City Sample guidance recommends an SSD, a 12-core CPU, 64GB RAM and a GPU with at least 8GB VRAM, including RTX 2080/Radeon 6000-class examples. That guidance describes the demanding sample as a whole; it is not a newly measured minimum for every UE 5.8 PCG exercise, or a guarantee for your workstation.
Who should make time for it? Technical artists learning procedural environments, level designers working with reusable rules, and teams evaluating an Unreal-centered worldbuilding pipeline. If you need a small bespoke scene immediately, a hand-authored layout or a smaller asset pack may be the faster route. The sample earns its download when understanding the system is part of the job.
Open the PCG implementation guide →
Sources & version notes
Checked September 13, 2026. This article separates the original City Sample from the UE 5.8 PCG update and offers an untested learning plan, not a claim of first-hand production use.
Epic’s update announcement · City Sample PCG documentation · Unreal MCP limitations and setup · General City Sample hardware guidance · Live Fab listing · Fab license page.
