Skip to main content

8.3.6.7 (2021.08.17)

RunScore Team
  • Fixed an issue caused by the “Records/Page” command that would cause headers in PDF’s to be displayed at the end of a page rather than the beginning.
  • Made a change to the “MyLaps ProChip” external timer to prepare for an upcoming change to the connection protocol. This change will now notify the user if the external timer has disconnected with the MyLaps Timing & Scoring App. This can be enabled by clicking the gear icon in Timing & Scoring of an existing TCP/IP export, then enabling the “Send Ping” checkbox under the Settings tab.

8.3.6.6 (2021.06.14)

RunScore Team
  • Added the ability to create a PDF output from listing files using the Destination, Output To, OR Output Format Commands
  • Added the ability to send a PDF to a Race Roster race

8.3.6.5 (2021.05.03)

RunScore Team
  • Fixed an issue that caused JSON output to fail if participants did not complete the same amount of laps in a lap race.

8.3.6.3 (2021.03.17)

RunScore Team
  • This release changes the cumulative time in output of laps race to default format (no fractional seconds). A timer requested requested that the time format used for cumulative times be the same as for split times, i.e. H:MM:SS.
  • This release updates the functionality of the “le number of laps” and “ge number of laps” commands to fix a bug that caused the laps not to be filtered correctly or display appropriate Time and Laps data as expected.

8.3.6.0 (2021.01.13)

RunScore Team
  • This release implements a breaking change to how emails are sent to SendGrid due to a change in the SendGrid authentication protocol. RunScore timers who previously used a username and password to send emails through SendGrid will need to contact Support at support@runscore.com to be issued a new username and password with instructions for generating the required api_key that is now used to authenticate email requests to SendGrid through RunScore.

8.3.5.10 (2020.12.02)

RunScore Team
  • This release includes a fix that prevents a deadlock situation from happening when a timer deletes results on the RunSignUp dashboard, but the result set will still be defined in the timer’s race folder.

8.3.5.9 (2020.11.03)

RunScore Team
  • Adds new integration with the BlueBox external timing system
  • RunScore now supports the upload of custom fields to RunSignup. Prior to this change, when a timer did a native upload, only fields that RunSignUp knew about, e.g. “First Name” could be uploaded. By supporting custom fields, now any field can be handled.

8.3.5.8 (2020.10.27)

RunScore Team
  • Timers reported that they were experiencing greater RunScore instability and crashes especially during live races. The cause was traced back to a minor update to the screen refresh rate. This update strictly removes that earlier change.

8.3.5.7 (2020.10.21)

RunScore Team
  • Adds support for RunSignUp custom fields
  • Fixes minor issue that could cause RunScore to hang when initializing a timer
  • Fixes a minor issue that could cause incomplete downloading of participants from when parsing empty or bad input data
  • Removes extraneous RunScore Results login