In the User Manual, there is a mistake in the description of trackPos sensor (“right” and “left” are swapped). Many thanks to Ho Duc Thang who found this error in the manual. A corrected version of the manual has been put online (download it here).
Computational Intelligence in Games
A preliminary scoreboard of the example controller is here. The score of controllers is computed as the distance raced by the controllers over three different tracks (in the final scoring process a different set of tracks will be used) within 10000 game tics. Submit your entry to get it scored!
A new version of the C++ Client is out. Download it here.
In this version:
- fixed a bug on race restart (the driver class is no longer de-allocated at each race restart)
- it is possible to specify the maximum number of control steps and the maximum number of learning episodes with command line options (check the User Manual)
In this version we fixed a little bug in the computation of the distRaced sensor.
In addition we developed a new sever, called wcci2008trainer , with a very “gentle” timeout on the client answers (10 seconds instead of 10ms). We strongly suggest you to use this bot to develop/learn your bot especially if you are working under Windows and with “results only” display mode. In fact there are some issues related to the timeouts under Windows when “results only” display mode is used. However, before submitting your entries be sure that your bot works properly with the strict timing requirements (i.e., 10ms) at normal speed (i.e., “normal” display mode and speed 1X). Final evaluation will be performed using the strict timing constraints at 1X speed.
To install the new server package
- under Windows: copy the update patch in your main TORCS directory and unzip it (answer “yes to all” to overwriting questions).
- under Linux: compile and re-install the wcci2008competition bot and compile and install the wcci2008training bot following the User Manual instructions.
With plenty of assistance from Matt Simmerson, Daniele and me have now managed to solve some outstanding problems with the competition software. In this new version of the Java client software (downlad), the following are the main changes:
- The client now tries resending information in case it does not get an answer from the server within a short time. This solves some problems with multitasking and networking on Windows.
- Evaluation automatically stops if the car’s damage counter goes above 5000. This is done to avoid TORCS shutting down the race itself (which it would do in cases of damage over 10000, and which would stop the serverbot listening).
- The distanceRaced value (suggested fitness measure) is now “throttled” so that it cannot increase or decrease too much in any time step. This removes an exploit that evolution found earlier on, which had the car crossing the start/finish line twice just after starting, erroneously adding a full lap to distanceRaced.
- The fields in the Action class are now all public.
- The default number of time steps in the SoloEvaluator are increased to 3000, on order to allow for more meaningful evaluation. In the final scoring we will likely use evaluation lengths of 10000 steps.
Usage instructions is just the same as for the last version. Go ahead and try it; you find any additional problems, please let us know!