City Sample

The City Sample project is a playground where designers and developers alike can explore how various new and improved systems are brought together to create expansive and engaging environments. This sample is built using the same assets and design techniques used in The Matrix Awakens: An Unreal Engine 5 Experience technical demo released on PlayStation 5 and Xbox Series S|X hardware.

The new and improved features of Unreal Engine 5 enable you to build large, highly-detailed worlds that are brought to life with Mass AI and fully dynamic lighting. The city is designed and built using procedural generation using the Rules Processor.

The following features are used in this sample project:

• World Partition works in conjunction with One File Per Actor to improve level streaming and editor workflow efficiency.
• Nanite enables the use of high-fidelity virtualized micropolygon geometry.
• Lumen generates dynamic global illumination and reflections using Hardware Ray Tracing.
• The Virtual Shadow Maps system provides consistent, high resolution shadowing for the city.
• Mass AI manages the behavior and visualization of traffic and crowds based on the MetaHuman library.
• Chaos physics drives the vehicle and the destruction systems.
• The MetaSounds system fills the city with urban sounds.
• Niagara is used for particle systems.
• And more!

Accessing the City Sample Project

You can download the City Sample from the Samples tab of the Epic Games Launcher or from the Unreal Engine Marketplace.

Recommended System Specifications

The City Sample is a graphically intensive project that requires a powerful video card and system to run at a stable framerate. It is recommended to install the project on a solid state drive (SSD), Nanite and Virtual Shadow Maps depend on fast speeds for the best possible performance.

• Windows 10 with support for DirectX 12
• 12-core CPU at 3.4 GHz
• 64 GB of System RAM
• GeForce RTX-2080 / AMD Radeon 6000 or higher
• At least 8 GB of VRAM

This sample project requires that your machine have up-to-date graphics drivers and DirectX 12. Nanite and Virtual Shadow Maps require DirectX 12.

On lower spec systems, you can adjust the viewport screen percentage setting to get better performance by reducing the resolution of the Level Editor viewport. You can set this in the Viewport Options located in the upper-left corner of the editor viewport using the Screen Percentage slider.

Navigating the City Sample Project

When you open City Sample, you are greeted by the Startup map that provides some on-screen information for using this sample project and its recommended system requirements. The project includes two maps: a big city and a small city. Select one of these maps to open from the Content Browser in the Content > Map folder.

• The Big City (Big_City_LLV) map is the same one generated for The Matrix Awakens technical demo. This particular map is resource intensive and may not perform well on machines with lower than recommended specifications. It's roughly 4 kilometers by 4 kilometers in size.
• The Small City (Small_City_LVL) is a smaller city generated using the same assets and configurations as the larger one. It is designed to showcase all of the rendering, physics, artificial intelligence, sounds, and gameplay features as the larger city.

The City Sample is a showcase for developing and designing worlds using World Partition and Data Layers. Unlike Unreal Engine 4, there are no sub-Levels that would traditionally be used to load in objects. Instead, World Partition loads them on-demand, and breaks up the scene into separate, editable parts.

When you load either city level, you'll find the World Partition window is docked on the right side of the editor viewport, and displays a simplified map of the world.

Part of the World Partition tools is the Data Layers Outliner that provides a listing of data layers that contain objects that make up the scene. The Data Layers Outliner can be opened from the main menu under Window > World Partition > Data Layers Outliner.

The Data Layers can be disabled as-needed from this window. Use the Visibility (eye) icon next to a listed layer to stop it from being rendered, or, to disable that layer completely, use the checkbox.

When a Data Layer is selected, the properties are displayed in the bottom portion of the window.

When opening the Small City for the first time, you'll notice that it's ready to go and all assets are loaded. However, when opening Big City, none of the cells are loaded. You'll want to use the World Partition window in the editor to do that. Right-click on any single cell, or use the mouse to left-click and drag to select multiple cells before right-clicking. Then, choose Load Selected Cells.

