Quote:
Originally Posted by bolox
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 |
so what exactly do you need to be able to use the data accessed by the simhq guy, to be able to use it for your gauges ? if some limited form of data is already accessed for them to create the displayed data for heading and altitude, shouldn't it then be possible to translate that to a format that some of the gauges can use ?
btw, isnt it also possible to have some very limited 3D version of the gauges so it avoids the 3D/2D problem you mentioned before ? with most gfx cards having multiple connectors these days and the minimal GPU resources needed to display a 2 color static image i would have hoped we dont need to run a 2e pc to just display the 2e screen with the UDP method. err, please be aware i know nothing of programing, so i am probably overlooking some obvious reasons why some of this is an issue 
__________________
President Dwight D. Eisenhower 1953: Every gun that is made, every warship launched, every rocket fired signifies, in the final sense, a theft from those who hunger and are not fed, those who are cold and are not clothed. This world in arms is not spending money alone, it is spending the sweat of its laborers, the genius of its scientists, the hopes of its children
Last edited by zapatista; 09-19-2012 at 09:41 AM.
|
09-19-2012, 09:28 AM
Threaded Mode