The first iteration was a simple copy of the RotorHazards built-in Webinterface hosted on a webserver with a changed datalink using a json file instead of a (local) socket.io connection to retrieve new race data. This solution could display race-results in the form of laptimes, but no double elimination tournament bracket or a quick way to understand when a pilot will have his next race.
Copterrace – EP2: Simple Start
Back to: Projects