You can quickly navigate the map by double-clicking on any cell in the World Partition window to move the camera to that location on the map.

City Sample In-Game Controls

The City Sample is a playable experience where players walk, drive, and fly around the city. You can use a keyboard and mouse or gamepad. Below are the controls for each.

Walking Controls

Driving Controls

Flying Controls

Menu Navigation Controls

Photo Mode Controls

City Sample In-Game Menu Options

After opening the in-game Menu, a user interface will appear in the bottom right corner of the screen. It includes options to change the lighting, the crowd and traffic densities, and enable visualization options for features like Nanite. It also includes a dedicated photography mode with common camera features like exposure, aperture, and depth of field settings.

You can navigate the menus using the keyboards Left / Right Bracket keys or if you're using a controller, use the Left / Right Bumpers. The following in-game menus are available.

Photo Mode Menu

The Photo Mode menu contains Camera and Focus settings to configure exposure, aperture, and focus.

World Settings Menu

The World Settings menu contains various settings that affect lighting, density of crowd, traffic, and parked vehicles, and various visualization options.

Controller Settings Menu

The Controller Settings menu displays the controller button mappings for walking, driving, drone, and photo modes. The menu also contains settings for camera control with look sensitivity and inverting the vertical axis.

Changes to these settings also affect Keyboard and Mouse.

High-End Visuals

The City Sample demonstrates Unreal Engine 5's high-end visuals for building large open worlds.

The City Sample requires DirectX 12 for its high-end visuals. Some features work in a limited capacity or not at all with systems that don't meet the Recommended System Specifications of this project.

Lumen Global Illumination and Reflections

Lumen is used to provide dynamic global illumination and reflections across the city. Lumen provides dynamic, photorealistic lighting for scenes with many areas being indirectly lit. It adapts to changes in direct lighting and geometry, combining new and old techniques to achieve high-quality results within real-time budgets.

Lumen is built with the next-generation consoles and high-end PCs in mind.

The City Sample uses Hardware Ray Tracing, which supports a larger range of geometry types such as skinned meshes. Hardware Ray Tracing also scales up better to higher qualities since it intersects against the actual triangles of geometry and has the option to evaluate lighting at the ray hit instead of the lower quality surface cache.

For Static Meshes using Nanite, Hardware Ray Tracing can only operate on the Fallback Mesh generated from Nanite's Fallback Triangle Percent in the Static Mesh Editor. Screen Traces are used to cover the mismatch between the full triangle mesh rendered by Nanite and the fallback mesh being ray traced by Lumen.

Lumen works with all movable light sources, including emissive materials as light sources. Skylighting uses Lumen's Final Gather for sky shadowing, which allows for indoor areas to be much darker than outdoor areas, and that helps bring out lightly colored surfaces that reflect more light. The City Sample is being lit by only Directional Light, Sky Light, and Emissive Materials from surfaces.

While you explore the city in-game, use the menu to access the World Settings where you can adjust the Sun Rotation. Or, while working in the editor, you can use the keyboard shortcut Right Ctrl + L and drag your mouse to move the Directional Light around.

For more information and details about how it works, see Lumen Global Illumination and Reflections and Lumen Technical Details.

Nanite Virtualized Geometry

Nanite virtualized geometry is used on all of the Static Meshes in the City Sample, and none make use of traditional levels of detail. Nanite renders pixel scale detail and handles high object counts by intelligently doing work on only the detail that can be perceived, and no more. It does for geometry what Virtual Texturing does for texture detail.

Nanite's internal mesh format and rendering technology means that its representation changes dynamically as you move through the world, updating the level of detail on the fly and culling parts that aren't rendered on screen. Objects closer to the player camera receive more detail, while further objects receive less, all the while keeping on screen detail uniform.

