This is an update to an older post you can find here.

If you just want to download the new Replay Director, click here.

Working with the iRacing replay software can be pretty challenging. While they clearly thought about people producing replays and have custom cameras, keyboard shortcuts to switch cameras, etc – actually using the replay software in that way is frustrating and almost unusable.

Lately, even things like the ‘Follow most Exciting’ camera mode doesn’t even seem to work, and I doubt issues with the replay software is near the top of the team’s roadmap.

In my previous post we looked at a 3rd party application that helps you insert camera changes and create a set of ‘nodes’ you can use to build out a professional iRacing replay.

Now, I have updated that application to automate the camera changes based on ‘events’ the application finds by scanning through the replay file.

Here’s a sample race with all driver selection, camera changes, and overlays provided by the new Replay Director software:

I’ll walk you through how to setup and use the software:

Software & Setup

To get started, head over to the releases page, download the zip file, unzip it and run the exe file.

Once you launch an iRacing replay, you’ll see the cars in the left hand bar start to populate.

base screen

Settings

You can see all the documentation in the Github repo.

You can change the way the application weights different event types to select which driver the camera is focusing on at any given moment. You are also able to select a driver # to focus on more (since you probably want to focus on yourself).

The default settings should work well, but feel free to change these for your specific needs.

Overlays

The application also includes a few simple overlays that can be used with OBS Studio or other screen recording software.

The available overlays are:

  • Current Driver
  • Driver Ahead
  • Driver Behind
  • F1 Style Leaderboard

You can see these overlays in the Youtube video linked at the top of this post.

overlay settings

Scan for Events

Make sure you’ve skipped forward in the replay to the Race session and are at the starting point in the race you want to start recording, then go to the Auto Director menu at the top and pick the Scan for Events option.

Now the application will scan your replay for events which can take a good amount of time for longer races. It will alert you with a pop-up once the scan is complete.

scan for events

Applying Camera Changes

Now simply goto Auto Director menu and select Apply Camera Events to see the camera changes put into place.

You can change the Event Detection settings and re-apply the camera plan without needing to rescan for events – This makes playing around with the settings trivial.

Coming Up Next

I want to build out more AI features and try to let an LLM act like a camera director and have more control over switching between drivers and cameras within the events detected by the application, but that proved difficult with the data we have available.

I’d like to add more support for custom cameras and have a database of custom cameras out of the box – I may also look to add more overlays over time.

If there’s any features you’d like to see or any bugs you discover using this program, please submit them in the comments here or in the issues section of the GitHub repo.

Thanks for reading!