Couple of Possible Bugs

66 views
Skip to first unread message

Gregg Mrkvicka

unread,
May 26, 2026, 7:17:45 AMMay 26
to Agee Race Timing Users Group
A couple of possible bugs from yesterday's race:

1. After the race started I punched in a random number of a competitor to check our network to the results kiosk. He came through fine so I deleted the read, finished the race, and reset the race. When that person actually did finish the race his chip did not read, it said he already finished with a finish time of 3 minutes (or whenever it was that I typed in his number to check the network). I had to give him a whole new number and manually put him in using the space bar and editing the time.

2. We had a runner entered into the wrong race. When I went and changed him to the correct race his finish time was deleted. His space as the second finisher on the timing screen was still there just completely blank. I had to double click it, enter his number and enter his time. 

Thanks for looking at these.

gregg

Brian Agee

unread,
May 26, 2026, 9:37:04 AMMay 26
to Agee Race Timing Users Group
I just tested both of these scenarios every way I could think of and I could not reproduce the problem. If you can reproduce the issue, send me a step-by-step guide or record a video and send it my way.

Frank H.

unread,
May 26, 2026, 4:57:42 PMMay 26
to Agee Race Timing Users Group
I had something similar happen to me on Saturday.  I had a participant show up late for a 5k and start after I had stopped capturing chip starts.  Nobody told me she was a late start and I captured her as a finish time.  I double clicked on her name in the athlete list and set her chip start time to her last seen time, then deleted her read.  She finished but it acted like I didn't pick her up. I didn't realize her "last seen" time in the athletes tabs (1/1 completed) didn't delete when I deleted the read and when I noticed, I refreshed the results from the action keys tab and the "last seen" read was gone and it let me manually give her a time and adjust it.  I played with it a little yesterday and it is repeatable but random where most of the time removing the read also removes the last seen but it seems almost always, one does not.  You can delete 25 results and one will not remove the last seen but the other 24 will. I did this on a two person event and almost every single situation, one last seen wasn't removed when the read was deleted.

I just figured from now on, if I change anything, I would refresh the results after doing so and eliminate the issue.

5/14/26 release of 1.6.7.1

Christopher Regan

unread,
Jun 4, 2026, 12:18:33 AM (8 days ago) Jun 4
to Agee Race Timing Users Group
I also ran into something similar to #1. I think the issue was that it read a bib I didn't have assigned to someone. I thought I then went in and changed the bib to match the actual bib # it should have been. Lets say the bib read was 4975 but she was actually 4976. I change the bib associated with the time for 4975 to 4976. Later I get a runner who doesn't get read on the finish line. I hit the spacebar to record a time. Turns out this is actually 4975 but when I try assign bib 4975 to the new time I just recorded it tells me they have already finished. So i had to change their bib to something else and then assign that to the runner to get them a time.

From my perspective the issue would most likely stem from when a time is switched from one bib to another, the original bibs finish time isn't getting cleared when it's transferred thus causing the software to think the original bib already finished the race.

Christopher

Christopher Regan

unread,
Jun 4, 2026, 12:25:02 AM (8 days ago) Jun 4
to Agee Race Timing Users Group
I just tried testing this and couldn't get it to occur. I'm sorta wondering if it had something to do with RunSignup as I was messing with RunSignup when my issue occurred trying to correct the bib issues.

I'm going to see if I can get back to that race and figure anything out.

Brian Agee

unread,
Jun 4, 2026, 12:23:56 PM (8 days ago) Jun 4
to Agee Race Timing Users Group
Today I spent some time on it and was able to replicate and fix issue #1 that was reported. So this fix will be included in the next update. Thanks!

Christopher Regan

unread,
Jun 4, 2026, 12:38:24 PM (8 days ago) Jun 4
to Agee Race Timing Users Group
Awesome, thanks Brian!

Steve Hudson

unread,
Jun 5, 2026, 2:54:33 PM (7 days ago) Jun 5
to Agee Race Timing Users Group

Swapping race numbers between 2 runners who wore the wrong ones according to the start list, such as those issued for husband and wife, is handled differently when on the race results clock screen ( highlight both and right mouse click and Swap option ) than on the Athletes list ( change runner A to be , say, 9999 then change runner B to be runner A’s race number and finally change runner 9999 to be runner B’s race number ).

First method is quick to do but chip start times not swapped. Second method works fine but is longer to achieve in the heat of the moment.

Could the chip start bug be resolved please and the highlight/right mouse click option be adopted on the Athletes list ? Thanks
Reply all
Reply to author
Forward
0 new messages