The directory shuto_revival_project_beta and its associated main_layout represent the pinnacle of community-driven content within the Assetto Corsa modding ecosystem. As a 1:1 scale recreation of the Tokyo Metropolitan Expressway, the Shutoko Revival Project (SRP) has transitioned through numerous iterations, leading to the current standardized naming convention found in stable releases like version 0.9.3. Understanding the technical structure of these files is essential for any driver looking to navigate the intricate C1 Inner Loop or the high-speed Wangan stretches without encountering technical errors.

What is the Shuto Revival Project Beta Main Layout?

The folder name shuto_revival_project_beta is the unique identifier used by Assetto Corsa to recognize the SRP track mod. Within this folder, the main_layout serves as the primary configuration of the map. In the context of simulation software, a "layout" defines which parts of a larger map are accessible, where the pit boxes are located, and how the game engine calculates track boundaries and surface physics.

For the Shutoko Revival Project, the main_layout is designed as an all-encompassing free-roam environment. Unlike specific sprint or time-attack layouts that might limit a driver to a single section of the highway, the main_layout typically opens up the entire modeled network, including the Inner Circular Route (C1), the Shinjuku Route (Route 4), and the Bayshore Route (Bayside).

The Evolution from Overload Layout to Main Layout

One of the most frequent sources of confusion for returning players is the disappearance of the "Overload Layout." In earlier versions of SRP (such as v0.9.1), the most comprehensive version of the map was titled "Overload." However, starting with the stable 0.9.3 release, the development team streamlined the naming convention.

The main_layout is functionally the successor to the Overload Layout. This change was implemented to simplify server configurations and help players identify the "default" way to experience the mod. If a server browser or a guide refers to "Overload," it is almost certainly referring to an outdated version of the project, and players should ensure they have the updated main_layout files to maintain compatibility.

Technical Specifications of the Beta Main Layout

The main_layout is not merely a path; it is a complex data structure that dictates the behavior of the simulation. Understanding these specifications helps in troubleshooting performance issues and understanding the scale of the project.

Map Scale and Geometry

The track spans over 165 kilometers in its standard configuration, with some testing builds extending even further. The road width varies between 4.5 meters in tight tunnel sections to 13.5 meters on multi-lane highways. The physical mesh is high-fidelity, meaning the bumps, expansion joints, and elevation changes are modeled to reflect the actual driving conditions of Tokyo’s expressway system circa 2007.

Pit Boxes and Spawn Points

In the main_layout, pit boxes are strategically placed in parking areas (PAs) such as Shibaura, Tatsumi, and Heiwajima. The number of pit boxes is a critical factor for server administrators. In the standardized main_layout, there are typically enough slots to support large-scale multiplayer sessions, often exceeding 50+ drivers simultaneously, depending on the specific server sub-configuration.

Surface Physics

The surfaces.ini file within the main_layout/data folder defines the friction, grip levels, and acoustic properties of the asphalt. This layout uses specific surface naming to distinguish between the main highway, the concrete barriers, and the rumble strips. Modifications to this file are the most common cause of "Checksum Failed" errors when attempting to join online servers.

Correct Installation Path and Folder Structure

A significant portion of user issues stems from incorrect directory placement. Assetto Corsa is highly sensitive to folder naming conventions.

The Directory Hierarchy

To function correctly, the files must be placed in the following path: [Your Steam Library]\steamapps\common\assettocorsa\content\tracks\shuto_revival_project_beta

Inside the shuto_revival_project_beta folder, you should see:

  • main_layout (Folder containing models.ini, map.png, and ui subfolder)
  • data (Often contained within a data.acd file for the main_layout)
  • extension (Folder containing config files for Custom Shaders Patch)
  • ui (Folder containing track descriptions and images)

Common Installation Mistakes

One frequent error is nesting folders. When extracting the downloaded ZIP or 7z file, users often end up with a path like tracks/SRP_0.9.3/shuto_revival_project_beta. Assetto Corsa will not recognize the track in this case. The folder shuto_revival_project_beta must be sitting directly inside the tracks directory.

Troubleshooting the "Missing Layout" Error

