-
Notifications
You must be signed in to change notification settings - Fork 0
English
configure-iracing-performance is a Codex skill for diagnosing, testing, and safely tuning iRacing graphics. It supports one monitor, triple monitors, OpenXR, OpenVR, and Oculus.
It does not apply a universal preset. Documentation and recommended settings are starting hypotheses; the result is accepted only after an in-session comparison.
When the objective is not supplied, the skill asks the driver to choose:
- Maximum visual immersion — prioritize image quality and agree on a minimum acceptable FPS.
- Best graphics at a stable FPS — define a target FPS and maximize quality within that frame-time budget.
- Maximum consistency and lowest latency — prioritize stable frame time and accept larger visual reductions.
The display path is also confirmed: one monitor, three monitors, or VR.
- Driving performance is diagnosed from
[Graphics Options]. - Replay quality is read from
[Replay Graphics]and preserved by default. - Replay may remain at high or maximum quality because it usually does not require racing-level FPS.
- Replay settings change only when explicitly requested.
- Real-time replay capture gets its own resolution and capture-FPS target.
This separation prevents high-quality replay values from being mistaken for active driving settings.
Invoke the skill in Codex:
Use $configure-iracing-performance to give me the best graphics possible
while maintaining 144 FPS on triple 1440p monitors.
Other examples:
Prioritize VR immersion but keep at least 90 native FPS.
Find the cause of my iRacing stutters without changing anything yet.
Keep replay graphics at maximum and optimize only race performance.
- Define the display mode, objective, target, and acceptable trade-offs.
- Fix a repeatable test scenario: car, track, session, time, weather, grid, camera, and demanding scene.
- Run the section-aware diagnosis.
- Record baseline FPS and iRacing
R,G, andTframe times. - Change one performance lever.
- Restart the simulator when required.
- Repeat the exact scenario.
- Keep the change only when it improves the selected objective.
- Restore the backup if FPS, frame time, smoothness, latency, stability, or perceived quality becomes worse.
Common frame-time budgets:
| Target | Budget |
|---|---|
| 60 FPS | 16.67 ms |
| 90 FPS | 11.11 ms |
| 120 FPS | 8.33 ms |
| 144 FPS | 6.94 ms |
| 165 FPS | 6.06 ms |
| 240 FPS | 4.17 ms |
scripts/diagnose.ps1 -DisplayMode monitor -OutputFormat JsonValid display modes are monitor, openxr, openvr, and oculus.
The result includes:
- exact renderer and SHA-256 hash;
- renderer/display-mode match;
- blocking iRacing processes;
- driving and replay graphics as separate objects;
- display, monitor, and OpenXR sections;
- hardware evidence and warnings.
The script never falls back to a renderer for a different display mode.
scripts/update-renderer.ps1 `
-RendererPath <path> `
-Section 'Graphics Options' `
-Set 'MaxCarsToDraw=30' `
-ExpectedHash <sha256>Preview is the default. Add -Apply only after reviewing the proposed change.
The editor:
- blocks writes while iRacing UI or the simulator is running;
- refuses missing or ambiguous keys;
- detects a stale renderer through the expected hash;
- protects replay unless
-AllowReplayChangesis explicitly supplied; - creates an atomic backup before applying.
scripts/restore-renderer.ps1 `
-RendererPath <path> `
-BackupPath <generated-backup> `
-ExpectedHash <current-sha256> `
-ApplyThe restore is verified by SHA-256 and keeps a safety copy of the replaced configuration.
- Do not edit while iRacing UI or the simulator is running.
- Prefer supported in-sim controls over direct INI edits.
- Preserve resolution, monitor topology, FOV, and replay quality unless the driver approves a change.
- Change only one performance lever per test.
- Treat a target as achieved only after measurement in the agreed scenario.
- Revert measured or perceived regressions even when documentation recommends the setting.