Changelog.

SCORING SCOPE

Road Racing becomes the first defined RaTiX discipline.

The initial RaTiX scoring model is now explicitly focused on Road Racing. Other motorsport disciplines will not inherit the Road model automatically and will require their own validation and calibration before becoming supported RaTiX categories.

• Road Racing defined as the initial scoring scope
• Oval reserved for a separately calibrated future model
• Dirt Oval reserved for a separately calibrated future model
• Dirt Road reserved for a separately calibrated future model
• Multiclass comparisons follow a class first approach
• Score and Confidence are treated as separate values
• Missing required data returns unavailable or null instead of an artificial default score

A RaTiX formula must fit the motorsport discipline it evaluates. Unsupported disciplines will remain unrated until their signals, thresholds and weighting have been validated with real data.

GARAGE 61

Global benchmark access validated.

Global benchmark access was enabled directly in coordination with Garage 61 after discussing the RaTiX concept and calibration approach.

• Global external driver data confirmed
• Track and car filtering validated
• iRating range filtering validated
• Session type filtering validated
• Track temperature filtering validated
• Track usage filtering validated
• Fuel level filtering validated
• Relevant benchmark fields confirmed in API responses

Pagination and rate limit behaviour remain part of the next API implementation phase.

BENCHMARKING

Real world PAC calibration moves beyond local test data.

Garage 61 can now be used as an optional external benchmark source for PAC development and scoring calibration. The native iRacing pipeline remains responsible for live RaTiX sessions.

• Real driver populations can be queried for comparison
• Benchmark populations can be filtered by relevant session context
• External data can support larger calibration studies
• Garage 61 remains optional and is not required to calculate a RaTiX score

LIVE SESSION PIPELINE

Complete spectator session processed successfully.

A full iRacing session was observed in spectator mode and processed through the RaTiX application from capture to stored rating output.

• Practice captured
• Qualifying captured
• Race captured
• Session data persisted locally
• Scores generated by the rating engine
• Driver profile UI populated from stored session data

SCORING ENGINE

Scoring Engine 1.0.1.

The current engine processes complete captured sessions and calculates the six RaTiX components used by RTX Global and RTX League.

• PAC implemented
• RAC implemented
• AWA implemented
• QAC implemented
• STR implemented
• EXP implemented
• Component calibration remains in active validation

DUAL SCORE SYSTEM

RTX Global and RTX League implemented.

RaTiX now supports two views of the same rated session.

• RTX Global uses equal weighting across all six components
• RTX League can use custom component weighting
• Both ratings are calculated from the same underlying session data
• RTX Global remains available as the neutral reference

DRIVER PROFILE

Local profile and progression interface operational.

Stored RaTiX sessions can now be presented as a persistent local driver profile instead of isolated race results.

• Active rating display
• Six component overview
• XP and levels
• Session history
• Local SQLite persistence

ARCHITECTURE

Local RaTiX runtime established.

The core application architecture moved from concept into working software.

• Desktop application
• iRacing adapter
• Local runtime
• Deterministic rating engine
• SQLite storage
• Local user interface

The scoring formulas remain internal while calibration and validation continue.