The error message "Track shuto_revival_project_beta/main_layout not found" or "Missing layout" is a clear indicator of a mismatch between what the game (or server) expects and what is present on the local hard drive.

Version Mismatch

If you are trying to join a server running SRP 0.9.3 but you still have version 0.9.1 installed, the layout names will not match. Version 0.9.1 uses different internal identifiers for its parking area starts. To fix this, you must delete the old shuto_revival_project_beta folder entirely before installing the new version. Overwriting files often leaves behind "ghost" files that cause the game engine to crash.

Case Sensitivity and Naming

The folder must be named exactly shuto_revival_project_beta. Any deviation, such as adding spaces or changing "beta" to "v0.9.3", will break the link to the main_layout. The game looks for the exact string defined in the server's configuration file.

Data.acd Corruption

In some cases, the data.acd file—which contains the layout's physics and logic—becomes corrupted during download or extraction. Using Content Manager to "Verify Content" can sometimes identify this, but a clean re-installation is the most reliable fix.

Server Compatibility and Checksum Failures

The Shutoko Revival Project is primarily a multiplayer experience. To ensure fair competition and synchronized physics, servers use a "checksum" system.

How Checksums Work

When you connect to a server using the main_layout, the server compares your surfaces.ini and track geometry files against its own. If a single byte is different, you will receive a "Checksum Failed" error and be kicked back to the lobby.

Why Checksums Fail on Main Layout

  1. Manual Edits: If you attempted to "fix" a bump in the road or change the grip levels of the asphalt, your checksum will change.
  2. Custom AI Lines: Adding your own AI splines to the main_layout folder can sometimes trigger a mismatch if those files are included in the server's verification list.
  3. Incomplete Updates: If the server has updated to a newer "Public Testing Build" (PTB) and you are on the stable release, the layouts will have different checksums even if they share the name main_layout.

Resolving Checksum Issues

Always maintain a "vanilla" version of the main_layout. If you wish to experiment with modding the track, create a duplicate folder with a different name. For online play, ensure you are using the exact car pack and track version specified by the server host, usually found in their community Discord channels.

AI Traffic Integration in the Main Layout

A common question among new users is why the main_layout appears empty of other cars when playing in single-player mode.

AI Splines vs. Traffic Layouts

The standard main_layout is often optimized for player-to-player interaction. AI traffic requires "splines"—invisible lines that tell AI cars where to drive, when to change lanes, and how to react to junctions. Because the SRP map is so vast, including high-density AI traffic in the main_layout can be extremely taxing on the CPU.

Consequently, many server hosts and the SRP team provide specialized "Traffic" versions of the layout (e.g., shibaura_pa_traffic). These are separate from the main_layout and include the necessary ai folders and traffic.json files to populate the highway with civilian vehicles.

How to Enable Traffic on Main Layout

To see AI traffic in the main_layout during a single-player "Track Day" session:

  1. Ensure you have the "Traffic Tool" or "AI Flood" enabled in the Custom Shaders Patch (CSP) settings.
  2. Verify that the ai subfolder exists within the layout folder and contains a fast_lane.ai file.
  3. If no traffic appears, you may need to download the community-made traffic splines specifically designed for the 0.9.3 main_layout.

Essential Plugins for the Main Layout Experience

To run the shuto_revival_project_beta/main_layout as intended, certain plugins are non-negotiable. The mod is designed around modern extensions of the Assetto Corsa engine.

Custom Shaders Patch (CSP)

Without CSP, the main_layout will lack proper lighting, the tunnels will look flat, and the night-driving experience (which is the core of SRP) will be non-existent.

  • Version Requirement: It is highly recommended to use CSP version 0.1.79 or higher. Some features of the main_layout, like dynamic rain on the Wangan or the advanced lighting of the Tokyo Tower, require the "Preview" versions of CSP available through Patreon.
  • Track Optimizations: Within CSP settings, enable "Track Configs." This allows the game to download community-verified lighting and physics adjustments specifically for the SRP beta.

Sol or Pure