The City Sample is made up of billions of polygons from tens of thousands of objects placed throughout the world. Nanite makes it possible to use film-quality assets in real-time with little to no additional setup other than enabling Nanite on the Static Mesh. It's even possible to drop a high-polygon ZBrush sculpt directly in game.

Use any one of the visualization modes that Nanite offers to see how it renders the scene. You can select from the list of visualization using the View Modes menu under Nanite Visualization rollout menu.

Nanite's Overview visualization mode.

For more information about how to use and configure Nanite for your own projects, see the Nanite Virtualized Geometry documentation.

Temporal Super Resolution

The geometric detail and fidelity required for large, open worlds with thousands to millions of instances totaling billions of polygons have increased the demands of games developed for next-generation consoles and high-end PCs. That level of fidelity can mean that games can consume a significant amount of their performance budgets before including rendering a frame at native 4K resolution.

Temporal Super Resolution (TSR) is an anti-aliasing method built to meet the fidelity demands of large, densely populated worlds. It uses a platform-agnostic temporal upscaling algorithm by taking a lower input resolution and outputting rendered frames at quality near 4K resolution. This means that you can increase performance without rendering native 4K but still achieve quality that rivals 4K from rendered lowerer resolutions.

In the comparison below, you can see the quality and performance differences between captured frames rendered at native 4K and one rendered at 1080p that has been upscaled to 4K. Temporal Super Resolution makes it possible to achieve image quality near native 4K resolutions while reducing GPU frame time by nearly half in this shot from City Sample.

You can right-click and save each of the images in the comparison slider at their full-resolution to inspect the quality similarities.

Virtual Shadow Maps

Virtual Shadow Maps (VSM) is Unreal Engine 5's new shadow mapping method used to deliver consistent, high-resolution shadowing that works with film-quality assets and large, dynamically lit open worlds that use Nanite, Lumen, and World Partition features.

Traditional dynamic shadowing techniques have often been limited to small and medium-sized worlds, forcing designers and artists to sacrifice quality for performance. By contrast, Virtual Shadow Maps offer a single unified shadowing method that automatically applies quality where it is needed most. Shadows can now have consistent quality for small and large objects over greater distances — with realistic soft penumbra and contact hardening.

In the comparison below looking down on the cityscape, you can see the quality and consistency differences that Virtual Shadows have over Cascaded Shadow Maps. With Virtual Shadow Maps, the entirety of the city is shadowed in a consistent way from large to small detail. Small parts of the building, like the spires and equipment on the rooftops are captured in fine detail, even the cars and larger objects on the ground in the distances have shadows.

Compare that with Cascaded Shadow Maps where you must decide where in the scene you want to have that detail. Shadows maps are not well-suited for high quality detail over large areas without incurring significant performance cost. Note how shadows in the distance are not sharp and shadowing on the ground appears to just shade everything rather than individual objects.

See the Virtual Shadow Maps documentation to learn more about how to use and configure it for your own projects.

Post Processing Local Exposure

Local Exposure is a new technique developed for Unreal Engine 5 that automatically applies local adjustments to exposure — within artist-controlled parameters — to preserve both highlight and shadow detail, on top of the existing global exposure system. It's not uncommon to have scenes with challenging high dynamic ranges using dynamic lighting in which applying a single global exposure adjustment is simply not enough to avoid having blown out highlights and completely dark shadows.

In games with a dynamic time-of-day system or like City Sample where you can change the lighting dynamically, scenes can easily be under or over-exposed in parts of the rendered image. Take for example the scene below, the sun lit area is very bright and the area under the bridge, without using Local Exposure adjustments, is very shadowed. Local Exposure helps achieve more consistent results when carefully crafted lighting per-scene is not feasible, like in City Sample where players can explore the environment at will.

Procedurally Generated and Populated City

The City in the City Sample project has been designed and created with procedural generation using SideFX's Houdini software extensively to build all aspects of the city, from the shape of the city island to all the parts in between for the roads and highway, buildings, sidewalks, street furniture, and more. The "generation" of the city happens only inside Houdini using custom tools and inputs provided by the user.

