EzioDash

A simple dashboard for Gran Turismo 7

Ever wanted to use your iOS device to see telemetry data from Gran Turismo 7? Now you can – and it's free!

Go to App Store Watch Video

Scroll for more information.

About EzioDash

EzioDash is a simple iOS app to capture and display telemetry data sent from the PlayStation game Gran Turismo 7. As such, your iOS device must be on the same local network as your PlayStation console. Naturally, your iOS device most likely connects via wireless (WiFi), but your console may connect either by wired connection or wifi. You do need to go into the network settings of your PlayStation console to find its IP address, which needs to be input into the app.

EzioDash is DonationWare.

EzioDash requires iOS 15 or higher (iPhone 8 or higher recommended).

Disclaimer

First and foremost, there is no guarantee that this app will work. The telemetry from Gran Turismo 7 is an undocumented feature, reverse engineered by brighter people to enable the rest of us to enjoy this. That said, there is no guarantee that this feature of the game will remain accessible to the public forever, and if it should be removed, changed or otherwise locked, this app will cease to work.

Also, note that the app you download may differ in visuals slightly.

The app consists of 5 different screens

Please note that the screens may differ slightly from the current app version, but as a whole it should be similar enough.

Rather than having a user interface with a lot of buttons, I have opted to instead have separated screens where you swipe left and right to go to the appropriate screen.

To navigate between these screens, simply swipe left and right. When starting the app you will go to to the third screen; the connection screen. From left to right in the app, the screens are; about, settings, connection, full dashboard and simple dashboard screens.

  • This screen is simply an "About" screen, with info on the app version (top right), donation link, contact info, some info on the app and the game, a bit of credits to various people somehow involved in the birth of the app, beta testers and so on.

  • This screen shows the settings that are available to change, like for example changing between metric units and imperial units.

  • 03 The connection screen

    This is where you arrive when the app starts. This is where you enter the IP address of your console and where you connect/disconnect. You will also find a small image of Ezio, our italian greyhound, who gave name to the app.

    From here you can swipe right to the settings screen, or swipe left to the dashboard screen.

  • This can be considered to be the main screen of the app. This is where you can see the telemetry in a dashboard-like fashion.

  • This is a simplified version of the full dashboard, focused on the tyre status and fuel information. There is also information on top speed, average/median lap times and time of day on track.

 

Telemetry

Of course telemetry does not necessarily make you a faster driver, but it can provide you with more information about your driving.

Top speed

Compare top speeds of various cars when it suits you, without having to watch the in-game speedometer.

Fuel usage

Keep better check on how much fuel you are using, and how far you can go on the fuel you have left.

Tyre temperatures

Managing your tyres is a very important for good results, EzioDash lets you know current and average tyre temperatures.

Lap comparisons

EzioDash lets you keep track of your average lap times for comparison, only counting your flying lap times.

Download from the App Store

EzioDash is available to download from the iOS App Store, giving you the best user experience and easy updates.

Requires iOS 15 or higher, and should also work on iPads in landscape orientation.

Get EzioDash from
the App Store

How to use EzioDash

Using EzioDash is pretty straightforward, but here is a short "how-to" (note that the app you download may differ slightly visually):

Connection screen

The connection screen is the first screen when you start the app:

Please note: screens may differ slightly from the current version.

Making a long story short; this is where you enter the IP of the PlayStation console running Gran Turismo 7 that you want to connect to. Take care to enter the address exactly as shown in the network settings of your PlayStation console. If the address is valid, the "CONNECT" text will light up white. Tap the "CONNECT" button and the app will start trying to connect to your game. When connection is established, the text beneath the address field will change to "CONNECTED" and the thin bar will be colored (green denotes a good connection). You can now click the right arrow or swipe from right to left to change to the dashboard screen.

Read more

Settings screen

The settings screen is where you will change settings:

Please note: screens may differ slightly from the current version.

