There's been a couple of requests coming in for us to better document the API that we provide for the users of R3E. In case you weren't already aware, the game client currently creates a block of so called shared memory when starting up, which allows other applications on your computer to read certain data that we expose through this memory block. A few examples of the types of data exposed: Data about the car, such as gear, RPM, speed, DRS, etc. Data about the race, such as position, lap times, etc. High-precision data about the player, such as physical position/rotation, G-forces on the driver, etc. This API has already been used by a couple of third-party applications and hardware manufacturers to allow R3E (and some older SimBin titles) to be used with stuff like this: SimXperience motion rigs Sensadigit's DashMeterPro Siminstrument's Dash EKSIMRacing's SLIMax Manager As a first step, I've written a small sample application to allow you to clearly see the layout of the memory block and to help you get started. This particular sample is written in C, which seemed appropriate considering its wide interoperability with other languages. I could put up samples in other languages if anyone would be interested in that. You can find the layout and sample applications here on GitHub. Feel free to come with suggestions on stuff you'd like to see added to the API, either here on the forum or on the GitHub issue tracker EDIT (21/6/15): Added a C# sample to the GitHub repo. EDIT (12/7/15): Added a bunch of new entries to shared memory (with some caveats). EDIT (1/3/17) - New minor version is 3. - Added new entries for extended flags. - Changed how tire wear is reported so it now matches the % shown on the new data displays.