What the Codex Update Is and Why It Matters
The Project Cars 2 Codex update is a foundational software change that introduces a persistent in-game notebook, called the Codex, to centralize setup notes, telemetry findings, and driving insights across career sessions. Rather than overwriting prior knowledge, it structures your learning so that data from one run can improve the next. For sim racers, this shifts progress from short-term memory to long-term recorded strategy. This guide explains how the update works, what it changes under the hood, and how you can use it to make more consistent, informed setup and driving decisions over time.
How the Codex Replaces Setup and Notes Overload
Before the Codex, drivers relied on external tools, text files, or memory to track which setup changes helped and why. The update replaces that patchwork with an in-game system that logs key setup parameters, weather conditions, tire choices, and observed performance notes tied to each session. This creates a searchable record you can refer to between stints and across career races. The goal is not to automate setup decisions, but to make it easier to correlate changes in grip, balance, and lap time with specific adjustments. Over time, this supports more deliberate practice and reduces repeated trial-and-error on the same circuit.
Session-to-Session Learning
The Codex tracks variables such as front and rear camber, toe, anti-roll bars, ride height, and suspension spring rates, then lets you annotate why a given change was made and how the car responded. When you load a saved setup, the system can surface past notes for the same circuit and weather, highlighting what worked, what didn’t, and under which conditions. This approach is especially helpful when you test multiple lines or braking zones, because you can compare lap-by-lap telemetry with written reflections. Rather than treating each session as isolated, the update encourages building a cumulative, circuit-specific knowledge base that compounds in future career runs.
Integration with Assists and Difficulty Settings
The way the Codex interacts with assists depends on your selected difficulty level. At higher realism settings, the update focuses on recording raw data and driver notes, while more accessible presets may store broader guidance, such as suggested brake points or ideal racing lines. The system does not automatically apply assists for you; instead, it preserves your chosen configuration so that repeated sessions remain comparable. If you toggle ABS or traction control between tests, the Codex logs each choice alongside lap times and observed oversteer or understeer, making it easier to isolate how each assist affects car behavior. This clarity is valuable when you refine setups or compare tire strategies across many runs.
Accessing and Using the Codex In-Game
You can open the Codex from the main menu or pause screen, depending on your UI layout, and navigate by circuit, weather conditions, and session type. Each entry summarizes setup changes, weather, tire compound, and an optional written reflection from the driver. The interface is designed for quick scanning, so you can identify, for example, that a specific anti-roll bar combination worked well in cool, dry conditions but caused understeer when the track temperature rose. From there, you can duplicate a setup, modify individual parameters, and save a new variant without losing the original record. This structure supports methodical experimentation rather than random adjustments.
Step-by-Step Workflow Example
To make practical use of the Codex, start by selecting the circuit and weather conditions for your next session. Review prior notes for that combination, focusing on which setups led to consistent lap times and which caused instability. Duplicate a previously saved setup, adjust one element at a time—such as front camber or rear toe—and record the expected hypothesis in the notes field. During the session, compare real-time feedback with your earlier observations, and after the run, log what changed and whether it moved you closer to your target lap time. By repeating this cycle, the Codex becomes a living reference that aligns your setup work with measurable outcomes.
Effect on Setup Consistency and Progression
One of the biggest benefits of the Codex update is how it supports setup consistency across a career season. Instead of rediscovering the same lessons at each event, you accumulate documented insights that highlight which adjustments worked under specific conditions. This reduces the risk of regressing to an unbalanced setup after switching tire compounds or weather presets. The update also helps you track long-term improvement by showing how your notes and lap times evolve as you learn the car and circuit. Over many sessions, this documented progression can reveal patterns, such as a tendency to oversteer on high-degradation tires or understeer after lowering ride height.
Telemetry and Observational Context
The Codex is designed to complement, not replace, external telemetry tools. While in-game graphs and replay analysis show what happened, your written notes explain why you believe it happened. For example, if telemetry shows repeated wheelspin on exit, you can link that to a suspension setting change recorded in the Codex, then test a stiffer anti-roll bar and note the result. This combination of objective data and subjective reflection makes it easier to prioritize which adjustments deserve further testing. Over time, your Codex entries should reference specific telemetry observations, creating a clear chain from observation to hypothesis to result.
Limitations, Expectations, and Best Practices
The Codex does not guarantee faster lap times or automatic setup solutions; it organizes information so you can make deliberate decisions. It works best when you treat it as a lab notebook rather than a quick fix, consistently recording details about each run. Avoid relying solely on saved setups without reviewing the underlying notes, because conditions such as track temperature and tire degradation can shift between sessions. The update also assumes you will still interpret data yourself, using telemetry, replay tools, and on-track feel to validate changes. Used thoughtfully, the Codex update supports more structured learning and long-term improvement in Project Cars 2.
Quick Comparison: Codex-Assisted Testing vs. Ad-Hoc Testing
| Testing Approach | Key Characteristics | Outcome Over Time |
|---|---|---|
| Ad-Hoc Testing | Minimal notes, frequent setup changes, hard to compare sessions | Inconsistent progress, repeated mistakes, slower learning curve |
| Codex-Assisted Testing | Recorded hypotheses, one-variable changes, session-to-session reference | More systematic improvement, clearer cause-and-effect understanding, stable progression |
Status and Compatibility Notes
The Codex update is available with the latest version of Project Cars 2 and is supported on consoles and PC where the game runs. It does not alter core physics or car models; instead, it adds a layer of documentation and organization around your racing data. Because the feature is stored in the game profile, cross-save behavior may vary depending on platform, so it is wise to confirm cloud sync settings if you play on multiple systems. Aside from these practical considerations, the update is fully backward compatible with existing career files, though earlier sessions will not automatically populate Codex entries until you revisit them under the new version.
Conclusion and Long-Term Use
For sim racers treating Project Cars 2 as a serious training tool, the Codex update transforms how you capture and apply knowledge across sessions. By recording setup choices, weather context, and reflective notes, it turns scattered observations into a coherent body of circuit-specific expertise. Used consistently, the Codex supports deliberate practice, reduces repeated errors, and makes it easier to compare the impact of individual adjustments. Whether you are tuning one race weekend or building a season-long development plan, the update gives you a structured, durable record of progress that remains useful long after the initial installation.