Here you will find settings that enable you to for example choose metric or imperial units (separate toggles for speed/distance and tyre temperatures), enable the keep-awake feature, disable the demo mode that is enabled by default and so on.

Read more

Full dashboard screen

The full dashboard screen is the main screen when using the app:

Please note: screens may differ slightly from the current version.

A quick run through of the elements; top left is the connection status bar (same as on the connection screen), followed by the RPM indicator bar. Top right is the on-track time-of-day (changes according to time progression). Left hand side contains current and top speeds, along with distance travelled. To the right of this is the throttle and brake indicator bars, with the current gear and RPM readouts in between. Beneath this is the fuel bar, with the fuel consumption info underneath. To the right of this is the tyre temperatures, indicating the average and current temperatures. Far right is the current lap, last, best and average lap times.

Read more

Simple dashboard screen

The simplified dashboard screen can also be used as your main screen:

Please note: screens may differ slightly from the current version.

The simplified dash focuses mostly on tyres and fuel. The front tyres are up top, the rear tyres at the bottom, with the fuel information in the space between. Additionally, on the right hand side is the connection status bar, the current top speed achieved, the average (or median) lap time (plus possibly the cutoff lap time), and last but not least the time of day on the track.

Not shown: Current version also displays the current lap, between the top speed and average/median lap time.

Read more

About screen

The about screen contains some further info and credits:

Please note: screens may differ slightly from the current version.

Here you can find the donation link, a link to this page, a short informational blurb and legal information with regards to the Gran Turismo and PlayStation trademarks. Here is also a list of people that have been instrumental in one way or another in getting this app to where it is.

Frequently Asked Questions

