Data Acquisition for Motec Plugin (DAMPlugin) V0.81 This plugin generates Motec i2Pro compatible log files. This is not a Motec product - do not contact them for assistance! Automatic Installation (preferred) - manual installation down the bottom if you get a virus warning: Download the DAMPlugin Handler .zip file attached, run the included DAMPlugin_Handler program (it will request Administrator access) and follow the instructions to 'install' it. In DAMPlugin_Handler, Add an rF2 folder, then Install the plugin to it. The required sound files will also be installed to your rFactor 2 data folder. To update an older version of the plugin, you need to click Uninstall, then Install. Now start rFactor 2 (single- or multi-player) and the plugin will be active with default options. Quit rF2 and you'll find a DAMPlugin.ini file in your UserData\player folder with options you can change. Some options are detailed below. Telemetry Marker With the plugin installed, in rF2's Settings -> Controls -> Devices menu you'll find a Telemetry Marker option. Bind this to a key or button and when you press that control while driving the plugin will place a marker at that time. You can press multiple times to record different values, so for example a double-press will be recorded as a '2' in the log. The time/location is only accurate to 1 second, and only one marker per second can be recorded. DAMPlugin.ini options: This file will be created in your player folder when you start the game with the plugin installed. Multiple player profiles will generate their own .ini files. By default: Logging is enabled on startup (Ctrl-M toggles logging, when in the car) The current garage setup is saved to the log folder (same name as the log itself). Logging status is announced in a male voice. Female voice and my Beeps are also available. Data is collected at default rates, precision and range, which should be fine for general purposes. No 'extra' channels are logged, to save file space. The DAMPlugin.ini file has comments all through it. These should be the first reference for the options available. Here is more info on some of those options: Channel Configuration The global Data rate option sets the frequency of logged channels. The default value of 3 results in useful rates suitable for general purposes. For better fidelity try 4. A setting of 5 will log everything at full speed which probably isn't required, while the low settings of 1 and 2 will limit some analysis. Higher settings will produce bigger log files. Base Channel Config: Each of the 5 base channel groups can be recorded in 3 different modes: normal, extra-precision, and high-range. Settings other than 1 will produce larger log files. Normal (1): standard precision and value range to suit normal use. Extra precision (2): A similar range of value as normal, but extra precision for more accurate logging. An example use of this is fuel consumption rate, which can be logged quite smoothly instead of requiring aggressive smoothing in i2Pro. High range (3): some vehicles or environments may produce higher than normal data ranges. A large truck, for example, could produce suspension positions that are outside of the normal working range and would lead to wraparound without this option. Extra channel config: A number of extra channels are also available, which are divided into groups. These may be useful for specific analysis types but are perhaps a little advanced for basic purposes, while some others are really just logged because they're available without any real use I can foresee. Full channel list: https://forum.studio-397.com/index.php?threads/damplugin-for-rf2.49363/page-2#post-819448 You need to enable any of those groups you wish to log by changing the corresponding value from 0 to 1, 2, or 3 (as described above). Notifications The plugin comes with Male, Female, and Beeps folders containing the various sounds used to indicate logging status. Custom sounds should be placed in their own folder(s), following the same file naming convention as the included files. Avoid using the standard folder names for your own sounds, to avoid overwriting them when installing the plugin again later. You can enable message center notifications (so a text message on the message center will tell you when logging is enabled or disabled) but bear in mind this is only visible when in the car. Compatibility: The log files are compatible with any recent versions of i2Pro. Very old 1.0.0x versions will have lap timing issues, plus various other bugs. Upgrade! Known Issues: Data is collected during driver swaps, but due to an rF2 bug the logs aren't built until exiting the game. The same thing also happens offline when restarting a race during the formation lap (at least). There are base channels under Scoring and Wheels but I forgot to add those to the config. I'll fix that next time! (the defaults should be fine anyway) Anticipated frequent questions: Do I need to run DAMPlugin_Handler every time for the plugin to work? No. I'm distributing the plugin this way to reduce incorrect installation, and the handler makes it easier to install/uninstall (it 'finds' the data folder automatically). But you don't need to ever run it again after the plugin is installed. Can you just give me the plugin files? I'll install them myself! It really is easier to just use the .exe. Honest. It even finds the last rFactor 2 installation folder, so most people won't need to select it manually. No rF2 files are modified. But I really don't like running strange programs! Ok, first: Every plugin you download and use is like a mini-program, it just happens to be attached to rFactor 2. If you are very security conscious (or paranoid) this may make you think twice about downloading strange plugins. Second: If you really want to, you can grab the plugin files and package them up for yourself or friends / league members. I know leagues often like to combine multiple plugins this way. I could have stopped the plugin working in this scenario but chose to leave it open. You take responsibility for getting the plugin installed correctly if you do this. I won't appreciate if someone comes here for help with the plugin not working and it turns out you didn't install it correctly for them. Manual Installation (if the automatic doesn't work please let me know so I can try and fix it) Try the auto install first! Grab the ManualInstall archive attached to this post. Put the .dll file(s) in their corresponding folders in your main rF2 install folder. Extract the PluginData folder to your rF2 data folder so the sounds work. If it doesn't work, check you're putting the files in the correct folders. If it still doesn't work, maybe try the automatic installer and see how it does it. Did I mention it's easier?