Skip to main content

9.0.0

RunScore Team

We are incredibly excited to unveil RunScore 9.0.0! A release that marks the beginning of a new chapter. This isn't just an update; it's a complete evolution of the software you've relied on for decades.

This version delivers 188 epics, bug fixes, and major improvements. We have focused on extreme performance, absolute data integrity, and a new community-focused model that makes RunScore accessible to everyone.

🆓 RunScore is Now Free​

The annual license model is officially retired. We believe the best timing tools should be available to every timer, everywhere.

  • No Annual License Fees: RunScore is now a free service.
  • One-Time Sign-Up: We've replaced the annual payment process with a simple, one-time Sign-Up form built directly into the application.
  • Fleet-Wide Licensing: Once you sign up, your license is valid for your entire laptop fleet. No more managing individual keys for secondary machines or finish-line backups.

☁️ MYLAPS Cloud: Timing in 2 Minutes​

Our new MYLAPS Cloud integration is designed for speed.

  • Automated Setup: The application does most of the heavy lifting. You can be up and running with cloud-ingested data in about two minutes.
  • Bib or Chip Selection: The integration now functions like a standard local connection, allowing you to configure the system for either Bib or Chip timing.

🎯 Precision & Data Integrity​

We've addressed long-standing "silent" issues to ensure your results are 100% accurate.

  • The "31-Day" Age Fix: Older versions used a mathematical approximation for age calculation (treating every month as 31 days). This could occasionally place a participant in the wrong division. Version 9.0.0 uses exact SystemTime logic, correctly accounting for 30 vs. 31-day months and leap years.
  • Advanced Runtime Validator (RTV):
    • Undefined Variables: The RTV now flags custom variables that have not been defined.
    • Ambiguity Alerts: It will warn you if a variable name creates ambiguity with RSM parameter replacements (like %1 or %a), preventing logic errors in your listings.
  • Corruption Prevention: The Enter Window now verifies if a record is completely empty before saving. This prevents the "blank record" bug that could previously lead to database corruption.

🛡️ Stability, Networking, and Best Practices​

Important Update on This Release​

We've shipped some great improvements and want to share a few tips to get the most reliable results on race day.

What's New

  • Rock-Solid Server ↔ Client Connection: RSServer and RSClient now talk to each other more reliably, even when a lot of data is flying between them (big events, lots of reads, busy networks).
  • No More "Bad Data" Crashes: If your timing hardware (ChronoTrack, race|result, etc.) sends an oversized bib or a weird/malformed read, RunScore will now shrug it off instead of crashing.
  • Windows Remember Their Size: Your Browse, Enter, and Listing windows now remember the size and position you set per race. Set them up once the way you like, and they'll come back that way next time you open that race.

A Few Best-Practice Reminders: Behind the scenes, RSClient doesn't actually do the "work" itself — it asks RSServer to do everything for it over the network. That's great for viewing data, but it means some things are safer and faster when done directly on RSServer.

Here's our recommended setup:

Use RSClient for (viewing only)
  • Announcer station
  • Live Results display
  • A second screen to watch Browse/results come in
  • Running listings that only touch fields not used in results reporting (e.g., updating Email, City, Shirt Size, etc.)
Please do these on RSServer, not RSClient
  • Entering or editing participants (especially Age, Bib, Gender, Start/Finish times). There is a known gap in how entries flow from Client → Server that can affect age-group processing. Until that's fully closed out, please do entry work on the server.
  • Sending SMS or Email — always from RSServer. Sending from the Client adds complexity and isn't as reliable.
  • Auto-Run — always from RSServer.
RSClient vs RSServer

RSClient = a window to look at the race. RSServer = where you run the race. When in doubt, do it on the server.

🤝 A Special Thank You​

This release wouldn't have been possible without our incredible community.

  • Beta-Timers Group: A massive thank you to our beta testers for their rigorous reporting and feedback.

RunScore 9.0.0 is the most stable, fastest, and most accessible version of RunScore ever built. We are proud to put these tools in your hands for free.