Everyone knows that there are millions of cool things you can do with your mobile phone. Watching movies is old already. The latest and coolest thing is to play mobile games. Play roulette, blackjack, slot machines or other cool games, and hit the jackpots for real money.
Server costs per
Month To maintain the site we need to raise funds each month to pay for the server.
The cash is gathered via Donations. However each month the incoming money falls
short. If you want to make sure that the site survives then please donate!
Thanx to nowarez
Version 0.90 or earlier needs to be uninstalled before installing this new beta version! This can be done by pressing delete key on the application icon. Uninstalling does not remove your saved sessions and tracks. A version 0.91 or newer can be upgraded normally.
Changes from v1.01 beta to v1.02 beta:
1. In-build accelerometer output logged to NMEA file on some phones. Sorry, the data is not used in anyway yet. Such phones as Nokia 5500, N82, N93i, N95, N95 8GB etc. should be supported by this feature… If you want to log proper acceleration data to your NMEA, please fasten your phone securely while driving (to a cradle maybe). This NMEA can be then be re-loaded afterwards when RaceChrono starts using this data somehow!
2. Fixed: Internal GPS stability.
3. Fixed: OBD gauges not refreshed when no fix to satellites.
4. Fixed: Broken OBDKey support (v1.01 beta)
Changes from v1.00 to v1.01 beta:
1. CSV export format now exports more data, such as X and Y-coordinates in meters, Longitudinal and Lateral G-forces, and Bearing. Also coordinates format is changed from GPS-style to decimal degrees.
2. CSV export format (with standard separators) can now be used directly with directly with TrackVision. Notice that the RaceChrono_MPH.properties and RaceChrono_KPH.properties needs to be copied to the “loggers” directory under the folder “C:\Documents and Settings\All Users\Application Data\Apex Visualizations\TrackVision\loggers” on your PC (or which ever folder has your Track Vision configuration data…).
3. Dropouts in GPS fix to satellites, or GPS connection are drawn with dotted line to the maps.
4. GPX export now writes Bearing, HDOP, VDOP, PDOP and fix quality (DGPS/GPS).
5. Improved graph viewer. Only two y-scales are shown, one right and one left, to avoid clutter. The channel graph color is now picked in order of channel selection; first picked channel gets green, second yellow, etc.
6. Lateral and Longitudinal G-forces calculated from GPS data can now be viewed in graphs. Note that the Lateral G-force graph is a bit rough for sessions recorded with older versions, but is better with sessions recorded with this version.
7. GPS Bearing is now saved in to the session file. This data can now be viewed in the graph. For older sessions the bearing is calculated from the position data (not as smooth as the real bearing).
8. Fix quality (DGPS/GPS) is now saved to the session file.
9. Coordinate precision (HDOP), Altitude precision (VDOP) and 3D precision (PDOP) are now saved in to the session file. They can be also viewed in the graphs and gauges. Especially the HDOP is useful when analyzing the reliability of lap times.
10. PerformanceBox (*.dbn) and VBox (*.vbo) session import now reads the session creation date in order to calculate the date for the laps (if the file has been edited with Performance Tools, the date will be the edit date).
11. Toggle button on sessions list changed to star-key as the #-key is needed to toggle marked status on some phones.
12. Improved marked sessions deletion. One confirmation question instead of many.
13. Fixed: Support for Alpha-Bid’s Bluetooth OBD-II reader.
14. Fixed: Graph hanged when some OBD-II values when over certain threshold, for example RPM over 8192.
15. Fixed: Removed a duplicate channel “Oxygen sensors”.
16. Fixed: Could not edit driver name when clean install of the software.
17. Fixed: Extra open tags when exporting GPX in “traveled route” scope.
18. Fixed: OBD-II timestamp generator was not reset on session start/resume.
19. Fixed: OBD-II timestamp was incorrectly dependant of the system clock. Any change to the system clock caused it to go out-of-sync.