|
Version 18.40 - August, 2018 |
|
New Features |
|
| Announcer Window |
|
|
Enhancements |
|
| Announcer Window |
|
| ORM Live Streaming Timing |
The corrected time was not being displayed (akin to the Announcer
Window). For live Timing the displayed time will now always be the
Combined/Corrected Time (RT + Time) when RT is configured as such.
AXWareProTS has the ability to optionally include the RT in the time if so desired. Default is ON (Corrected Time is = RT + Time) |
| Staging Grid |
Added Best Left and Best Right lane for staged entries. Prior to this
the Best Left and Best Right was updated once the run was completed.
Adding this for staging provides additional announcer information.
|
|
Bug Fixes |
|
|
Registration/Standing Grid headings |
Fixed a small display issue with the Headings to reflect the proper data fields and the number of runs being managed. |
|
Registration Grid Headings Runs Session |
Fixed minor Header Display issue in the Registration Grid based on the number of sessions and runs per sessions. |
|
Staging |
|
|
Version 18.30 - May 2018 |
|
Enhancements |
|
| Status Log during Re-accepting | Added more information during any re-accepting process. The status dialog shows more information about what the process is doing as well as closes it once done, indicating the operation is over. |
| Number of runs |
Revamp process to properly manage sessions and the number of runs
allocated for the event. Since the software is for true ProSolo events
as well as other style of events, the number of runs counted was managed
differently. Now:
|
|
Bug Fixes |
|
|
Recorded Times |
Best L and Best R times could show up as 3.000 and combined as 6.000
seconds. 2 conditions caused this to occur
|
|
Version 18.20 - May 2018 |
|
New Features |
|
| Networking |
|
|
Enhancements |
|
|
Staging |
|
|
Bug Fixes |
|
|
Staging |
In some cases entering the OFF penalty would kill the expected timer but cause the next set of times to be sequenced incorrectly. |
| Version 18.10 - Jan 2018 |
|
AXWareProTS - New Features |
|
|
Enhancements |
|
|
Warning Thresholds and Timing Triggers |
Added new messages to indicate false trip conditions for the finish gates.
This notifies the T&S of a potential false trigger due to trash blowing
through the sensors or a misalignment or another issue with the
sensor/emitter. Prior versions ignore the Warnings even though the configuration allows you to set the parameters akin to AXWareTS. |
| Time Slip Printing | Added additional data fields to the selectable items to print. This include RT, 60ft, etc. |
| Staging Row Height |
In order to provide more flexibility when selecting different Fonts in
the Staging Grid, the Row height can now be adjust to compensate for
fonts that are fairly large or tall. This provides support for
consistent row heights for any selected font. You can pick the font, and
adjust the row height as necessary. To adjust the height, position your mouse between the left side heading on any row in the staging grid and drag it to he new desired height. |
| Live Timing Streaming |
Many changes to Live Timing Streaming services. All event types are now
support including:
|
|
NEW Live Timing AXWareLiveRPI LAN base Live Timing |
|
|
Broadband based
Live Timing Streaming |
|
| Timing Warnings | Warnings are now provided that indicated triggers that may occur out of sequence. For instance, if you get a Finish trip before a Start Trip. All trips are managed in sequences, start, 60ft if so configured, then a finish. If the 60ft or the Finish occur outside of that sequence for the running entry, a warning is generated. |
| Live Timing Results |
New Behavior has been put in place.
|
|
Bug Fixes |
|
|
Staging Re-fresh Entries |
|
| Networking | In the Synchronization stage, the HTML Style sheet was accidentally set to the Announcer Style sheet. |
| Re-Classing | Using Re-Class from inside Insert/Edit Reg Entry - could fail...the source entry was not correctly selected. |
| Version 17.50 - Sep 2017 |
|
AXWareProTS - Major Update - New Features |
|
|
Enhancements |
|
| Staging Pax Entries |
Since AXWareProTS was designed for Session control and Challenge Classes,
Pax classes were not properly managed in the staging grid, especially
with respect to Run Numbers. As of this version, pax classes are treated similarly to AXWareTS |
| Announcer Windows | Improved several display components in the Announcer Window, including Combined Time, Top Time and Top Pax indicators. |
| Final Reports | For Pax Classes the Pax Time + the Raw Time are printed in the Total Column for easier viewing. This is opposite normal classes where the Total Time + the Pax Time is provided. |
|
Staging Grid |
|
| Networking | Added the Membership File to the Network Synchronization process so that all of the data is present on the Client. |
| New Print TTOD? Option | You may now select to print the TTOD information for reports or turn if off. Option is in Print Options |
|
Bug Fixes |
|
| Staging Grid - OFF penalty |
OFF penalty could at times not affect the recorded times. OFF
penalties are provided to allow you to terminate a timer when a car
cannot finish their run (cannot cross the finish line), or missed the
lights for whatever reason. For running timers, a prompt will appear to kill the selected Timer. |
|
Staging - penalties |
Penalties, DNF's especially force the Run # in a session to be reset, an
incorrect behavior. Workaround: was the Run to be Forced to the Current Session #. |
| Version 17.10 - Mar 2017 |
|
Major Update - New Features |
|
| AXWareProTS |
|
|
Enhancements |
|
| Announcer Window |
Vehicles on course offer more information in the On Deck and Run History
areas. Vehicles on course are tagged with "On Course" in the On Deck are
and "Running" in the History area...providing more information during
their runs. The vehicles On Deck are moved out of the On Deck area
once a run is completed. Reset Finish and Killing timers results in proper vehicle sequencing. |
| Membership File & Events | The linked membership is now validated in a more explicit manner providing better control of program settings when membership files build with prior versions are loaded and may have outdated settings. The settings are now forced to default values that potentially improve program stability. Prior to this, old membership file could force out of range values and cause the software to crash. |
|
Bug Fixes |
|