Search the Community
Showing results for tags 'never_eat_yellow_snow1'.
Fonte stracker and ptracker stracker and ptracker are apps for the race simulator Assetto Corsa. stracker is the server-side portion and ptracker is for the client side (i.e., it runs in the game). Both apps aim to improve your online experience. It is not required to always have both instances running - stracker can be used without all drivers using ptracker and vice versa. However, you get the best experience when both are running. ptracker Main Window The client app provides a window in the game with 3 sections: The hotlap section, the leaderboard section and the message section. Each section is highly customizable, you decide about the information displayed on your screen. The hotlap section shows information about the current lap. The hotlap line is shown here in its default configuration: Live delta / lap time / pit time display Lap validness display (green: lap valid, red: lap invalid) Split delta Sector delta Connection status (gray: not connected, green: stracker connection established, yellow: setup available for download) Session progress (qualification/practice: time left, race: <current lap>/<number of laps>) Fuel indicator (gray: fuel for more than 3 laps left, yellow: fuel for 1 to 3 laps left, blinking: less than 1 lap left) Fuel prediction (number of laps left). ('-' if no fuel prediction is available) The leaderboard section shows the current leaderboard with current rank, car badge, tyre, name, relative deltas, best lap times and more. The message section shows chat messages and messages from ptracker and stracker, such as personal best lap times, server best lap times, players entering and leaving the server, etc. The message section can be detached from the other two sections, so that you can place it independently on your screen. Chat functionality ptracker has a chat feature built in accessable with hot keys. You can open a chat editor by pressing Alt+T (of course you can change the keys in the configuration dialog). There are 9 predefined messages mapped to the number pad keys 1 to 9 (NumLock has to be enabled): 7 hi 8 thank you! 9 bye 4 good race 5 good pass 6 sorry 1 2 3 Dialogs Additionally, there is a dialog with more detailed information and customization. You activate this by either double clicking on the hotlap section or by a single click on the connection icon. The dialog can be closed by clicking on the icon in the top left. The dialog has the following sections: The Lap Stats section shows information about the best laps achieved. The information is either gathered from a database on the client machine, or (if available) from stracker. The information source is indicated in the lower right. You can set various filters in this dialog. You can click on a lap to get more detailed information. You can navigate through the ranking with the buttons on the lower screen (go to top, one page up, go to my rank, one page down, go to bottom). Similarly, the Session Stats section shows information about recent sessions. The Config section is the central place to configure the behaviour of ptracker. You have loads of possibilities to change the behaviour. The Setups/Players section provides an interface to share setups in various ways. This functionality is limited for servers running stracker. Server admins may also use this page for kicking bad drivers. The Database section provides an interface for controlling the local database. Performance During the development of ptracker, a lot of effort has been spent to make it as efficient as possible and to keep the in-game FPS as high as possible. This is the reason why ptracker is split up into two parts, a normal python app running in the Assetto Corsa game and an exe file which is automatically started from the python app. stracker The server-side app automatically stores all laps, sessions and drivers in a database on the server. It can provide web pages with interesting information for access with a browser. See the NEYS AC server statistics for an example. HTML Output The HTML output of stracker features the following items: Lap Times. Ranking of a track/car combination with various filters (accessable by the '+' button). You can click on any lap to get more detailed information. Sessions. History of sessions. You can click on any session to get the leaderboard information. Furthermore, clicking on a driver in the leaderboard provides you with the laps of the driver, and of course you can get the details for all the laps. Drivers. List of all drivers seen on the server. Championships. Championship ranking (for leagues). Statistics. Server statistics. Live Map. Live view of current server activity. Admin Area. Admins can access this area for performing a number of tasks: Manual lap invalidation, e.g., when there were cheaters online. Driver management (adding to banlists, etc.) Championship management. Group management. General administration. Multiserver support A lot of communities offer multiple AC servers. stracker supports these setups with flexible configuration options. You choose if you wish to keep all servers in one database, or have a seperate DB for each one. Database backends There are two database backends supported: sqlite and postgresql. While sqlite has its strengths in its ease of use, the postgresql database is a natural choice for larger setups. You can switch between these database backends at any time. DOWNLOAD http://n-e-y-s.de/download
App to display tyre temperatures and pressures automatically adapting colors to optimal temperature range for most builtin cars. Current version: 1.6.2 -> tyre_temp-1.6.2.zip FAQ: If you have questions about the nature of the values displayed by this app or how the tyre physics works in general, please read the thread http://www.assettocorsa.net/forum/index.php?threads/tyre-temperatures-and-wear.2723/ before posting here. Most questions have already been discussed there. How to configure the app for custom temperature ranges Since version 1.6.0, the app can be configured to display custom temperature ranges for specific cars / car classes. Therefore you will need the files <assetto_corsa_install_dir>/apps/python/tyre_temp/tyre_temp.ini <your documents>/Assetto Corsa/logs/py_log.txt A) Set the class of an unknown car If the app displays the tyre "unknown" for a given car, it might be enough to set the class of the car. Therefore, open tyre_temp.ini and search for the section CLASSMAP: [CLASSMAP] ; Set the class of a specific car (as listed in content/cars). Known classes are GT2, GT3, EXOS125, F1_1986, F1_1970, F1_1967, FAB. You can also create new classes here. ks_corvette_c7r = GT2 ; Set the class of a specific car (as listed in content/cars). Known classes are GT2, GT3, EXOS125, F1_1986, F1_1970, F1_1967, FAB. You can also create new classes here. ks_nissan_gtr_gt3 = GT3 To add a car to an existing class, add a key/value pair just like in the above example. The key must match the directory name of the car under <assetto_corsa_install_dir>/content/cars (use small letters!). Set or override the temperature mapping of a given car / tyre combo This can be done by following this step-by-step guide: Start the game with the car selected. Choose the tyre you want to configure, click on drive and exit the game again. Open py_log.txt with a text editor (e.g., notepad) Search for a line like tyre_temp.py[iNFO ]: Temperature mapping found: car name 'bmw_m3_gt2', class/tyre name 'GT2 Slick Soft' or tyre_temp.py[iNFO ]: Car name 'bmw_m3_gt2', class/tyre name 'GT2 Slick Soft' The interesting part here is the "GT2 Slick Soft". The first part of this name is the class the car is currently mapped to (here GT2), or STD, if no specific mapping is used. The second part "Slick Soft" is the name of the selected tyre. To add a temperature mapping for this tyre, add the following lines to the section [TYREMAP_OVERRIDES] in tyre_temp.ini: tyre_2_class = GT2 tyre_2_tyre_name = Slick Soft tyre_2_display_name = myGT2Softs tyre_2_opt_temp_max = 50 tyre_2_opt_temp_min = 20 Note that the mappings must have indices starting from 0. In my case I already had two other mappings tyre_0_... and tyre_1_..., therefore I have used the tyre_2_... prefix for the mapping. tyre_2_class must be set to the class reported in the .ini file. tyre_2_tyre_name must be set to the tyre name reported in the .ini file. tyre_2_display_name must be set to a unique name used for displaying the tyre in the app (It must be different to any other tyre name!). min and max temperature are defining the optimum temperature range. To verify that everything works, save the .ini file, restart the game and check if the temperature mapping is used as expected. If it is not used, inspect the py_log.txt file for errors and warnings and try to correct them. You should see a line tyre_temp.py[iNFO ]: Registering temperature overrides (20-50) for tyre 'Slick Soft' of class 'GT2' displayed as 'myGT2Softs' matching your customization Hint: If you rename the .ini file to another file name, the app will regenerate a new ini file with default settings. Changes in 1.6.0: Looks like there are no updates from KUNOS regarding the optimum temperature ranges of newly added tyres (the thread hasn't been updated since adding La Ferrari). I tried multiple times to beg for this information, but the devs do not seem to care. Because of that, and because of the great spectrum of mod cars out there, I decided to make it possible to customize the optimum tyre temperature ranges by editing the tyre_temp.ini file. I hope the examples in this file are speaking for themselfs for the interested users. If something goes wrong, please try to rename your tyre_temp.ini file before posting a bug report to see if the app works with the default settings. Change Log: fix formula abarth hard tyre typo add ferrari_458_gt2 to GT2 class make tyre temperature ranges customizable via .ini file editing (edit tyre_temp.ini beneath tyre_temp.py for that; generated after first app start) improve wear display accuracy (use the inverse display option in tyre_temp.ini) add an auto-hide mode for the tyre type label. In this mode, the tyre type will not be hidden if it is actually unknown. There are still the options to always hide it and never hide it (look at the .ini file) 1.6.2 compatibilities with AC v1.3 fonte AC Forum