Fix Save Files

📊 Division of Responsibilities

1. CRCarInfo.cs - Individual Car Tracking

Purpose: Tracks per-car data and player-specific information

1. ✅ Mileage tracking (total, session, race)

2. ✅ Speed calculations (current, average)

3. ✅ Lap timing for individual car

4. ✅ Waypoint navigation (arrow, beacon)

5. ✅ Player GUI (diagnostics, countdown messages)

6. ✅ File Creation:

· RaceData_{trackName}_{timestamp}.csv - Player's lap-by-lap data

· MileageReport_{trackName}_{timestamp}.txt - Player's mileage report

· car_mileage.json - Persistent mileage database

· race_history.json - Player's race history

1. FirstSecThird.cs - Real-Time Race Position Tracking

Purpose: Tracks all racers during the active race

·✅ Position calculations (1st, 2nd, 3rd, etc.)

·✅ Comparative race data (all cars' laps, waypoints)

·✅ Real-time sorting using Jobs System

·✅ Race results display when race ends

·✅ Best lap times tracking

·✅ File Creation: NONE (purely runtime tracking)

1. CRRaceManager.cs - Campaign & Scene Management

Purpose: Manages cross-scene race progression

1. ✅ Persistent positions across multiple tracks

2. ✅ Scene transitions and countdown coordination

3. ✅ Campaign progress (which track, who's winning overall)

4. ✅ Final standings across all races

5. ✅ File Creation:

· race_save.json - Campaign save file with positions across scenes

---

🔄 How They Work Together

During Race Start:

CRRaceManager (fires events)

↓

OnRaceStart event

↓

CRCarInfo (subscribes) → Resets lap timer, mileage

FirstSecThird (subscribes) → Starts position tracking

During Race:

CRCarInfo (each car)

→ Updates waypoints, lap times

→ Reports to FirstSecThird

↓

FirstSecThird

→ Calculates positions for ALL cars

→ Updates race manager

↓

CRRaceManager

→ Stores positions for next scene

When Player Finishes:

CRCarInfo (player)

→ Detects lap completion

→ Calls FinishRaceAndAllOtherRacers()

↓

FirstSecThird.ForceFinishAllRacers()

→ Finalizes all AI positions

→ Calls CRRaceManager.MarkRacerFinished()

↓

CRRaceManager

→ Updates campaign standings

→ Saves progress

→ Triggers scene transition

File Creation Summary:

CRCarInfo → Creates CSV/TXT after EACH race (player stats)

FirstSecThird → No files (runtime only)

CRRaceManager → Saves JSON when positions change (campaign save)

✅ Evidence They're Integrated:

1. Event System:

// CRRaceManager fires:

CRRaceManager.OnRaceStart?.Invoke();

// CRCarInfo subscribes:

CRRaceManager.OnRaceStart += OnRaceManagerRaceStart;

1. Cross-Script Communication:

// CRCarInfo talks to FirstSecThird:

FirstSecThird raceTracker = FindObjectOfType ();

firstSecThird.ForceFinishAllRacers();

// FirstSecThird talks to CRRaceManager:

raceManager.MarkRacerFinished(racerName, totalRaceTime);

1. Data Synchronization:

// CRCarInfo syncs with CRRaceManager:

private void SyncSavedDataWithCurrentScene(FirstSecThird raceTracker, ...)

{

foreach (var savedRacer in raceManager.racers) {

var matchingSceneRacer = FindMatchingFirstSecThirdRacer(...);

matchingSceneRacer.position = savedRacer.currentPosition;

}

}

🎯 Why This Architecture Makes Sense:

---

📝 Bottom Line:

No, they're not redundant! Each has a specific role:

· CRCarInfo = "What's MY car doing?"

· FirstSecThird = "Where is EVERYONE right now?"

· CRRaceManager = "How's the CAMPAIGN going?"

The files they create serve different purposes:

· CSV/TXT (CRCarInfo) = Detailed player performance analysis

· JSON (CRRaceManager) = Campaign save/load system

They communicate through events, method calls, and shared data structures (like FirstSecThird.RacerInfo and CRRaceManager.RacerData).

Recommendation: Keep this architecture! It follows good separation of concerns. However, you could add a single centralized file manager if you want to consolidate the file I/O operations for consistency.

____________________________________________________________________________________

If FirstSecThird does not save a file what is laptimes.json for?

. Saving laptimes.json (Lines ~638-675)

1. Loading laptimes.json (Lines ~677-707)

⏱️ What laptimes.json Contains

{

"bestLapTimes": [

{

"trackName": "CityRacing1",

"bestTime": 45.234

},

{

"trackName": "CityRacing2",

"bestTime": 52.891

}

],

"allTrackTimes": [

{

"trackName": "CityRacing1",

"lapTimes": [

{

"trackName": "CityRacing1",

"lapTime": 47.123,

"dateTime": "2026-01-03T19:27:18"

},

{

"trackName": "CityRacing1",

"lapTime": 45.234,

"dateTime": "2026-01-03T19:30:45"

}

]

}

]

}

🔄 When Files Are Saved

FirstSecThird saves laptimes.json:

· On OnDestroy() (line ~236) - When the script is destroyed

· After displaying race results (line ~618) - In HideResultsAfterDelay()

private void OnDestroy()

{

// Clean up native arrays when object is destroyed

CleanupJobResources();

// Save lap times to persistent storage

SaveLapTimes(); // ← SAVES HERE

}

private System.Collections.IEnumerator HideResultsAfterDelay()

{

yield return new WaitForSeconds(raceResultsDuration);

showingResults = false;

// Save lap times before potentially leaving the scene

SaveLapTimes(); // ← SAVES HERE

}

📊 Summary - File Responsibilities

---

✅ Conclusion

Your initial statement was incorrect - FirstSecThird.cs DOES save a file: laptimes.json

This file stores:

· Best lap times per track (for leaderboards)

· All lap times history (for statistics)

· Track-specific records (persistent across game sessions)

It's different from the CSV/TXT files that CRCarInfo creates because:

· CRCarInfo: Creates new timestamped files each race (detailed per-race reports)

· FirstSecThird: Updates one persistent file with best times (cumulative records)

The architecture makes sense:

· FirstSecThird = Historical best times (like a hall of fame)

· CRCarInfo = Individual race reports (like race receipts)

· CRRaceManager = Campaign progress (save game)