Now is the time to be heard so post away.I'm sorry it has taken some time to answer your questions.
Yes, it's clear now that we have introduced some problems in RowPro version 2. Here's an update on what we're doing about these problems:
- Daylight saving: We had an issue with a 1-hour offset in the race server when Daylight saving started in the US last week. This is now fixed.
- GMT: When you set the start time of a scheduled race in RowPro 2.000, the GMT start time is incorrect, but if you create the scheduled race on the Oarbits website it works correctly. We have fixed this problem in RowPro 2.001, which we expect to release in the coming 2-3 weeks. We may be able to "correct" the RowPro 2.000 GMT error by making a change on the race server. If this is possible, we should be able to do it in the next week, and this will enable people to create scheduled races with the correct GMT using RowPro 2.000. In the meantime, all scheduled races need to be created using the Oarbits website.
- Freezing on screen: There is a bug where packets are sometimes not being transmitted over the network while you are racing. This leads to a number of issues similar to what you described. We have seen this bug in the lab and have done some work to find a solution, but we're not there yet. We will do some more work on this, and if we can find and fix it in time for the release of 2.001, we'll put the fix in that.
- 1.8 compatibility: There was an issue with people graying out at the start in 1.8, which is fixed in version 2. If people with 1.8 join a race with other people who have version 2, the 1.8 people may gray out at the start. This is a catch-22, because upgrading to 2.0 will fix the graying out problem but will introduce the version 2 problems. Because of this, it's not realistic for us to say people should upgrade from 1.8 to 2.000. However once 2.001 is released, if we have managed to fix the packet transmission issue, then our advice will be to upgrade from 1.8 to 2.001.
- e-Row: In principle the race system still works with e-Row, however we are not testing as much with e-Row now so it's possible there are some issues with e-Row.
Stepping back from all this, we all know the main reason for this ongoing series of small but intrusive issues is that the race system is designed for compatibility with e-Row, and this means there are some fundamental issues that we cannot resolve in the current race system. Because of this, we are now building a new race system. We know everyone wants this new race system, so we have stopped patching up the old system and are now concentrating all our effort on making the new one as quickly as possible. The one exception to this is the packet transmission issue I described above, which we will try to fix.
We are aiming to have the new race system ready around June / July this year. There's a lot to do, so these dates are just an estimate at present. Some key points about the new race system are:
- The plan is to release the new race system in RowPro version 2.005.
- The new race system will use a different network protocol. This means it will only work with RowPro 2.005 and later. It will not work with e-Row at all, and it will not work with RowPro versions earlier than 2.005.
- Soon after we release the new race system and we know it's stable, we will close the old race system, so anyone who wants to continue racing will need to upgrade to RowPro 2.005 or later. This is because it's not practical to split the racing community in two, and also because racing between the old system and the new system will not be possible. This will be a major step forward for the race system and for everyone using it.
Please feel free to forward this email to other RowPro users. I'd welcome your feedback about all this.
Also, if there are any other issues besides the ones discussed above that your really really want us to look at in the current race system, please let me know and we'll consider whether it's better to look at them or to wait for the new race system.
Pete
Digital Rowing
Frank