Thirdup

I wasn't entirely thrilled with the look of the little paper labels for the LEDs. I called the local Office Depot and they can print a transparency for 75 cents. Now just to fill in the templet with what I want.

Well, I owe you a beer. I'm not sure which actually was causing the issue, but installing the 1.01 patch did the trick (it over-wrote my modified export.lua file which might have been the culprit).....I then used Morg's "example_export.lua" (sans "example_"). In any event, at least my throttle is all lit up like Christmas now. *which of course means that I'll now have to figure it all out and see what i can break next. Thanks ddahlstrom and thanks Morg!

Hmmm, you know....I have a seperate text editor but I may have actually edited the lua's with notepad (actually, the only edit I think I initally made was to the config....so that might explain alot if the first thing I did horked things). Not sure on the BS version (off-the-shelf install). I was unaware of a patch, but I'll check that first thing.

Still can't clear that last hurdle...... I confirmed that exporting was set to "true" in the config.lua. I'm working off a fresh BS install, so I used the included example_export.lua (removed the "example_" of course) G940leds.exe launches and detects the G940 (it turns off all LEDs) Udp_sender.exe is communicating and I can send color changes manually. Game launch and flight still are not producing anything on the LEDs. G940leds.exe is displaying the "hello" message (so it appears that the app is at least getting to the coroutine). No errors in "errors.log" relating to this set of lua's (although I can produce one if try and I now know where they would be). I've attempted to run both included coroutines with the same results. I also tested/changed the "hello" message text to reflect which coroutine was running, and I can confirm that the export.lua edits are calling the assigned coroutine in the G940leds.lua. I suck at this stuff, but I'm not giving up hope just yet.

Rgr that. Thanks again!

So it doesn't matter which profile I have loaded into the G940 via the Logitech software? For some reason I've got it in my head that I should have my button profile set up in the same fashion as the LED program uses (ie: button1 is autopilot on/off, button2 is toggle gear, etc)..

Thanks, will go back thru it all when I get home tonight.

Greetings. I've had my G940 for several weeks now. I even followed this thread before the purchase (seems there's not much out there taking advantage of the G940 LEDs). After pondering Morg's code and trying to get my head around it, I decided the next logical step would be purchasing DCS:BS (loving it, btw). I'm no programmer but I can usually edit a config file or two without screwing things up. I've got Morg's program running. All the files are in place as per the instructions. The communications part appears to be working (I can update the LEDs with udp_sender.exe). Nothing seems to happen when the application calls up the example functions (I've tried switching between the g940leds_AutopilotTargetingMode and g940leds_example). My (dumb) question is: do I need to configure the controller in the Logitech software (ie: change the default DCS:BS load) so that it somehow reflects what these example functions are doing (ie: button#3 should be gear, etc)? I just have a feeling that the LEDs are not working because I'm missing a step somewhere. It took me a few hours to realize that the udp_sender.exe would only work if main application was already running. I'm at further disadvantage because I'm not even remotely familiar with the sim yet. Any tips appreciated.