Forza Horizon 6

Forza Horizon 6 (Playground Games, 2026) is an open-world driving game set in Japan, with the map centred on Tokyo. It runs on ForzaTech. The track is named Brio in the install. Observed

All observations on the FH6 pages come from one recorded census of a Steam install of the game, which is no longer installed (about 158 GB), so the figures cannot be re-checked today. The counts are measurements over every file of the stated kind and are marked Observed; no FH6 statement is marked as proven. Observed

Where the data lives

<game folder>\media\
  Tracks\Brio\            GeoChunk0..3.minizip, ChunkMap*.dat, ChunkContentsMiniZip*.txt, bin.zip, Ribbon_00\, trackroutes\, triggerzones\
  Cars\                   one zip per car (682) and _library\ (materials, textures, shaders, wheels, tyres)
  Livery\, UI\, Stripped\ livery shapes, menu art and map tiles, string tables, the encrypted database
  ShadersDXIL.zip, Rendering.zip, Water.zip, ...   engine shaders and settings
  _library\TexturesPG\    shared engine textures

The layout is described on PGZP archives; the cars on Cars. Observed Player saves are in a platform game-save folder, not in the install (Saves and tunes). Observed

The Tokyo track

The world is one very large map (22,035 m square on the pause map) whose Tokyo city lies in the south; the Shibuya scramble crossing is around x −2,050..−850, z −5,390..−4,190. Observed It is stored as 512 m terrain cells and as placement cells of several sizes (Coordinates and cells). The map has four seasons, and the same data selects spring, summer, autumn or winter content (Seasons). Observed

The data volume of the track is on Data volume: 113,868 models, 14.4 million placements, 169,351 textures, the downtown core at 46 million triangles per 700 m box at LOD1. Observed

Pages for this game

• Archives and keys: PGZP archives, Encrypted files.
• Data model: Grub bundles, String tables.
• Geometry: Models, LODs and clusters.
• World: Placement files, Template libraries, Hand-placed instances, Coordinates and cells, Seasons.
• Materials, shaders, textures: Materials, Shader containers, Environment, Other world families, Rocks and animated props, Spline deform, Swatch textures.
• Terrain, water, decals: Terrain clusters, Far-field colour, Near-field ground, Water, Decals.
• Cars: Cars, Factory paints, Wheels and tyres, Liveries, Saves and tunes, Car materials.
• Limits: Values only the running game holds, Data volume.

What is special about this game

• FH6’s mesh record (version 1.13) breaks the published FH5 readers. The record has a material-group count, four season material ids per group, a 32-bit morph count and more fields than FH5’s. Sourced · ForzaTools
• One track in four seasons. Material ids, placement files, terrain clusters and parent materials all select by season (Seasons). Observed
• Much of the look is computed at run time from data no file holds: the near-field ground clipmap, decals’ blend state, ambient-occlusion strength, wetness. (Values only the running game holds) Observed
• The game database, settings and profile are encrypted with Arxan TransformIT; no key is public. Observed
• Placeholder textures ship in the data (saturated flat images and default maps); a decoder that takes every texture at face value will show them (Swatch textures). Observed
• Name-based guesses mislead. Water, decal and road surfaces must be classed by shader family, never by material name; some names that suggest water or foliage are metal (Materials). Observed

Which build of the game do the observations come from?

The census recorded the install’s Tokyo track but not the game’s build number. The install is gone and the figures cannot be matched to a specific update.

What is known

System	Claims	Confidence	Proven or observed
Overview	15		87%
Archives and files	101		87%
Data model	125		92%
World and streaming	317		89%
Geometry	143		94%
Materials	70		96%
Shaders	251		88%
Textures	61		90%
Lighting and sky	37		89%
Terrain	73		84%
Water	19		79%
Effects and decals	17		76%
Gameplay data	145		89%
Runtime and limits	28		93%

Computed from the engine's pages; the whole picture is on the coverage page.