Here is a collection of answers to questions you may have:

  • Why won't the app connect to my PlayStation console?

    Follow these points to try to resolve the problem:

    • First and foremost; check that your IP address is correct in the app – compare with what your console is showing in the network settings.
    • Make sure that the iOS device and the PlayStation console is on the same local network. You need to be on a wifi network with the same IP address range as the console (preferably the same local wifi network, i.e. same SSID, if the console is also on wifi).
    • Other possible network issues may of course occur, but that is beyond this FAQ and most likely something related to your network environment.
    • Make sure that Gran Turismo 7 has loaded, it must have reached at least the initial news screen where you select "World Map" before it connects.
    • Sometimes the ports used for the telemetry can be blocked for an indefinite amount of time. Seemingly, there is no need to restart the game, you just have to wait it out.

  • The simple answer is that since the app is meant to be used continuously while playing, with the screen active, it seems prudent to disconnect and stop all activity if the app is put in the background either by iOS itself or from putting the iOS device to sleep manually. Use the Keep awake setting to prevent the device from going to sleep by itself.

  • The dashboard will only show telemetry while you are either on track or having entered a race in a lobby. And, you do need to be connected to the game, of course. For replays, you must currently manually enable the (experimental) replay mode support for telemetry in the settings.

  • There are a number of network-related issues that can influence the connection between the app and the game running on the PlayStation console. This is beyond the scope of this page, but it can be a good idea to test the app and the connection quality in a situation where you are certain that no other devices on the same local network are congesting the network traffic in any way.

    Other than that, it is possible that older iOS devices are unable to keep up with the telemetry, indicating a lower quality connection. This does not mean that the app won't work, but it may update less frequently. Your mileage may vary, and you will have to evaluate if it "works" or not, for you.

  • Due to the nature of the app where it needs to update the dashboard up to 60 times per second, the energy consumption increases and with that comes the heat. There is not much that can be done about this, but we recommend that you keep the iOS device connected to wired power to keep the heat from a discharging battery to add to the heat.

  • At least for now the app won't work on replays from scratch. You must manually go into the settings screen and from there you need to enable the experimental support for displaying replay telemetry data. DO NOTE: the telemetry from replays is NOT 100% the same as what the live data was! This is most obvious if you look at the fuel gauge during a replay; you will most likely see that the amount of fuel left "jumps" up and down a bit.

  • This app was not written as a customizable dashboard, and it is unlikely that the app in its current form will allow for any customization.

  • There are a few instances where the dash will reset. This is on purpose. For example, while you are in a lobby and have entered the race (i.e. you have clicked the green checkmark or you have entered the track) the dash will not reset. But as soon as you are considered to be "in the menus" so to speak, the dash will reset. For example, in a lobby, while you are entered, the dash will not reset. However, if you click the red cross button to exit the race (not the lobby), the dash will reset. The reasoning is that you may want to reset the dash at some points, and this is a good way to do it.

  • This usually only happens if you coast a lot at the beginning of your run, or apply the brake while on the throttle respectively. Since the app has no previous data to work with, the percentage of these two readouts go up very quickly. However, it may then take some time to get them down to "normal" levels again, so you can give the gear indicator a quick tap to reset these two readouts (although the same logic will then apply again).

  • The most likely culprit here is that some tracks have pit lanes that aren't at the start/finish line. One example is the Tokyo Expressway South layouts, where the pit lane is in a parking garage some 1/3 of the total track distance (depending on what direction it is) from the start/finish line. For obvious reasons this messes up the fuel per lap percentage, but it will gradually correct itself as you lap around the track.

  • No, this app has no such functionality at the moment. There is other software aimed at solving that kind of problem. Besides, even if the telemetry is only 296 bytes per packet, it sends a new packet 60 times per second. To add to that, a human usable data file, for example a CSV text file, needs more space. And even unpacked, that amounts to 60 megabytes per hour. Not a lot, but it would also involve functionality for the app to manage those recorded sessions.

  • No, there is no way to get the game to send another player’s telemetry.

  • No, there is no portrait mode. The app is only available in landscape mode.

  • Ezio is our italian greyhound, born in the year of the pandemic, 2021. Italian greyhounds are not the most common breed of dog, for sure, but they are one of the most charming beings you can find. My family have had iggys (from the acronym IG) since 1984.

  • Sure, you can download a ZIP-file containing SVG files that you can upload to the game (see "Decal Uploader" in GT7 documentation) and use as decals on your livery. You can find the ZIP file here: https://granturismosport.se/eziodash/eziodash_logo.zip

Connecting EzioDash to your PlayStation

This section describes how to setup EzioDash together with your PlayStation console running Gran Turismo 7

There are several elements on the connection screen, but the main one is where you enter your local IP address of your PlayStation console. Tap the input box and enter your IP address, for example you can enter "192.168.0.128" (without the quotes) if that is the IP address of your console. Once entered, the app will remember the last used IP until you change it.

Note: To find the IP address of your console, you need to go into the network settings of your PlayStation where you can select a menu option to view your network connection. Note the IP address, which is likely an IPV4 address with 4 numbers separated by period characters, for example 192.168.1.87 or similar looking. Do note that your address may vary from this example, and that it CAN change from time to time, depending on how your local network is setup.

Once you have entered a valid IP address (the app allows a variety of formats including valid IPV6) the "CONNECT" text button will light up in white text, meaning you can click it to try to connect to the game's telemetry ports.

When you've tapped "CONNECT" the app will start trying to connect, and the status indicator below the IP address will change from "DISCONNECTED" to "CONNECTING". If everything works like it should, the status indicator should change to "CONNECTED" and the bar below should begin to fill up to indicate the connection quality. The status indicator bar should fill up green when the app connects, and if it remains at a steady green color you can assume you have a good connection. A red, orange or yellow bar means that the connection is bad and the app is missing a lot of telemetry packets from the game.

To proceed to the dashboard once connected, you can either swipe left on the screen or tap the large circled arrow pointing to the right to take you to the dashboard screen.

