Something in ORAC's driving bugs you? This page tells you where to look. The full tuning guide describes all 1,400+ settings; you don't need to read it. Find your problem below, try the settings named there, and ask an AI assistant when you get stuck.
How tuning works
Tune in the game. In a race, press F9 and open ORAC's Tweaks menu. Each window there (PIDs, Steering, Pedals, Speed plan, Lanes, Weather, Gears ...) is a group of settings. A change works at once on every ORAC car and is saved to C:\orac\orac_tweaks.ini.
Change one thing at a time. Move one setting a little, drive or watch a few laps, and compare. Write down what you changed. "Reset ... to the code defaults" in each window takes you back.
Make your tune-diff file. Double-click ORAC tune diff.bat in your ORAC folder. It writes ORAC-tune-diff-<date>.txt to your Desktop, with the settings you changed and your notes.
Upload it. Use Upload your tweaks, with a comment on what got better. Others can try it and reply, and we fold good settings into the next release.
Problem → where to look
The place is the F9 window and the group inside it. The setting names are written as they appear in orac_tweaks.ini and in your tune-diff file. Start with the first setting of each row, and make small steps (5 to 10 percent).
difficulty.brake: higher = later, harder braking (lower = earlier, softer). control.pedals.brake_envelope_slack: how far the brake may go past the car's measured limit. pids.brake.kp: how hard the brake pedal chases its target.
difficulty.accel: higher = the plan expects more acceleration, so higher speeds on exits and straights. control.pedals.throttle_envelope_slack: how far the throttle may go past the measured limit. control.plan.exit_brake_inhibit: on = no braking on corner exits. pids.throttle.kp: how hard the throttle chases its target.
difficulty.corner: the corner speeds; this is where difficulty shows most. difficulty.tyre: one grip factor on corners, braking and acceleration together.
control.steering.aim_base_m and control.steering.aim_speed_coeff_s: a longer look-ahead turns in earlier and steers more calmly (but cuts more to the inside). pids.pursuit.kp: higher turns in harder and earlier; lower runs wider. pids.lateral.ki: raise it if the car sits beside the line through a long corner.
pids.pursuit.kd: too low and the car overshoots and oscillates around the line. pids.lateral.kp: too high snatches at the line and weaves. pids.lateral.kd: raise it slightly if the car weaves after a correction. control.steering.aim_base_m: too low and the car weaves.
Slip › Per-car peak Pedals › Slip on the pedals (output) Pace & difficulty › Difficulty
peak_rear_slip_factor: lower = the rear-slip reactions come in earlier. control.pedals.throttle_slip.long_rear.gain: the throttle's traction control; raise it against wheel spin. difficulty.accel: lower it a little.
Too timid or too aggressive in traffic: side by side, overtakes
Lanes › Pass decision Lanes › Car ahead Lanes › Contact Speed plan › Follow caps Traits › Aggression
lanes.lane.w_pass02: higher = moves out to pass earlier and more firmly. lanes.lane.w_front: raise it if cars move around a slower car too late; lower it if they swerve for cars that are no threat. lanes.lane.w_contact: raise it if cars touch side by side; lower it if they refuse to run close alongside. lanes.lane.follow_time_s: the following gap; lower = closer racing. trait_groups.aggression_side.pct_min: how much more side room the most timid drivers keep.
Too slow or too fast in the wet, or through puddles
Weather › Wetness → grip table Weather › Puddles
wet.wet_on_wet_lat and wet.wet_on_wet_long: the grip ORAC expects from wet tyres on a fully wet track (higher = plans faster). wet.puddle_cost: higher = avoids standing water more.
Pace & difficulty › Difficulty › Tyre per vehicle class
difficulty.tyre_class.<class>, for example difficulty.tyre_class.gt4 or difficulty.tyre_class.lmdh: a grip factor for that class only. 1 = no change; the guide lists the cars of each class.
Odd gear shifts: too early, too late, up-then-down pairs
Gears › Shift points Gears › Guards and timing Gears › Rev match
control.gears.upshift_rpm_fraction: lower = earlier upshifts. control.gears.downshift_rpm_fraction: higher = downshift sooner when slowing. control.gears.brake_zone_guard_s: raise it to stop upshifts further before corners. control.gears.rev_match: the throttle blip around a shift.
They show what ORAC is thinking, drawn over the game. Open one with F9 → ORAC's Debug menu → the screen's name. No extra start flag is needed: the Launch ORAC files start the game ready for it.
Each screen shows the focus car: by default the car the camera is on ("Follow camera" at the top of each screen). Press F6 for the debug camera and switch cars with the camera-cycle controls. ORAC data shows only for cars ORAC drives.
Inputs
Screenshot coming soon
What you see: graphs of the last 5 seconds (newest on the right): speed, pedals, steering, the steering PIDs, the speed PID, the pedal PIDs, over / understeer, and each axle's slip compared with its peak. The current gear and gear target are shown as numbers.
Speeds: white = the car's speed now, blue = the speed the throttle aims for, orange = the speed the brakes aim for. A follow limit appears only while the car is held up behind another.
Pedals and steering: each has the value sent to the game and its target. A big gap between them means the output is limited (rate limit, slip, a ceiling).
Slip / peak: 1 (the grey line) is the tyre's peak grip. Above it, the tyre is sliding.
Tells you: white speed above orange before a corner = braking late or too gently, see Brakes. Throttle well below its target on exit = something holds it back, see Slow out of corners. Rear slip far above 1 before a spin, see Spins.
Heading + lateral
Screenshot coming soon
What you see: two graphs of the last 5 seconds.
Heading (degrees): the white middle line is the direction of the lane the car wants to be in. Red = the heading the steering aims for, blue = where the car actually points. Grey lines at ±5° and ±10°.
Lateral error (metres, up = the car is left of it): red = distance from the target lane, green = distance from the steering's own aim. The scale is stretched near zero: equal bands for 0-10 cm, 10 cm-1 m and 1-10 m.
Tells you: lines swinging up and down around white on a straight = the car weaves, see Wobbles. Red lateral error staying on one side through a corner = it runs wide or sits off the line, see Turns in late.
Speeds 3D
Screenshot coming soon
What you see: the speed plan as a coloured ribbon on the track ahead of the car (menu name: SPEEDS 3-D + SLOWDOWNS).
Blue = accelerating, red = braking, white = speed held. Deeper colour = harder.
Speed numbers sit on the ribbon. An amber cross marks a slowdown for a car ahead, a magenta cross a stop, a cyan cross a car we follow.
Labels above the cars ahead are coloured by time to contact: red soonest, then orange, yellow, white.
Tells you: where the red starts is the braking point. Red starting long before the corner = brakes too early. Lots of white or pale blue on an exit = throttle too gentle. Amber crosses everywhere in traffic = the car is held back by others, see Traffic.
Lanes 3D
Screenshot coming soon
What you see: the road ahead cut into thin lanes, 10 cm each, coloured by how good ORAC thinks each lane is.
Green = a good lane, white = neutral, red = a bad lane (another car, a wall, the road edge, a puddle).
Blue = the lane the car has chosen, yellow = the racing line's lane, the white line and cross = our car.
Lanes off the road are not drawn.
Tells you: why a car picks a side. Blue jumping from side to side = it cannot make up its mind; red covering the space next to a car = it will not go side by side. See Traffic or Wet.
Tracking
Screenshot coming soon
What you see: lines drawn from the car onto the track (menu name: TRACKING 3-D).
Green line = the path the steering follows to reach its lane. Blue line and cross = the target lane, where that path ends. Red line along the path = the target lane the lanes logic picked.
Yellow line and cross = the aim point the steering looks at. Magenta line and cross = the car's distance from where it should be now.
Red line 3 m from the car = where the car points; cyan line = where the steering wants it to point.
Orange cross = the point on the speed plan where the pedal targets are read.
Tells you: a long magenta line = the car is off where it should be, see Turns in late. Red and cyan heading lines far apart = the car is sliding or turning against the steering, see Spins.
Turning on screen_inputs, screen_tracking, screen_lanes or screen_speeds (F9 → Tweaks → Debug screens) keeps that screen running with its window closed, so it is ready when you open it. It never changes the driving.
Racing lines
ORAC can drive on a racing line you recorded yourself instead of the game's line. Each track layout has its own file; ORAC uses it from the next session, for every ORAC car.
Racing-line recording guide (PDF): step by step, with the messages you will see and what to do about them. It is also in the docs folder of your ORAC download.
Record a line
Start an offline Practice on the track and drive the car yourself (use Launch ORAC.bat, not the "ORAC drives your car" launcher). Other cars on track are fine.
Drive an out-lap, then one clean lap on the line you want.
During the next lap, press Ctrl+F8: ORAC saves your previous full lap as the dry line. For a wet line, drive a lap on your wet line and press Ctrl+Shift+F8 instead (record the dry line first).
The file is saved as C:\orac\lines\<track>_<layout>.oracline, for example braselton_layout_a.oracline. The F9 window Racing line shows what was saved and has the same two save buttons.
Restart the session (go back to the menu and start a new one). ORAC uses the line from then on.
Use someone else's line
Download it from the Racing lines page (lines can be downloaded once a moderator has checked them), or get the file from a friend.
Put it in C:\orac\lines\ and keep its file name exactly (<track>_<layout>.oracline). It replaces your own file for that layout, so back yours up first.
Restart the session.
Check that it is used
The F9 window Racing line shows the state for the current track.
In the log x64\orac_pmr.log (next to the game's exe), look for the line drive: racing line: ORAC line file ... EVERY ORAC line reader uses it. If the file has a problem, ORAC drives on the game's line and the log says why.
After a game update the file is still used; the log then has a warning that the game's own line changed since the recording. If cars look wrong there, record the line again.
Turn it off
Set raceline.enabled to off in the F9 window Racing line and restart the session: ORAC then drives on the game's line everywhere and records nothing. To drop a single track's line, delete its file from C:\orac\lines\.
Give both to your AI assistant (attach them to the chat).
Describe what you see: the car, the track, the corner, the weather, and what the debug screens show.
Ask which settings to change. Then change one thing at a time in F9 and test again.
Example prompt
I am tuning ORAC, an AI mod for Project Motor Racing. Attached are the ORAC tuning guide and "ORAC explained".
What I see: GT4 cars (Mercedes AMG GT4) at Spa, dry, brake far too early into La Source and lose about a second there. On the SPEEDS 3-D screen the red braking part of the ribbon starts well before the braking board. On the INPUTS screen the brake pedal stays below its target.
Please:
1. Explain in plain words what is most likely causing this.
2. Name the 2 or 3 settings to try, with the F9 window and group, the setting name exactly as in orac_tweaks.ini, and which way to move each.
3. Suggest a safe first step size, and what I should watch on the debug screens to see if it worked.
Only use settings that are in the attached guide.
Found settings that work? Upload your tweaks so others can try them too.