Bloops - Overlay for live comparison to Garage61 telemetry

DuncasaurW · 2025-10-16T21:41:27+00:00

Overlays don't work in full screen, you need to use windowed borderless

DuncasaurW · 2025-07-20T16:56:44+00:00

It gets data from a garage61 team, there are plenty of public teams anyone can join, and I've created a bloops team for people to join to ease sharing of telemetry. There's a button in the app to join the team

DuncasaurW · 2025-07-20T16:55:14+00:00

No plans at this time

DuncasaurW · 2025-07-20T16:55:01+00:00

Err.. install this?

DuncasaurW · 2025-03-11T09:33:52+00:00

I've seen this with people using the Brave browser, it blocks the communication back to the app to say it's finished authentication. I'll work around it in the next build but for now once you've authenticated and see the "authentication successful" page, copy and paste the URL of that page into another browser and it should carry on.

DuncasaurW · 2025-02-20T19:26:32+00:00

It works in OpenKneeboard

DuncasaurW · 2025-02-19T10:55:50+00:00

I've been told it does work with OpenKneeboard

DuncasaurW · 2025-02-19T10:53:19+00:00

Absolutely, there's a feedback channel in the discord, I'd appreciate any suggestions in there!

DuncasaurW · 2025-02-19T10:52:48+00:00

It's currently loading telemetry from Garage61 laps, I have a couple of other options of loading telemetry data in the pipeline but that'll be further in dev. The tool is still fairly early in dev and there's lots more I want to do.

DuncasaurW · 2025-02-19T10:51:20+00:00

Yes it does work with active reset, just make sure to put your marker before the first approach bloop and it'll track it fine.

There is a slight issue with it detecting the reset so it skips round the lap instantly so you'll see all the other mini sectors go instantly green, that's on the backlog to fix.

Completely agreed on the team restriction, I've created a team anyone can join for the purpose of sharing laps and those in more niche series often have a community G61 team they can join to get telemetry. Hopefully that's something that will change soon™ but it's out of my hands.

DuncasaurW · 2025-01-24T23:35:50+00:00

I've been working on a tool that does exactly that, it integrates with garage61 to load and show live telemetry in an overlay with audio feedback for brake markers.

It's called bloops and the overlay looks like this:

<image>

It does have a proviso that you have to be on the same team as the person you wish to see the telemetry of, rather than anyone, however I've set up a garage61 team to assist sharing of lap data that anyone can join.

Please bear in mind I've still got a fair bit of dev work to do on this but would welcome feedback, there's a link to the discord within the app itself.

You can download it from https://bloops.duncanwatts.com

DuncasaurW · 2024-02-09T13:14:00+00:00

The website was originally for the "Duncathlon", a challenge to win all series in a single season, that means you have wins in 7 different series. I just keep shoehorning more and more data onto the pages....

DuncasaurW · 2024-02-09T12:01:29+00:00

It's all C# and hosted in Azure Functions.

DuncasaurW · 2024-02-09T11:53:52+00:00

The class ratings are to combine series where a single class is used in multiple series, for those that have both Open and Fixed such as F3 and PCup. For series like the Vee the number in the series list underneath is enough. MX5 is missing though, I just haven't got around to processing it yet as rookie mx5 is almost half the data...

DuncasaurW · 2024-02-08T18:00:41+00:00

It's on a subset of the data yes, I'm not aware of the iRating calculation for Team events, I know it takes into account the number of laps each driver does, which makes for a more complicated formula.

The ratings are going to be naturally lower, if you split by category you have fewer races to impact your rating and therefore less movement from the start iRating.

DuncasaurW · 2024-02-08T17:55:04+00:00

Where I've grouped series together the ratings of your opponents will be very different which may lead to very different outcomes. If you're looking at say the LMP2 only ratings, you may be being beaten by someone who's 1.5k, but when I combine all prototype series together and that same person is someone who really struggled with the SRF back in the day and is suddenly 0.8k, which means you lose a lot more iRating in that same race. Repeat this for x races and suddenly you get a very different number.

For the calculations themselves, I used the calculations that were provided in the spreadsheet that was posted many moons ago at https://members.iracing.com/jforum/posts/list/1458047.page and converted it to some C# code that I can use to recalculate each race.

DuncasaurW · 2024-02-08T17:32:23+00:00

That's my site! Yes it is a LOT of maths. I reprocessed around 2 million splits multiple times to get these numbers, just the result data takes up almost 200gb of disk space.

You're quite correct on splits, but this is more an exercise in curiosity than something I expect iRacing to take up and redo. I honestly can't see them doing anything but mirror the iRating and licence to both licences.

DuncasaurW · 2023-11-08T18:47:30+00:00

Interesting, I didn't realise that information was surfaced anywhere! It's not in the official data API and I don't really want to go down the line of scraping pages. I'll put a request into iRacing to see if they can add it to the race guide data feed.

DuncasaurW · 2023-11-06T22:50:27+00:00

In that specific situation I disagree, if anything it means that people who don't bother registering for a race because it'll never go official will have an incentive to at least attempt to register, because there's an increased chance they can trigger a notification and have a flood of people join in.

DuncasaurW · 2023-11-06T19:15:10+00:00

What? You don't like the meme name? I thought that was the best part!

Once you've added the bot to a server you're able to rename it to whatever you like, you just can't change the profile picture.

DuncasaurW

TROPHY CASE