The result — a huge point cloud — is exported from Houdini and imported into Unreal Engine 5 where the Rule Processor — an Unreal Engine tool developed for this project — converts the point clouds into thousands of instances.

When Epic games developed The Matrix Awakens, it was known that the project would be an open world city that would need to be fully detailed and very large. This project is using many new features of Unreal Engine 5 and at the time of its development, it was known that many other departments would be creating content and they would need to be able to simultaneously work together. The relatively small size of the environment team and the amount of detail being targeted for the project meant two things: Nanite would remove typical polygon budget limits, and modular assets would be needed that could be instanced thousands of times across the world.

Houdini is used to handle all the upfront work of generating the city shape, the road networks, connecting freeway system, building placement and provides a ton of metadata that can be used in Unreal Engine 5 to procedurally generate the final city. Using these tools in Houdini enabled an infinite number of different cities to be generated in a short period of time by the designers.

The generated city data contains all sorts of metadata that can be used by other tools in the Unreal Engine 5, including the Artificial Intelligence system that drives the traffic and crowd simulations. Buildings are constructed from a volume. The building generator uses a shape grammar language to style the building volume. Each different building style has a different set of rules. A given volume can also be split into two different styles: one for the bottom of the building and one for the remaining top section.

The City Sample project includes the source files needed to procedurally generate your own city using Houdini and Houdini Engine. You will need a license from SideFX in order to use the City Building Generator asset in the engine with Houdini. The Houdini source files are located in the CitySample root folder and are named CitySample_HoudiniFiles.zip.

The City Sample was developed using the following versions:

• Houdini: 18.5.532
• Houdini Engine: 3.5.2

Guided walk throughs for using these files to generate your own city with roads and freeway network will follow in the near future.

Houdini uses a node graph that flows from top to bottom. Each node is a program that executes a task on its input and outputs the result to be passed to other nodes, just like a material graph in Unreal Engine. The main city is built in stages that follow this structure:

1. City Layout
2. Roads
3. Freeway
4. Lots and Sidewalks
5. Traffic, Buildings and Ground
6. Street Furniture, Decals and Audio

Parts are built in a dependency order such that the Freeway is dependent on the Road network, and building placement requires the Freeway to be built to avoid placing buildings on top of it.

In order to build the city and support all the procedurally generated instances that make up the world, Nanite needed to be used as much as possible. It meant that a mega mesh could be built and needed to use instances to do so. Each building in the city is made up of hundreds of instances, and all props on the street, such as furniture, decals, and even trash are using Nanite. Very little custom geometry is used in the city, which ensures that the project's memory usage stays within the set budget.

However, it was inevitable that some amount of custom geometry would be required. Custom meshes are used for collisions, the freeway deck, road decals, and custom roofs for non-rectangular buildings.

Collaboratively Constructing Large Worlds

Unreal Engine 5 makes it easier to work collaboratively within your projects to manage and edit your assets and scene.

One File Per Actor

The Entire world in City Sample uses the One File Per Actor (OFPA) system. It writes a separate file for each unique instance of an Actor placed within the Level rather than writing its data into a single map file.

For developers working in the Level Editor, nothing about your workflow has changed. You can still edit a Level by opening a single map file and making your changes. However, for those who work collaboratively using a version control system, the underlying system now tracks each Actor as a separate file, meaning that designers and artists can edit different objects and layers of the same Level without encountering conflicts when committing changes.

To learn more about setting up and using this feature in your own projects, see One File Per Actor.

World Partition

Developing games with large, open worlds in mind requires dividing the map into many smaller sections that can be loaded and unloaded as the map is traversed. Loading a multi-kilometer area all at once and having it populated with objects isn't always possible. Development tools in the past have required developers to manually divide their Levels into sublevels and carefully manage when they are streamed in and out. Viewing sections of the world in context with each other could often be difficult.

