LeLv30_Superbus

Upgraded to Titan from HD 6970 and the change was noticable but not dramatic. Most of all I'm happy I can now use HDR for the first time without bright white flashing squares in the picture. An AMD driver issue which was never fixed.

I have my BK2 Gamer plugged to the usual left-right speaker output with the splitter cable. It works great that way. No need to use a subwoofer output. Buttkicker has been the easiest peripherial device to install, ever.

Yes I created a Config\Export\SIOCconfig and copied exportsupport.lua there if that's what you mean, but thanks anyway. I don't use Helios and neither does Duckling I'm afraid. It doesn't do SIOC (Opencockpits) afaik.

Clueless I'm sorry to report I have made little or no progress. I copied the old export.lua to the new directory C:\...\DCS World\Config\Export and examined what changes there were in the example file and implemented them. DCS connects to SIOC server when I start the sim, but it doesn't seem to send or receive anything. DCS freezes completely after drawing the first frame. I'm afraid I'm not smart enough to crack this one. It has to be something really stupid and simple, though, because I can't think of any reason they would have changed anything fundamental now. There was no need. :helpsmilie:

Duckling, I just switched to DCS World and my cockpit (running SIOC) stopped working, indicator lamps and switches alike. You might want to wait until I figure out what changes are needed. I expect them to be very small.

tonym, .rar is a compressed archive, like .zip. Install WinRAR, for example, and uncompress. The .miz is inside. While I'm at it, this is a great mission, thank you very much!. I've flown it three times now. My only problem has been getting access to the DCS command console, I can't find its key assignment in Options -> Controls...

Strix, how was your framerate affected by this change?

It's worth noticing that the brochure talks abput FSUIPC support, though. That means it works with MS Flight Simulator. FSUIPC does not work with DCS.

Just to give people more ideas, hopefully, here is my solution too. Thanks to the supporting steel plates Buttkicker shakes the stick quite a bit, not just the chair. It's perfect for me. I will install a seat arming switch, a warning light and an EJECT switch later.

One more thing I noticed: I had to reverse the "=0:" and "=1:" in ExportSupport, please see comments: lSIOC_SendString = lSIOC_SendString..lSIOC_Var.."=1:" -- In my cockpit "1" turns the led OFF - go figure! else lSIOC_SendString = lSIOC_SendString..lSIOC_Var.."=0:" -- In my cockpit "0" turns the led ON These would be on lines 38 and 40 in your ExportSupport.lua.

I started to read through your files again and I think line 134 in your Export.lua is wrong. You never send your warningIndicators, you are only sending some (I'm guessing) variometer data: lSIOC_SendString = lSIOC_SendString..Variometer(gVariometerSIOCParam)Try this instead: lSIOC_SendString = lSIOC_SendString..ProcessIndicators(gIndicatorTables)This would all be in line with the the fact that your switches work but your indicators do not. Indicators are updated after each frame, switches are updated before the simulation frame. This line is only executed after a frame. I found out that the line I told you about earlier (gIndicatorTables = etc.) is duplicated in your siocConfig, so moving it is not necessary. It's redundant and can be removed altogether from Export.lua, as long as you keep it in siocConfig. Sorry, I don't remember which one was "0_93_beta" but I'm afraid none of them work with any version of DCS A-10C without modifications, because they are for Black Shark. The way DCS A-10C handles input and output has changed at least once too, so not all Lua code for A-10 out there works any more with the current version.

Try moving this line: gIndicatorTables = {warningIndicators} --added 2012-01-14 after this this one: dofile ("./Config/Export/SIOCConfig/siocConfig.lua") "warningIndicators" table is defined in siocConfig. Therefore I think the table is empty when the first line of code is executed. That would explain why your switches do work but your indicators don't. I hope this was helpful. I struggled 6 months with the code part only, before my A-10C cockpit started working, because the information is spread like precisious breadcrumbs all over various posts over a long period of time. (And I still can't get 3 position switches to work correctly...) strike last sentence - I solved the problem!

I compared your lines to my own and I noticed two little differences on every line: Your: Var 0111 name WR_GCAS, Link IOCARD_OUT, Output 24 // WRNG_GCAS Mine: Var 111, name NSAFE_LDGEAR, Link IOCARD_OUT, Output 11 A leading zero (note there isn't one in your siocconfig.lua - nor mine) and a missing comma, that is. Please note that I don't really know whether or not these things matter, though. I hope this was helpful.

I've got a with just one switch like that connected to BU0836 and it works well as long as long as you set the correct state before starting the sim.

VAC Friendly is exactly what I was looking for too, thank you! I noticed there is a lot of file copying required, however. If possible, please consider making your mod JSGME -compatible in the next release. All you need to do is include the correct directory structure so your mod's users do not have to care about where to put each file.

I saw it after I posted. Some bleeding there, but I'm glad to hear you fixed it already. One thing that caught my eye, however, was that in the picture the letter "L-"'s weren't illuminated very well in some of the second column indicators. That's what it looks like to me, anyway. Same thing with some of the "R-"'s in the third column. Double leds would probably help there, or mounting the single led a little deeper, or using a led with a wider beam. What do you think?

$175 is fine for me. Just drop me a pm when you are planning to make another one. The 1-hole version is probably just as good if you mount the led deep enough. I'd like to see a picture with the lights on first, though. The led will probably have to be brighter if it's further back from the face plate. It all depends on how wide the beam of light from the led is. This just crossed my mind: what about light bleeding to neighbouring indicators through the baseplate or diffuser plate? Is that going to be a problem?

Ah I see. You can run two leds just as easily as one. At least that's what I did. Leds require very little current so the Phidgets card shouldn't have any trouble with two. Just connect them in series and calculate the correct forward resistor. I used R = 1 ohm for two TLG 114A leds. Most leds like a current of 20 mA. That gives Vf = 2.5 volts for the leds which is good for TLG 114A (rated 2.1 - 2.8 volts Vf). 12 ohms would give Vf = 2.4V, for example. +5V ----U----U-----R---- -5V U = led R = 1 ohm resistor Led calculator: http://led.linear1.org/led.wiz Unfortunately Helios does not support OC cards. :(

Looks very nice indeed I'm interested in buying one of these too for $US 140 + shipping, as soon as you make another one. Please pm me. I was wondering if two 5 mm leds side by side would give a better result than just one? Have you tried what the panel looks like when lit up? I made 3 landing gear and one take-off trim light last weekend using two leds and a semi-transparent piece of plastic to scatter the light and they look ok to me. I'm in no hurry, though. I've got the Opencockpits master card and I still have to figure out how to make DCS speak to it. (Any help would be appreciated, byt he way. I've got Oakes' interface code for Black Shark but just replacing the SIOC parameters with mine doesn't seem to be enough with A-10C.)

Something else in the picture caught my eye. Look at the gun trigger. Then look at your HOTAS Warthog from the same angle.

This just caught my eye: In order to stop builders from wasting time: If you mean "it is easy to rotate the plate by +/-90 degrees" - it is not. If you connect the screw holes, you get a rectangle which is not a square. In other words... + b + a + b + ...a does not equal b, unfortunately. I hope this was at least of some use to someone. My apologies if I misunderstood you, Gadroc.

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:

Nice! Wow. How are your new pedals?

FWIW, I bought an IOcard LCD board from OC but I haven't got a display for it yet. I've been looking for one that'd look like the real thing, with green dots and all, to no avail (so far). I haven't even powered my master card yet, so I have a long way to go. I decided to use my PC's power supply, so I won't run out of current.