If/when you want to disconnect, you can go back to this screen and tap the "DISCONNECT" text button on the connection screen. The app itself does not disconnect by itself, not even if the game or PlayStation console is shut down. However, if the app goes into the background or goes into standby (by itself or manually) it will disconnect from the telemetry.

Note: If you establish a stable connection and want to use EzioDash continuously, toggling the "Keep-awake" setting will allow the app to keep the screen on indefinitely without changing any UI settings in iOS.

The connection screen is the first screen when you start the app:

Please note: screens may differ slightly from the current version.

The connection status indicator

The connection status indicator is present on both the connection screen and the dashboard screen. On the connection screen it is accompanied with a status text indicating the connection status of the app. On the dashboard screen you will find it in the top left corner, and on the connection screen it is located beneath the IP address input box.

The connection quality is displayed as a bar that fills up and is colored green for a good connection. If your connection quality is low, the telemetry reported by the dashboard may be wrong, or lagging behind. It is therefore important to make sure that your local network connection is as good as it can be.

Telemetry from the game is sent 60 times per second (with minor variations), and there is no guarantee that a telemetry packet is received, or that it arrives in the correct order. Due to this, the app discards packets that are sent out of sequence, as well as counting the number of missed packets. This is the basis for the connection quality indicator. The more missed or lost packets, the lower the quality is considered.

The full dashboard readouts

This section describes the various parts of the full dashboard

