Jump to content

OpenCockpits cards


Cezar11

Recommended Posts

Has anyone gotten the list of devices and clickabledata together yet for A-10?

 

I'm looking to build an OC card input device ( not really concerned about output yet.. but want to futureproof myself ).

 

I noticed that my devices.lua is basically empty ( i'm sure this is WIP ) but wondered if there was a good list of input coords for A-10 yet.

Home built i5 quadcore. dual ATI 4850 in xfire mode. 16GB ram Warthog HOTAS, Thrustmaster Rudder, TrackIR 5, TM MFD's, windows 7 64 ultimate.. 40" primary screen, 19" secondary

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Has anyone gotten the list of devices and clickabledata together yet for A-10?

 

I'm looking to build an OC card input device ( not really concerned about output yet.. but want to futureproof myself ).

 

I noticed that my devices.lua is basically empty ( i'm sure this is WIP ) but wondered if there was a good list of input coords for A-10 yet.

 

Yes look at this post for devices

 

Also a lot of the functionality for getting and setting variables is grouped under the main panel, device 0, even though they don't belong there.

Link to comment
Share on other sites

not sure I understand what this is.... in the listing there's this..

 

devices.UFC = {

__index = {

performClickableAction = function: 357CA260

SetCommand = function: 357CA218

 

the UFC is more than a single button... so where's the breakout for each button function?

Home built i5 quadcore. dual ATI 4850 in xfire mode. 16GB ram Warthog HOTAS, Thrustmaster Rudder, TrackIR 5, TM MFD's, windows 7 64 ultimate.. 40" primary screen, 19" secondary

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

so.. gonna leave a brother confused on this ?

Home built i5 quadcore. dual ATI 4850 in xfire mode. 16GB ram Warthog HOTAS, Thrustmaster Rudder, TrackIR 5, TM MFD's, windows 7 64 ultimate.. 40" primary screen, 19" secondary

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Cezar,

 

There are several threads on the forum here that explain how to interface OC cards, even source code for direct SIOC to lua integration. I suggest you start with reading Oakes threads (BlackShark and A-10C are 99% identical in reading the clickabledata.lua). The devices.lua file is not empty on a DCS A-10C installation it just uses a counter to increment the value. Start with one on the first line that says = counter() and add one for each call to it (hint for Beta4 just subtrace 7 from the line number).

Link to comment
Share on other sites

not sure I understand what this is.... in the listing there's this..

 

devices.UFC = {

__index = {

performClickableAction = function: 357CA260

SetCommand = function: 357CA218

 

the UFC is more than a single button... so where's the breakout for each button function?

 

To press the UFC buttons would be

GetDevice(devices.UFC):performClickableAction(3000+b,1)

where b is 1 to 35

 

To get the devices table (for devices.UFC to work) you need to

dofile("./Scripts/Aircrafts/A-10C/Cockpit/devices.lua")

at the top of your export.lua otherwise you need to use the device number

 

Why 3000+b? the answer is in command_defs.lua

 

If you do your research on the forums, and start opening up lua files and poking around in them, your confusion will slowly be replaced by knowledge

Link to comment
Share on other sites

I kinda resent the assumption that I didn't do any research. I hate asking these kinds of questions on the forums, for the exact reasoning displayed in your post, i'm not trying to be a dink here, but why would I make the magic leap that a-10 uses an incremental counter, when BS was very plain in its device numbering system? Furthermore, why would I make the assumption that I need the dofile statement?

 

I get the clickable data file and all I was missing was the device number. I've searched for the last 2 weeks everyday for hours on this matter before I've asked. All I've been finding is the BS stuff.. which is obviously a little less than 99% similar to a-10 in its availability in the files.

 

I appreciate the help, and I do take a great satisfaction in finding out how to do things myself, I just obviously don't have the time nor the aptitude for reverse engineering these files, however, I don't think that should stop those of us that don't from enjoying the extended functionality that this has to offer...

Home built i5 quadcore. dual ATI 4850 in xfire mode. 16GB ram Warthog HOTAS, Thrustmaster Rudder, TrackIR 5, TM MFD's, windows 7 64 ultimate.. 40" primary screen, 19" secondary

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

We're cool.... I do put a little too much emotion into emails and such... breaking rule no. 1 LOL :)

 

It's just frustrating when you do exhaust what you think are the only avenues of information and still can't put it all together in your head..

 

I zipped up the entire scripts folder and subfolders and going to take them to work tomorrow... see if I can't put something together.

 

I probably just need to order the cards and start building.

 

thanks for your help again.. :)

Home built i5 quadcore. dual ATI 4850 in xfire mode. 16GB ram Warthog HOTAS, Thrustmaster Rudder, TrackIR 5, TM MFD's, windows 7 64 ultimate.. 40" primary screen, 19" secondary

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

That's the route I went, Cezar ... the most I've done is connecting a couple switches and rotaries to see what happened in the SIOC data. Whenever I actually start getting things put together for good, then I'll be laboring over Oakes's and Y2kiah's threads like a madman again, I'm sure.

Link to comment
Share on other sites

I ordered the cards today... ( man.. $160 for a master and usb card + shipping ) but we'll see what's going on here :)

the nice thing about the OC cards is you don't have to run them on the A-10 pc, so I can use a less than capable pc for that.. ( from what I've seen, the whole LUA thing can be run over the LAN.. please yell if i'm mistaken..)

 

Feed, maybe you and I can support each other in this world, sharing little bits of info we find out from the forums... it's nice not to feel so all alone out here! :)

Home built i5 quadcore. dual ATI 4850 in xfire mode. 16GB ram Warthog HOTAS, Thrustmaster Rudder, TrackIR 5, TM MFD's, windows 7 64 ultimate.. 40" primary screen, 19" secondary

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • 5 weeks later...

Hi Cezar11, it's been a month since you ordered from OC. Have you figured out export.lua yet?

 

I'm at the point where I have installed, powered up and tested my Master Card's inputs and outputs (using these instructions) and I'm going to wire some switches and landing gear & T/O trim leds today.

 

I think I can make the Sioc part work (toggle switches, buttons and leds are all I need) but I'm at lost with all the lua stuff myself. I have found Oakes's siocConfic.lua file and his export.lua for Black Shark and I'm trying to figure out what to do with them in DCS A-10C. If there is a simple export.lua file with one toggle switch and one led I'd be glad if someone pointed me to the right direction...:helpsmilie:

1002770406_sioc012.JPG.4dd0b415badaf89e38f2a240cb85c4ee.JPG

Link to comment
Share on other sites

I'm still in the "build it physically" stage here, but have the cards and have fiddled around in SIOC just a little bit. No interfacing with DCS yet, but if you're looking at Oakes's and y2kiah's threads, I'd say you're in the right spot. Another thread with good info is Jocman's pit build - he seems to be working on the wiring and code piece, first.

 

I wish I could be more help right up front, but I'll be poking through those threads myself once I get some switches wired up. :)

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...