The World Partition system solves this problem and simplifies the process as it automatically divides objects in the level into cells based on their grid position. The cells manage the content within them and adjust accordingly as objects are added and removed so that you never need to manually manage assets. During gameplay, World Partition automatically loads and unloads cells as you move through the world.

The Level Editor with part of the Big City loaded using World Partition.

To learn more about setting up and using this system in your own open world projects, see World Partition.

Data Layers

Where the World Partition system divides the level into cells that can be loaded and unloaded at will, Data Layers are a system within World Partition used for organizing objects into layers that can be loaded and unloaded as needed. Data Layers replace the older Layers system found in Unreal Engine 4 that required a lot of manual curation of content to manage.

The City Sample makes use of Data Layers by organizing them into different sets of objects found in the world, such as procedural ones, rooftop props, freeway, and so on. The Data Layers Outliner contains a list of all layers that contain objects found in the scene. From there, you can add, remove, or set visibility of objects using these layers.

For more information about setting up and using layers to organize objects in your scenes, see World Partition - Data Layers.

Simulating Real-World Systems

MetaHumans

The City Sample is populated with thousands of unique digital human characters adapted from a subset of MetaHumans and accessories. The MetaHuman characters are generated using MetaHuman Creator. MetaHuman Creator enables you to generate many diverse and unique photorealistic characters with consistent quality.

A crowd of generated MetaHuman characters used in City Sample and The Matrix Awakens.

The MetaHuman Creator makes it possible to design and develop film-quality characters that can be used for playable and non-playable characters (NPCs). For example, you can see in the images below that the background NPCs are consistent in quality to the playable hero character IO.

(Left to Right) City Samples playable hero character IO, Male Character, and Female Character.

MetaHuman characters come fully rigged and ready to animate. They also include their own levels of detail to balance quality with performance, making it possible to fill the city with animated film-quality characters.

City street crossing with many unique high quality characters.

Using Drone mode while in-game, you can see hundreds of crowd characters. The closest ones are fully rigged and animated MetaHuman characters, and the more distant ones are custom generated, vertex-animated Static Meshes generated from the MetaHumans.

City Sample sidewalks populated with MetaHuman characters using the Mass AI Crowd System.

To start creating your own film-quality digital humans, start using the MetaHuman Creator today. To learn more about the MetaHuman creator and how you can use MetaHumans in your own Unreal Engine 5 projects, see visit MetaHuman documentation.

Artificial Intelligence System

The Artificial Intelligence features of Unreal Engine 5 bring the city and world around it to life. Many of these features are new to the engine and are considered experimental at this time. You can dive into the City Sample and explore how they work for this project.

For more information about these features developed for Unreal Engine 5 and used in the City Sample, see the Artificial Intelligence documentation.

MassEntity

MassEntity provides a framework for data-oriented calculations that can be used in places where performance is key — including the simulation of thousands of AI agents in the scene, but not exclusive to the AI domain. It also ensures entities inside the world are persistent. This system is used for both the Traffic and Crowd systems in City Sample.

The Mass Spawner is an entry point to bring Mass Entities into the world. The Mass Spawner dictates two things: what type of entity is spawned and where it is spawned. The City Sample uses multiple spawners, one each for crowds, intersections, traffic, and parked vehicles.

When you select one of the Mass Spawner Actors placed in the level, the Details panel contains information about how the entities are used. The Entity Type (1) specifies what type of entity is being spawned and the Spawn Data Generators (2) specifies where it will be spawned in the world.

When specifying what should be spawned by the Mass Spawner, you should make a new asset type called the Mass Entity Definition. It dictates Traits for that entity being spawned, such as visuals, level of detail, behaviors and more.

A new Mass Entity Definition Data Asset type is used by the Mass Spawner to specify what should be spawned. This data asset dictates Traits about entities being spawned, such as their behavior, visuals, level of detail, and more.

