can i use a 2e small monitor to display a few gauges ?

[Artist]

Afaik the issue with IL-2 was that, yes you could get all necessary info for the gauges with DeviceLink via udp/network - but (officially) only in offline mode (there is or was mod to bypass that limitation).

In CoD you can get at the info from within mission script, FearlessFrog demonstrated it here with Heading, Altitude, and Speed. Problem is, that it has to be part of the mission script, which means that you've to copy it (with FMB) into all missions you want to use it in. And if you're flying online it has to be part of the mission script on the the server...

Artist

[jimbop]

Is this thread relevant? I don't have know anything about it, just remembered the thread: http://forum.1cpublishing.eu/showthread.php?t=24856

[Skoshi Tiger]

Originally Posted by jimbop

Is this thread relevant? I don't have know anything about it, just remembered the thread: http://forum.1cpublishing.eu/showthread.php?t=24856

Thanks for the link, but the app on that page is for the original IL2 series that uses device link. It's relatively easy to set up a client program to poll device link using the UDP protocol and retrieve the information.

COD is a different kettle of fish.

As stated beore I tried to use a C# script to set up a UDP server wfrom within COD but due to my limited C# scripting skills failed.

Anyone else had any luck?

Could be that there is another way to get the info out of cod. I guess we need scripting documentation for COD.

Cheers

[hugso]

It really is a shame - there is all that information in getParameters and yet there is no official info on how to utilize it. I am busting to get my motion platform cockpit working with CoD. It works great with IL-2 and Devicelink, but why does getParameters have to be so complicated with no clues about how to use it?

[zapatista]

gentlemen, now we are getting somewhere

artist,
thanks for the link, being able to already access some of the flight data sounds like a major step in the right direction

bolox,
thanks for the summary, i remember your nick from the old ubi forum discussing that feature at length. have you had a look at the link that artist posted and is that type of flight data access possible for some of the cockpit gauges ?

i have no programing or coding experience so am out of my depth on the practical side

if this currently would only work offline, thats a major step in the right direction, and it might be possible for some of the main online servers to implement it to in their setup later (untill luthier incorporates it as a feature). setups like this with separate display for cockpit gauges is possible in several of the major modern flightsims (DCS series, xplane etc), would be great if we can get it working for SoW

[bolox]

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

[zapatista]

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

[bolox]

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 ?

The easiest way would be for CoD to output 'old style devicelink' outputs.

This would entail the CoD script doing:
1) reading the request packet sent from udpspeed,
This bit would probably need to read from an ini file to set up the IP address and port
2)ordering the data from this packet into an array or similar.
This could be simplified/eliminated IF the contents of the packet is a fixed, known set say for a BFP gauge set using~ 10 parameters.
A more universal system would be better tho.
3)Then each parameter must be associated with the relevant CoD parameter and read this data, There is a problem in converting units as IAS is given in km/h in Luft AC and mp/h in British AC. Doable in code but another complication Indicated ASI is also possibly nit accurate
4)write this converted data into the reply packet
5)send it

that's my take on what needs to be coded- actually doing it is beyond my talents

this is the nearest example of something similar i've found
http://msdn.microsoft.com/en-us/library/tst0kwb1.aspx

http://tools.ietf.org/html/rfc768
shows udp protocol

devicelink doesn't use checksums

btw, isnt it 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

anything is possible An MG produced program that displayed the 'wondewoman' gauges- (editable, reposition/sizing ability, saveable profiles,...) would be nice as a free bonus in the sequel
As to wether modern cards won't affect fps i couldn't say for sure (4 yrs ago with IL2 it was definately a problem)
http://forums.ubi.com/showthread.php...-thread/page30

[Skiiwa]

I for one, Support this Thread!

[Friendly_flyer]

I hope the devs gives this a mind. With the complexity of the engine, this would likely help reach another niche of the market too.

Please, do go on, Gents!