Been a long time proponent of this sort of thing, and in these days of 'shiny' tablets etc it is unusual not to have some sort of official output protocol in a flight sim
Yes the data Artist points to is what is needed- infact CoD has many more types of data that is readable than old IL2 devicelink.
I've messed about with coding based on that to do 'speedbar' type readings of various parameters but that's about my limit of coding- hacking other peoples work
One of the 'tricky bits' of coding required is to 'translate' the request packet from say udpseed into an answer packet from CoD
Not only are there instrument reading parameters available but also many other useful ones- for a full list see zip in 1st post
http://forum.1cpublishing.eu/showthr...338#post342338
Apart from deciding which CoD parameter is most relevant as an output (gauge users will want instrument readings whereas performance chart makers will want 'absolute' values) some values might need converting to the relevant units
The more I look at what is involved coding wise to export this data via udp, the more I realize that it's beyond me
If anyone gets to do this a more MKI version of this would probably be my first project