These weather scripts manage the time-of-day transitions and atmospheric effects. Driving on the main_layout at 3:00 AM with the orange sodium lights reflecting off the asphalt is the intended way to experience the mod. Pure is currently the gold standard for high-fidelity visuals on this specific map.

Content Manager (CM)

While not a plugin in the traditional sense, CM is the essential launcher for managing SRP. It allows you to select the main_layout, choose your starting point (e.g., Tatsumi PA instead of Shibaura PA), and manage the complex car packs required for SRP servers.

Optimization for Performance

Given the 1:1 scale and high level of detail, the main_layout can be demanding on hardware, especially in VR or triple-screen setups.

Level of Detail (LOD) Settings

The SRP developers utilize an aggressive LOD system. Objects far away are replaced with low-polygon versions. If you notice "popping" of buildings or signs, you can adjust the LOD settings in the extension folder config or via the CSP "General Patch Settings."

VRAM Management

The textures for the Tokyo skyline and the highly detailed highway signs can consume significant VRAM. If you experience stuttering while driving through the Hakozaki Junction or other dense areas, consider lowering your texture resolution in the Assetto Corsa video settings.

CPU Bottlenecks

Handling dozens of players or AI cars on a map this large puts a heavy load on a single CPU core. Disabling unnecessary "Extra FX" in CSP, such as Motion Blur or high-resolution SSR (Screen Space Reflections), can help maintain a stable frame rate during peak traffic hours on the main_layout.

Navigating the Map: Key Sections of the Main Layout

The main_layout covers several distinct areas of the Tokyo expressway system. Familiarizing yourself with these will help you navigate during high-speed cruises.

  1. The C1 Inner Loop: A circular route that goes through the heart of Tokyo. It is technical, narrow, and filled with sharp curves. It is the most popular area for "touge-style" highway racing.
  2. The Wangan (Bayshore Route): A long, relatively straight stretch that runs along the coast. This is where high-horsepower cars go to test their top speeds. The main_layout includes the famous bridge sections and long undersea tunnels.
  3. The K6 (Kawasaki Route): Often used to connect the Wangan back to the inner city, providing a diverse mix of sweeping bends and industrial scenery.
  4. Parking Areas (PA): These serve as the "hubs" of the main_layout. Tatsumi PA and Shibaura PA are the most iconic meeting spots where players gather before a run.

Summary

The shuto_revival_project_beta/main_layout is the definitive way to experience the Tokyo underground racing scene in Assetto Corsa. By understanding that main_layout is the updated name for the previous "Overload" configuration, ensuring your installation path is precisely content/tracks/shuto_revival_project_beta, and maintaining clean, unedited files for server compatibility, you can avoid the majority of technical hurdles. Whether you are cruising with AI traffic or engaging in high-stakes multiplayer battles, the main_layout provides the most comprehensive and immersive representation of the Shuto Expressway ever created for a consumer racing simulator.

FAQ

Q: Why do I get a "Track Not Found" error when joining a server? A: This is usually because your folder is named incorrectly or you are missing the specific layout version the server is running. Ensure your folder is shuto_revival_project_beta and you have the 0.9.3 stable release installed.

Q: Can I use the Main Layout without Custom Shaders Patch (CSP)? A: Technically yes, but the experience will be severely degraded. You will encounter broken textures, no night lighting, and potential crashes. CSP is considered a requirement for SRP.

Q: How do I change my starting position on the Main Layout? A: In Content Manager, click on the map icon for SRP. You will see a list of "Starting Positions" such as Shibaura PA, Tatsumi PA, or Heiwajima PA. Selecting one will spawn your car in that specific parking area.

Q: Why is there no traffic in my single-player game? A: The main_layout does not always include AI traffic by default to save resources. You should look for layouts with "Traffic" in their name or use a CSP-based AI flood tool.

Q: I updated to 0.9.3, but the server still says I have the wrong version. Why? A: You may have residual files from an old version. Delete the shuto_revival_project_beta folder entirely and perform a fresh install. Do not just "merge" the folders.

Q: Where can I find the official download for the Main Layout? A: The official Shutoko Revival Project website and their Discord server are the only authorized sources for the stable and public testing builds. Always use these to avoid corrupted files or malware.