You ask about things I was sure of and could provide links to before 2007. I have seen no major changes since then.
IIRC there were online cheats where data from players planes were being read at the host server and used but that may have been speculation including the part where one team got caught.
http://forum.1cpublishing.eu/showthread.php?t=29404
Quote:
Don't output "true" values, only instrument readouts. This makes sure that DeviceLink instruments can't move faster than those displayed in the sim. Currently the variometer(and other gauges) output changes in value faster than the virtual gauge.
Another benefit of this is authentic needle movement for anything using Devicelink.
|
There is no devicelink TAS or position outputs. They were asked for and turned down. What the above refers to is on-screen instrument updates which I can't say how often the game updates the gauges but if devicelink is getting queried 1000+ times a second then check FPS to see about the load that action puts on the game!
Get yourself a copy of UDPSpeed or UDPGraph and see what you get. I was only able to get instrument readings. Perhaps Pfeil knows something extra or just how often IL2 updates gauges or didn't take into account the load he placed on the game.
Note all the gauges and actions he says are not supported.
You also have a file named devicelink.txt in your game folder. It names all the commands.
This is something that perhaps DT has an expert on. Otherwise you're welcome to read many pages of threads trying to separate signal from noise and hope you interpret loose words to hard reality. You'd do better running UDPSpeed gauges and looking for real differences while remembering that yes you can affect the game through overload. One gauge, 10x a second should be enough to see if the on-screen gauge is only updated at more than 1 second intervals. You can't see 100th of a second so don't bother 1000x per.