Quote:
Originally Posted by bolox
a little bump for this
would really like some form of official statement as i'm sure i'm not the only one thinking of a pit build for CLoD and some idea of what (and how) we will be able to input/output data would enable us to get an idea of which route(s) to choose
|
+1
I read some info related to classes for scripting published by some users but I do not see clear the way to use them in order to run a "Client-side" script that would be able to manage an external gauge developed software, all I've seen are "server-side" scripts which have no use for this purpose.
I know how to develop in .NET, but I didn't have enough time to go through this yet anyway. I do plan to develop something in order to make the gauges work on a secondary screen or something like that so I can use them on my homemade cockpit.
Anyway, I think this should be done either using client-side script to create some kind of interface with a .NET app or adding some kind of output to a file from the game by the dev team so we can read that file and use it the same way.
I and I bet a lot of people would love dev team to make an official statement regarding this, or release some kind of information related to this subject so the community can move on.
__________________
Former member of:
StG111 2003-2005 | SG1 2006-2009 | 15.Span 2010-2011
CPU Intel i7 920 @ 2.67 -> OC 4 Ghz
MB ASUS P6T
Cooler Noctua NH-D14
Memory 12GB
GPU 2x nVidia 285 GTX 1GB SLI
HD 2x SATAII WD VelociRaptor 150GB RAID 0
SB ASUS Xonar DS/DT 7.1
PSU Tagan 1100W
OS W7 Ult.64
LCD LG W2284F-PF
TrackIR 3 Pro +
Saitek X-52 +
Saitek Pro Rudders Pedals +
Pro Flight Throttle Quadrant +
Saitek PcDash 2