Salut
Voici un nouveau HUD totalement param?trable, r?alis? par CTDP
http://rapidshare.com/files/382215431/rfDynHUD_v1.0.zip
This is the help readme for rfDynHUD and the rfDynHUD Editor.
rfDynHUD means rFactor Dynamic HUD. (Please don't call it "That new TV-Style" or something like that.)
It is a new, feature rich, configurable and extendable dynamic HUD system for rFactor. It is configured through ini files, which are created and modified using the provided editor, which is kinda self-documentary. Please read the following clauses carefully. We will happily answer all your questions, if you got some, but please avoid asking things explained here.
Configuration files - overlay.ini
The "config" folder contains rfDynHUD configuration files.
The plugin supports individual configurations for each mod, car and session and even specific ones for being in the garage. If no specific configurations are found, the default configuration will be used. This default configuration is expected in the "config" folder under the name "overlay.ini". Use the editor to create a valid configuration of your preference.
Mod-specific configurations are searched for in subfolders named like the mod. So if you want to create a specific config for the "F1CTDP06" mod, you have to save the config file in a subfolder of the config folder called "F1CTDP06" and config file is to be named "overlay.ini".
If you want to use an individual configuration for a car, which's class is called "CarClass" of the Mod "MyMod", the config file must be stored as "MyMod\overlay_CarClass.ini".
To use session-type specific configurations, you have to insert the session type identifier into the name as the last part.
Valid identifiers are:
?TEST_DAY
?PRACTICE1
?PRACTICE2
?PRACTICE3
?PRACTICE4
?PRACTICE
?QUALIFYING
?WARMUP
?RACE
PRACTICE is a wildcard for PREACTICE1, PRACTICE2, etc.
Please refer to the log file to know the names of the mod and car, if you don't already know them.
The search order, if the mod is "F1CTDP06" and the car is "F1 2006" and the session type is "PRACTICE3", is the following:
1.F1CTDP06\overlay_garage_F1 2006_PRACTICE3.ini
2.F1CTDP06\overlay_garage_F1 2006_PRACTICE.ini
3.F1CTDP06\overlay_garage_PRACTICE3.ini
4.F1CTDP06\overlay_garage_PRACTICE.ini
5.overlay_garage_PRACTICE3.ini
6.overlay_garage_PRACTICE.ini
7.F1CTDP06\overlay_garage_F1 2006.ini
8.F1CTDP06\overlay_garage.ini
9.overlay_garage.ini
10.F1CTDP06\overlay_F1 2006_PRACTICE3.ini
11.F1CTDP06\overlay_F1 2006_PRACTICE.ini
12.F1CTDP06\overlay_PRACTICE3.ini
13.F1CTDP06\overlay_PRACTICE.ini
14.overlay_PRACTICE3.ini
15.overlay_PRACTICE.ini
16.F1CTDP06\overlay_F1 2006.ini
17.F1CTDP06\overlay.ini
18.overlay.ini
The "_garage" block is skipped, when leaving the garage.
If none of them could be found, the built-in factory default configuration is used.
Unfortunately we had to use a unique vehicle class for all cars for the "CTDP F1 2006" mod. So this mod doesn't support special configurations for any car.
Configuration files - three letter codes
The "config" folder also contains the three letter codes configuration file used by the StandingsWidget and others. This file keeps mappings for known driver names to short forms (not necessarily 3 letters), that can be displayed instead to save some room on the screen. The file is accessed as "three_letter_codes.ini" and has entries of the form:
Rubens Barrichello=BAR
Michael Schumacher=Mich
Pedro De La Rosa=DLR;P. d.l.Rosa
As you can see you can also separate a second short form by a semicolon from the actual three letter code. This short form is normally generated. But for some names it can be usefull to define it yourself.
Configuration files - input bindings
Another file, searched for in this folder, is the "input_bindings.ini". It keeps mappings of key-strokes or button-presses to input actions on named Widgets. Use the InputBindingsManager from within the editor to generate and maintain that file.
Editor - Different backgrounds
You can change the editor background images, so that they look like you use to see your rFactor. Do this by creating one screenshot for each of the resolutions, that you see under the "Resolutions" menu (menu bar). If you're lazy, just create a screenshot for the resultion, that you want to use in the editor. But we encourage you to create a complete set of screenshots and send them to us, so that we can provide them as additional downloads.
After you created those screenshots copy them to a new folder under the editor\backgrounds folder in the plugin folder. There you'll find a folder called "default", which contains the default screenshot-set. Now select the new set from the properties editor to the right after deletecting any Widget.
Editor - Basic workflow
Add a new Widget by selecting an entry from the Widgets menu.
Remove a widget by selecting it with the mouse and then either pressing the DELETE key or choosing the "Remove selected Widget" entry from the Widgets menu (last item).
Position or scale a Widget by either dragging it resp. its borders with the mouse or by changing the appropriate properties in the properties editor on the right side of the editor.
Positions and sizes can either be given in absolute pixels or percentages. Only use pixels, if you're creating a private configuration and never plan to switch your game resolution.
If you want to share your new configuration, you must use percentages for both position and size. Otherwise your configuration will look different on different screens and resolutions.
You can change the default, that is used when a new Widget is created in the options window.
All other properties are only configurable through the properties editor. Select a Widget with the mouse and then modify the properties as you like. Every single property is documented. So if you want to know more about a specific property, select it in the properties editor and the description will be displayed in the panel below.
Templates
It is possible to define templates for any Widget type. This is simply done by storing a Widget configuration file containing one Widget of any kind. Then select the configuration file for the "templateConfig" property in the property editor to the right after deselecting any Widget.
Screenshots
You can create screenshots from your currently displayed configuration. Select "Take Screenshot" from the "Tools" menu. This will create a new image file in your "UserData\ScreenShots" folder.
Have fun!
Source : www.live-simracing.com