When deciding where to spawn entities, distribution along a ZoneGraph (see next section) provided through the procedural data from Houdini is used to generate spawn points along the ZoneGraph for the Crowd and Traffic Systems to use.

Generated data used for choosing where to spawn Crowd and Traffic entities in the city.

For parked vehicles using the spawner, a point cloud of locations is generated along city streets from the procedural data.

Point cloud locations along city streets used for spawned parked vehicles.

The Mass Spawner supports many distribution possibilities for entities in the world. The example below is a visualization of the Traffic and Crowd Systems spawned throughout the world. Green represents driving vehicles, Blue are parked vehicles, and White are crowds.

Learn more about this feature by visiting Mass Entity in the Unreal Engine 5 documentation.

ZoneGraph

The ZoneGraph is a lightweight design-driven flow for AI that follows a point-by-point corridor structure. It can store meaningful tags (static and dynamic) that can be leveraged for AI behaviors.

The Zone Shape component can be added to the world from the Place Actors panel. See the Big City level's World Outliner and look for the Zone Shapes folder to see how these are being used.

StateTree

StateTree is a new generic state machine with an intuitive user interface shown in a decision tree structure. The StatTree dictates the behavior of Crowds. These StateTree assets are linked directly in the Mass Entity Definition data asset of the Crowd.

You can find these StateTree assets specified in the Mass Entity Definition data asset of Crowds. The Traffic System does not run on StateTree behavior. For example, see the data asset named CrowdStateTree in the Content/AI folder.

Learn more about this feature by visiting StateTree in the Unreal Engine 5 documentation.

Smart Objects

Smart Objects are a collection of Actors placed in a level that the AI agents and players can interact with.The system is configurable and adds an unprecedented level of interactivity to your scene.

These did not ship as part of the developed city, but you can explore them on your own in the MassCrowd test map included with the sample project.

Learn more about this feature by visiting Smart Objects in the Unreal Engine 5 documentation.

Chaos Vehicles

Vehicles in the City Sample are driven by the Chaos Vehicles System. This physics-based system enables you to set up and configure vehicles for different styles of gameplay like an arcade racer or something that provides more realistic handling.

The City Sample also allows you to drive a variety of four-wheeled vehicles, each with their own physics configuration for handling.

The Chaos Vehicle system also supports a robust deformation system using Control Rig to create unique deformations for each vehicle.

For more information about setting up and using vehicles in Unreal Engine 5, see Chaos Vehicles.

Tuning Vehicle Handling

Each vehicle Blueprint contains a Vehicle Movement Component that defines the physical and mechanical properties of the vehicle, including its engine torque, transmissions, gearing, mass, and center of mass. The Vehicle Movement Component also has an array of data-only Wheel Blueprints for the front and rear wheels. Wheel Blueprints control many of the vehicle's handling and braking properties with settings for tire friction, suspension, braking torque and more.

Vehicle data Blueprints for each vehicle are located in the Content/Vehicles/[Vehicle_Name] folder. For example, Content/Vehicle/vehCar_vehicle02.

The drivable vehicle Blueprints end with "_Sandbox" in their name, like BP_vehCar_vehicle02_Sandbox. These cars can be dropped in a level and are drivable.

Dynamic Vehicle Deformation

The vehicles in City Sample make use of Control Rig with the Chaos Vehicle system to apply unique deformations to each vehicle. This means that each crash is achieved dynamically by utilizing the vehicle's driving dynamics. Collisions are detected using several physics bodies placed around the vehicle's body, and constraint plasticity provides the ability for physics constraints to permanently deform after passing a specified threshold.

The vehicle Control Rig contains movable constraints that are locked along a single axis. As they are moved along that axis, they will deform part of the car's body. In the City Sample, a single Control Rig is used for all drivable vehicles to apply dynamic deformation. It is named CR_Frame_Destructible and located in the Content/Vehicle/Animation folder of the Content Browser.

