Djuuu

Erf, Sorry ! I would have been very surprised if my version for worked with DCS, with literally zero test :P Anyway, thanks for your feedback. I can try and see if there are obvious errors if you provide me the following log files : [DCS folder]/temp/Error.log [DCS folder]/temp/G940leds.log But again, I can't promise anything, since I don't have DCS. (and I am not planning to get it for the moment)

For those flying on Lock On FC 2, I have redesigned all the LUA part to set up a profile more easily : It is a Modman package : you should install it with Modman (packed with version 7.3, I don't know if there are backward compatibility issues) I have implemented the main statuses you might want to see on the buttons : engines, flaps, gear, radar, autopilot, modes, etc. To assign status function to buttons, edit : /Config/Export/G940leds/LO-FC2/profile.lua You can also tweak the colors corresponding to each status here : /Config/Export/G940leds/LO-FC2/colors.lua This version has only been tested on Lock On FC2 (patched to 1.2.1) I will check previous versions of Lock On if I have the time. The DCS side I have provided is just a draft, trying to duplicate morg's profile with my implementation. But I can't test it since I don't have it (I'm not ready for a true-hardcore sim yet ^^). If you want to give it a try, you'll have to change the game setting in : /Config/Export/G940leds/config.lua In this file, you can also disable the little intro/outro animations and tune the refresh rate. (Which also changes the blinking rate, because yeah, blinking is implemented ! ) Feel free to suggest other functions you would like to use. You can download the package here : http://www.tardot.net/files/G940leds_1.1b.rar

Really nice work ! I programmed the exports I wanted for Lock On FC2, and it works pretty well. I also made intro/outro animations, just for fun :) Since I wanted to use blinking lights, I followed you recommendations and didn't use coroutines. I first tried to put my code in LuaExportAfterNextFrame() as you suggested, but it was too laggy. I find using LuaExportActivityNextEvent() is a better solution than LuaExportAfterNextFrame(). This way you can use the time interval you want instead of every frame, which I find quite heavy. I use 1.0 sec most of the time, and 0.4 sec when I want to make a light blink. I think I will try coroutines though, to see what the problem with implementing blinking is. Still about blinking, do you think it would be possible to handle such a feature directly in the program, instead of the LUA side ? Functions like SetBlinkInterval=0.4 (I guess a common interval would be easier) and SetBlink=1or (button 1 would blink from off to red) would be awesome ! Another remark : I noticed that with time, using the axes of the throttle (including R1 and R2 wheels) makes the game laggy. I don't know if it due to the duration of the use or the number of missions. Anyway, restarting the program puts everything back in order. Thanks for the good work !