v3 is largely a total rewrite. Why? Well, first, I started this project 4-5 years ago, when node.js (the server) was still very young. Since then it has matured and developed a massive community and adoption rate. That said, lots has changed and vastly improved. Including my own knowledge as LR and RM were my first published/usable projects with node (and since has been my dominant platform for the last 4 years of projects). Secondly, the codebase is simply messy and hurried and drives me a crazy given it never took the time to go back and rebase into a better structure/pattern as I learned more and more (like real automated testing with complete code coverage).

So, now is the time. It is going to take some time, and I super appreciate everyone's patience and feedback.

Now for the good stuff... features.

v3.0 will be the current feature set with some updates.

UI completely redone (every single screen). Tablet first views and switched out of the jquery mobile UI.

Core features are exposed as a RESTful api (e.g. add driver to queue, finish line crossed, add cones, new registration, etc.)

Separation of real time communication concerns, meaning you manipulate the system through the API and receive data updates at the client (screens) via real time socket updates. This makes soooo many things easier on so many different levels, as well as opens up more possibilities for those that want to customize
** the above was a big change and much needed. Now all system manipulation is done through a single interface. Like adding a new registration, all goes through the same "function" regardless of where it is coming from (MSR import, CSV, the registrar sitting at the reg table, etc.) I know, I know, shame on me for not doing this in the first place :-)

Separation of timing and scoring. These are now 2 different things which allows a much simpler approach when adding new scoring types (hello Rally Cross, Pro Solo, etc.)

Worker checkin. Let’s be honest, the first version sucked. My bad. Now it is better. It won’t satisfy everyone, but most of you. You all do work assignments so differently, which I still don’t quite get. My original intention of flexibility is still there. assign work duties prior, worker checks in prior to their rungroup/heat/etc. but person checking in can assign to whatever. Bottom line, first version = yuck, new version = better.

Dedicated car # / class is now separate screen and not updated by registration screen. Think of it as your binder / Excel spreadsheet that you all keep with all your reserved numbers/classes.

Registration / Driver Checkin is merged and simplified into a single screen.

Multiple events per day by simply making one live and the other not live. By default, events are “live” (so long as the date is “today”), but you can “disabled” the first event when you’re ready to start the second.

CQ is getting a screen makeover with more contrast, functionally the same

CC… I have a total rewrite again but given some of your feedback will probably end up with 2 options. Or a single screen that allows for either grouping drivers by “status” (queued, on course, finished), or order by car # or snaking slot (this keeps the car in the same “slot” regardless of status.

CC’s new feature is having a new screen for adding/managing cones. From a single screen you can add cones to multiple stations without having to go back into the screen… you’ll see it is waaay nicer/easier.

TK - I’m still deciding. I’m toying with the idea of making a single system screen for TK that can do TK, CC and CQ easily and intuitively.

Results - many of you have expressed wanting to have to old school format in printed form. This isn’t a replacing Live Result, but the printed results. Your wish, my command.

Exports / Imports - one improvement of exporting an event and importing it again. Maybe you had to use a different main computer for a single event and didn’t use the restore from cloud backup and then backup to cloud. :-/

Well that’s what I have off the top of my head.

I’m still a couple of months away, so thank you for the patience… it’ll be worth it, I promise.

Oh, Rallycross version will be formally introduced in v3.1. I need to get through the rewrite, and then add the big change, as I want to do it right and awesome.

@JasonPowell - Absolutely. There are some minor inconveniences with the current software, but nothing we can't live with. As long as data backup and live results stay operational, we would definitely be willing to pay a reasonable maintenance / subscription fee.

Chris is still alive! Had a phone chat with him tonight. Here's the short version: His startup has consumed all his time, but he hasn't forgotten about axtime. Version 3 is about 1/2 done. There is a possibility he'd make the current version open source which would allow clubs to tweak things to their liking. LIVE CLOUD RESULTS will continue to work for many years as this service is set to auto-renew each year. IF we see the oddities with live results like last fall, I'll let Chris know and he'll restart the cloud services. He's hoping to give us all an update in the coming months about his plans for the software in 2018.
Personally, I'm happy with current version of the software (we had zero glitches in 2017) and I feel good about the 2018 season knowing the cloud results will continue to work :-)

So, is Chris still available for new sales? I have an acquaintance who ghosted one of our events last year and is considering buying AXti.me for his club, but the main AXti.me site seems to have disappeared and the FB page hasn't changed in years. This forum and the demo are still available, so the message is ambiguous. He's worried about committing to the purchase with zero support, if he can even do so.

@sjd - I understand your point and share some of your sentiment, particularly your disappointment. However, I see no reason to abandon the system as long as it still continues to function. We paid our initial purchase price 3 years ago and AXti.me has not cost us a dime since then. As long as live results work on event days and the software is usable between, we plan to keep using it.

@Duke That's the issue, it wasn't working for us. It worked for a while and then stopped for no apparent reason. I outlined the entire problem in another thread. I know we were on a Macbook which some speculated was this issue. So it had stopped working, support had become non existent and we had no choice but to abandon it. Ironically enough we're now running Windows on the Macbook Pro with different software and it works perfectly.

@JasonPowell The software we're using now was written by a Canadian autocrosser with the Southern Alberta Solosport Club and is called MJ Timing. It's free but not open source.