Since a single Control Rig is used for all vehicles, you will want to use the Preview Mesh assignment slot to swap out different drivable vehicles to preview their deformation.

Deformation Control Rig for different drivable vehicles.

Procedural Audio and MetaSounds

In addition to all the tools that give you freedom in visuals, game mechanics, and building open worlds, Unreal Engine 5 also allows greater control over your game's audio with MetaSounds.

MetaSounds provide audio designers access to a fully featured Digital Signal Processing (DSP) graph and sample-accurate control of sound modulation and events whether you're playing pre-designed sounds or synthesizing in real-time — all of which is powered by a robust interface for reacting to game data from both code and Blueprint.

MetaSounds empower designers with production efficiency tools, like the Preset and Composition Systems that enable designers to define and reuse their MetaSound graphs. It also enables them to build a library of powerful, customized MetaSound nodes that can streamline workflows while making MetaSounds accessible across teams.

In addition to the developed MetaSounds system, the City Sample also includes experimental designs, tools, and systems for bringing procedurally generated worlds to life with sound.

Learn more about this system by visiting MetaSounds in the Unreal Engine 5 documentation.

Vehicle Audio

Drivable Vehicles

The drivable vehicles in the City Sample take advantage of an experimental tool called MotoSynth. It is a granular-based engine simulation tool that utilizes recordings of car accelerations and decelerations to granularly resynthesize acceleration and deceleration movement in real-time. Additionally, the drivable vehicles use MetaSounds for various decorative engine sounds, including idle loops, drifting noises, and RPM max-out sounds.

NPC Vehicles

The non-playable character (or NPC) vehicles are entirely powered by MetaSounds. They take advantage of procedural audio generation features around seeded randomization. A procedurally randomized mixture of traditional pitch-blended engine loops, synthesized filtered noise, and synthesized sub-tones are dynamically modulated based on the NPC vehicle's speed.

Music Redesign

MetaSounds are a powerful design environment, allowing designers to kit-bash and reuse existing sounds and music material.The City Sample features two remix variations reusing original music stems created for the demonstration, creating brand new variations of the music including a night-mode variant that is reminiscent of club music.

City Soundscape and Procedural Audio Generation

World Audio Data System and Working With Houdini

The World Audio Data System is an experimental suite of tools and features centered around working with procedural data propagation and design. It includes a custom Processor Rule to convert Houdini point cloud metadata and bake it down into a Soundscape ColorPoint Spatial Hashmap, and then distributing the cached hashmap data to individual Actors designed to stream in and out with World Partition spread across the 16 square-kilometer Big City.

These World Audio Data Actors contain Colorpoint caches and take advantage of World Partition Streaming to maintain a low memory footprint.

Soundscape Design

Most of the ambient sound around the city is controlled by Soundscape, an experimental state-based procedural ambient sound system. Soundscape enables designers to define spawning behavior for sounds around the Listener, including conditional spawning behavior based on ColorPoint metadata. Most of the sound that spawn in the City Sample depends on ColorPoint data cached and loaded dynamically through the World Audio Data System. This allows designers to designate which types of sounds are allowed to spawn based on spatial metadata, such as ambient highway sounds around the freeway, ambient traffic noises on large streets, and so on.

In addition to ColorPoint data, Soundscape also listens for dynamic ColorPoint data being fed to Soundscape through a Mass AI processor to keep track of the location of idling MetaHuman and NPC vehicles. The locations are used for ambient honking and MetaHuman shouts and other vocalizations. Soundscape plays a key role in making the city sound alive.

Creating Your Own Procedural City Guides

The City Sample project provides all the source files necessary to generate your own procedural city using Houdini and Unreal Engine 5.

In the first guide you will use Houdini to setup and generate procedural data used to create your own city with its own road network, freeway system, building zones, and more. The data exported from Houdini is then used in the second guide to populate and build your city using Unreal Engine tools and features.