The full dashboard consists of multiple elements, which is explained below:

  1. Connection quality indicator. This bar goes from red to orange to yellow to green to indicate the quality of the connection. Normally this should be a full green bar if you have a good local network environment.
  2. Gear shift indicator. This bar is directly connected to the RPM of the car, and corresponds more or less to the in-game gear shift indicator. It fills up from the left towards the right, starting from green through yellow, orange and red and starts flashing between blue and white when it reaches what in the game is the flashing shift indicator.
  3. In-game time of day. This is a 24h clock corresponding to the time of day on the current track. If the game has time progression enabled, this will show the correct on-track time. Note: For tracks that don't have a full 24 hour cycle, this time of day may seem to be stuck, until it switches over to the first morning time of day. This is only applicable in races where the time progression is either high enough to cause a full day cycle to pass, or is long enough to pass from one day to another.
  4. Current speed. This is the car's current speed (in kph or mph).
  5. Top speed.* This is the top recorded speed (in kph or mph). Can be reset by tapping the digits.
  6. Distance travelled.* This is an estimate of the distance travelled (km or mi), accuracy is not 100%. Can be reset by tapping the digits.
  7. Fuel indicator. A simple bar and percentage of fuel left. Note: In races without fuel consumption, this will remain at 100%.
  8. Fuel used per lap.* This shows the percentage of fuel used per lap (only when you've passed the starting line) if fuel consumption is enabled.
  9. Laps remaining.* This shows an estimate of how many laps you can finish based on your past consumption and fuel remaining.
  10. Time remaining.* This shows an estimate of how many minutes and seconds you have left, based on an average lap time (which can be reset).
  11. Brake indicator. This indicator bar shows how much brake input the game is getting. Note that this may not correspond to your pedals input.
  12. Throttle indicator. This indicator bar shows how much throttle input the game is getting. Note that this may not correspond to your pedals input.
  13. Gear indicator. This shows the current gear (if enabled, the internal app state shows above). Tapping this resets the "lift and coast" and "braking on throttle" meters.
  14. Braking on throttle.* This small indicator increases/decreases depending on how much you brake while simultaneously being on throttle.
  15. Lift and coast.* This small indicator increases/decreases depending on how much time you spend off both throttle and brake.
  16. RPM. This indicates the current RPM of the engine.
  17. Tyre temperatures; front left, front right, rear left and rear right. These 4 indicators shows the tyre temperatures. The top temperature digits shows the average temperature* for that tyre over the past 30 seconds or so. The bottom temperature digits show the current, actual temperature as reported by the game. The background of the tyre is filled with a gradient ranging from blue (cold) to green (working temp) to red (overheating). The color at the top of the tyre follows the average tyre temperature, and the bottom color follows the current tyre temperature.
  18. Current lap. This indicates the current lap as reported by the game.
  19. Last lap time. This indicates your last lap time as reported by the game.
  20. Best lap time. This indicates your best lap time as reported by the game.
  21. Average/Median lap time.* This indicates your average (or median, if you enabled that in the settings) lap time. This is based only on your flying laps. Can be reset by tapping the digits. Note: If you have enabled a cutoff lap time in the settings, it will be shown below this readout, and any laps exceeding that time will not be counted towards the average/median lap time.

* denotes a readout that is NOT straight from the game telemetry, also meaning that it may not be 100% accurate at all times. Some data is based on qualified guesswork, but should be usable and "good enough" in most cases.

There is also a toggle in the settings to display the app's internal state tracking, which when enabled shows as a text above the gear indicator. It has the following possible states; MENUS, ENTERED, PITENTRY, PITLANE, PITSTOP, OUTLAP and FLYING.

The dashboard screen is the main screen of EzioDash:

Please note: screens may differ slightly from the current version.

Why are some readouts zero or empty?

For obvious reasons some readouts shows zero or no information when starting (or after a reset), but there are a few readouts that have special conditions.

Beneath the fuel bar, there are three readouts. The first readout shows percentage of fuel per lap, and shows only if fuel consumption is active and only after the first lap has completed. The second readout shows laps remaining, and uses the same conditions as fuel per lap. The last readout is time left for the remaining fuel. This third readout only shows if/when you have an average lap time value.

The average lap time is only available when the app can determine that you've completed a flying lap. For this reason, if you go into the pits after an outlap or the first flying lap, you will not get an average lap time.

Lift and coast

The app keeps track of how much lifting and coasting you do. This basically means how much you let the car just "roll" through corners and such. For this, the app counts how many packets pass by where you are off both throttle and brake. Of course, this would give a false picture if those were the only conditions; this is only measured when the game is not paused, the car is on track (outlap or flying lap) and in gear. Also, the speed must exceed 20 kph (about 12-13 mph) and it stops counting after 3 seconds of continued lack of throttle and brake input.

This meter can be reset by tapping the gear indicator (also resets "braking on throttle").

Braking on throttle

EzioDash also keeps track of how much of the time you apply brake at the same time as you are on throttle. For some cars and driving styles, this is a common practice, but if you know that you are touching the brake pedal while you shouldn't, this is a good indicator to see how much of this you are actually doing. Knowing enables you to try to change a potentially bad habit. As with the lift and coast, this is only measured under certain conditions; not paused, on track (outlap or flying) and above 20 kph.

This meter can be reset by tapping the gear indicator (also resets "lift and coast").

The simplified dashboard readouts

This section describes the various parts of the simplified dashboard

The simplified dashboard consists of a select number elements:

  1. Tyre temperatures; front left, front right, rear left and rear right. These 4 indicators shows the tyre temperatures. The top temperature digits shows the average temperature* for that tyre over the past 30 seconds or so. The bottom temperature digits show the current, actual temperature as reported by the game. The background of the tyre is filled with a gradient ranging from blue (cold) to green (working temp) to red (overheating). The color at the top of the tyre follows the average tyre temperature, and the bottom color follows the current tyre temperature.
  2. Fuel indicator. A simple bar and percentage of fuel left. Note: In races without fuel consumption, this will remain at 100%.
  3. Fuel used per lap.* This shows the percentage of fuel used per lap (only when you've passed the starting line) if fuel consumption is enabled.
  4. Laps remaining.* This shows an estimate of how many laps you can finish based on your past consumption and fuel remaining.
  5. Time remaining.* This shows an estimate of how many minutes and seconds you have left, based on an average lap time (which can be reset).
  6. Connection quality indicator. This bar goes from red to orange to yellow to green to indicate the quality of the connection. Normally this should be a full green bar if you have a good local network environment.
  7. Top speed.* This is the top recorded speed (in kph or mph). Can be reset by tapping the digits.
  8. Average/Median lap time.* This indicates your average (or median, if you enabled that in the settings) lap time. This is based only on your flying laps. Can be reset by tapping the digits. Note: If you have enabled a cutoff lap time in the settings, it will be shown below this readout, and any laps exceeding that time will not be counted towards the average/median lap time.
  9. In-game time of day. This is a 24h clock corresponding to the time of day on the current track. If the game has time progression enabled, this will show the correct on-track time. Note: For tracks that don't have a full 24 hour cycle, this time of day may seem to be stuck, until it switches over to the first morning time of day. This is only applicable in races where the time progression is either high enough to cause a full day cycle to pass, or is long enough to pass from one day to another.

* denotes a readout that is NOT straight from the game telemetry, also meaning that it may not be 100% accurate at all times. Some data is based on qualified guesswork, but should be usable and "good enough" in most cases.

The simple dashboard screen is one of the dashboards in EzioDash:

Please note: screens may differ slightly from the current version.

Not shown: Current version also displays the current lap, between the top speed and average/median lap time.

Giving you some options

This section describes the various settings available in EzioDash

The options are as follows:

  1. Toggle metric units (speed/distance): (defaults to on) This toggle lets you toggle between metric units (kilometers per hour, kph) and imperial units (miles per hour, mph).
  2. Toggle metric units (temperatures): (defaults to on) This toggle lets you toggle between metric units (degrees Celsisu, °C) and imperial units (degrees Fahrenheit, °F).
  3. Toggle between average and median lap time: (defaults to off) This toggle allows you to switch between an averaged lap time (based on flying laps) or a median lap time. I will not go into the difference in depth, you can read more about the difference on Wikipedia.
  4. Set cutoff for flying laps: (defaults to None) This slider lets you choose if you want slow laps (up to 110% of your fastest lap) to be disregarded for the display of average/median lap time.
  5. Toggle keep app awake: (defaults to off) This toggle lets you tell the app to always stay on, keeping the screen from dimming and the iOS device from sleeping. Please note that this app may draw quite a lot of power, and will drain your battery with a pretty rapid pace. Consider keeping the iOS device on wired power (or equivalent) to prevent excessively rapid discharge and heat.
  6. Toggle display internal app state: (defaults to off) This toggle lets you display the app's internal state tracking, which shows what the app thinks is going on in-game. This displays as a text above the gear indicator.
  7. Toggle support for replay mode: (defaults to off) This toggle lets you enable the experimental feature that allows EzioDash to display telemetry during replays. Please note that the replay telemetry differs from live telemetry (this is in-game), so there will be differences or odd behavior at times.
  8. Toggle enable demo mode: (defaults to off) This toggle lets you activate a demo mode from the connection screen. The demo mode is simply a pre-recorded session that is replayed in the dashboard screen.

And below the toggles is a simple link to this page. Please note that the app goes into disconnected mode when clicking any link in the app, due to the app going into the background.

The settings screen allow some creature comforts:

Please note: screens may differ slightly from the current version.

Not shown: Current version also has an option to have the RPM bar flash when it reaches the warning threshold.

Demo mode

The app has a demo mode that simply replays a recorded session. To enable the demo mode you need to go into the settings screen to enable the option “Display demo mode”. Then from the connection screen you must disconnect (if connected) before you can tap the “START DEMO” text. To view the demo, proceed to the dashboard screen by swiping or tapping the large circled right arrow. You can also go back to the connection screen and tap "STOP DEMO" at any time.

Known bugs and quirks

Here is a list of known bugs:

  • In my experience, the app will in some cases "lag behind", up to several seconds or even more in extreme cases. I have yet to discover WHY this happens (it's not related to connection quality), I have personally seen this only on my old iPad Air (2nd gen) and iPhone 6S. This does not seem to happen on my old iPhone 8 (all running iOS 15.7). If anyone knows, drop me a line, please.
  • The app may sometimes lose connection or freeze for a short time. This is likely due to bad connection quality, or an interruption on the network. This may cause the ports used for the telemetry to block for a time (which is an operating system issue, more or less). EzioDash will keep trying to reconnect, but you may have to force quit the app and wait a few minutes before it will reconnect.
  • It is possible that the app fails to detect pit stops. There is no built-in data about this in the telemetry, so the app uses homegrown logic to determine if/when a car enters the pit. If this fails, it mostly affects the calculation of the average lap time, and in extension the time remaining for the fuel. There are two ways for the app to detect a pit entry; either by careful examination of the telemetry data, or “brute-force” looking at the pit lane entry coordinates. Both of these approaches CAN fail, especially for new tracks. So if you encounter a track where the app fails to detect a pit stop (and you can reproduce it reliably), or get stuck in either of PITENTRY, PITLANE or PITSTOP states, feel free to notify me about it.
  • There is a small chance that the app may crash when quitting the game while the app is still running.
  • Dirt tracks doesn't seem to have neither fuel consumption nor tyre wear, and going into the pit lane just sees the car trundle through. This means that there is no way to detect if/when a car enters the pit lane on dirt tracks.
  • Some cars in the game exhibit strange behavior (telemetry-wise) which will prevent the app from working properly, either in some isolated aspect or completely. One example is the Chaparral VGT car, which always have the clutch engaged. I may look into this in the future, and since the actual car id is included in the telemetry, it may be possible to somehow get around this.

Bug reports

You are very welcome to contact me if you find anything that isn’t working as intended. I do however request that you try to recreate the problem before you contact me. A bug that can be reproduced is a lot easier to find. Also, please include the build version of the app (top right on the about screen), where in the game you were (lobby, arcade, time trial), what car you were driving, and on what track. The more information you can provide, the easier it will be to find and hopefully fix.

If you can include a replay or video of when and/or how the bug occurred, it can be very helpful.

There is a changelog available for the app here.

You will find contact info on the bottom of this page.

Donations

Due to the reason mentioned in the disclaimer, I have decided to release this app for free. Since it relies on the goodwill of a third party (i.e Gran Turismo 7), I feel it would be unreasonable to charge even a small sum for the app. But, if you feel that this app is something you appreciate and would like to support the development, I do have a Ko-fi page here: https://ko-fi.com/bornhall

You can donate a small sum to keep the coffee flowing, or to buy a bone for Ezio. You can even donate monthly if you so wish. If you have contributed to the development I would like to take the opportunity to thank you, so – THANK YOU!

Of course, if there is substantial support for the app, there may be versions for iPad and additional features in the future. So, support it if you like and use it!

Credits

This app would not have been possible without the work of Nenkai and the combined efforts of people on GTPlanet like poumpoum, tarnheld, Stoobert, gu64, MGR, Hyurt, snimat, ddm, vthinsel, Lukejuryous, DJShadesUK, Evis and anyone else I might have forgotten. Also a big thanks to my beta testers.

You can find more information about how this all came to be here:
https://www.gtplanet.net/forum/threads/gt7-is-compatible-with-motion-rig.410728

This is in parts based on information gathered by Nenkai (and others). Learn more from his Github:
https://github.com/Nenkai/PDTools

Contact

If you have any questions about EzioDash, you can contact me by e-mail: bornhall@gmail.com

You will also find me on the forums on GTPlanet with the nickname "Bornhall".

Note: I can’t possibly answer all e-mails or messages, but I will read them. Please include “EzioDash” somewhere in the subject line for better visibility though.

Privacy policy

You can read the privacy policy here. However, the app does not collect any personal data at all (apart from the telemetry), so it's basically a formality.