I read random past friday upates since late 2009 and at some point they talked about it. The plan was to keep it, but expand upon an ddevelop it more. And to remove the restrictions for it in multiplayer. I am sure that it will technically work the same way. Just different framework version.
What is not yet known is how much of our features existing or desired for, will be satisfied by Call of Dornier. Then one will know where it all stands. And can figure out where to go from there.Wrestling the reversal bug bullshit seems to be a required past time for the upcoming year yet. This also adds ability for hooking up all kinds of strange game controllers (any, really, including a G25 force feedback steering wheel, to be used as elevator trim when mounted low left in the simpit. I did that ot rocked.
Setting things up to facilitate communication between the main app, the network relay tool, and binding the sockets to these different ips and ports. That was so ghetto. Using '¨stdout' from my AHK program piped to the stdin of the G940 led reading applet. Through UDP networking.
If devicelink is open and welcoming with several different connections at the same time, maybe the development should be best spent on specializing a focus for each of our two program efforts. That can be used together for those who ish to use the best features from both. Mostly axis solutions (with anti-bugged to hell controller illnesses as per the G940) for YaDeLi seems to be where it excels. AutoHotKey is the bomb for button and even sound effects easily added, and can be used to control the LEDs in the G940.
|