morg

Yoda, try to set cockpit resolution to the lowest. You need a very good computer otherwise. Copying memory from the video card to system memory is slow.

hreich: Yes, it is game related, otherwise they very easy get out of sync. So the result will probably be more irritating than useful when just changing off/on when pressed.

E9rendil: No, you will have to change the export script to export the correct data for FC2 Schkorpio: Yes, if you not are happy with the supplied examples you have to configure g940leds.lua.

Anyone know what the Base/distance axis command does? I don't notice anything when i try it.. /Martin

You will have to explain more what you have done and what doesn't work if you want us to be able to help you.

basedow, unless you have a very nice computer it will probably stagger every time the picture is exported. You can try it by just enabling it in the export.lua file.

Glad that it works! I'm pretty sure it was the patch, I think they added some functions for export that used in the script.

No, the leds are completely seperated from what the buttons actually do

Thirdup, you might have missed to enable exporting in the Config.lua file that is located in the same director as export.lua. Or you might have introduced a syntax error when editing in the files, have you checked Ka-50/temp/error.log (path and filename from memory, might be errors.log). If there is an error in one of the lua files it will be at the bottom of that file. Might also be a firewall problem, altough i consider that highly unlikely when udp_sender is working.

ddahlstrom, if you could send your export.lua maybe someone can look at it and see if they can find an error

easiest would probably be to start udp_sender.exe and send "SetAll=g;"

Your laser has probably burnt out. Turn it off as soon as you dont use it and always let it cool down properly!

masterroot, just because the weapons are there doesn't mean you can fire them. If you have bought a plane with working weapons (more like an addon...) it will probably say in the readme/manual how to fire them.

i know how big it needs to be, just to test it in a game that has a good FF implementation (like live for speed)

Yeah, but it's ten times as big as it needs to be. Not allowing the user to adjust the deadband is a big mistake by ED in my opinion. Try live for speed (lfs.net).

Sobek, i wouldn't recommend you to buy one. Wait until ED has released a patch, if they do... Atm i actually use it with the FF power off most of the time. I can never remove the hand from the stick but the precision is amazing.

They are in Ka-50/scripts/aircrafts/Ka-50/Cockpit/mainpanel_init.lua on lines 271 to 287. There also seems to be a switch for only the descend mode on argument 560 (line 154 in the same file)

oops, sorry about that, will fix it. Glad you like it!

Yeah, the coroutine is in G940leds.lua. you have to import it with dofile("./Config/Export/G940leds.lua") before adding it to the table

Here comes the new version! It allows for much more custumization and is ready to add support for more games/functions. I have written a readme as well, and i hope it is understandable. It still has some issues, biggest one being that people who use the mode switch probably wont like that the leds cant change based on current mode. I hope to fix that some day. The default configuration isn't very usable, it's mostly an example of the special commands for DCS. Change 'g940leds_example' to 'g940leds_AutopilotTargetingMode' in export.lua on the line that says 'Coroutines[CoroutineIndex] = coroutine.create(g940leds_example)' to get a more usable version (same as the first version of the program). Note: Requires patch 1.01! Short overview for new people: G940leds is a program that listens on a UDP port for commands about how to light the leds on the G940 throttle. I have written it in a way that hopefully will minimize the need for conditionals and other code in the interface that talks directly to the game (for DCS, the lua code). Since the program itself is written in C++, it is probably alot faster at those things than a script. It comes with example scripts that shows how to use it with it BlackShark. Update: Had made a stupid bug in the G940leds.lua file. Fix uploaded (same name though) G940leds110.rar

Mine is changed someways to fit the new version im working on, so it wont work either. But i think the problem is that you are missing the following rows in export.lua, and they should be before all the other coroutine stuff Coroutines = {} -- global coroutines table CoroutineIndex = 0 -- global last created coroutine index Or you can wait till tomorrow sometime when i will release the new version ;)

First, you shouldn't have to change from localhost (not that it does any harm) The things that pop up is: - Have you activated export in config.lua? (maybe should have mentioned that in my post...) - You didn't insert a syntax error by mistake in export.lua? Check Ka-50/temp/error.log at the bottom, it will say if it failed to load the file.

If lockon has support for using the luasocket module (which i assume it does, or any other udp capable module) it will work as long as you write a script for it

I'm sorry to say i can't keep my promise. I have a working prototype of a better version, but plans have changed and i will be away this weekend and don't have the time to finish it. I haven't searched the forums yet, but is it possible to get information "all wheels locked", "wheels retracted" and somewhere in between? (ie, moving or damaged). I only found information for the gear handle, and thats not very useful. Thankful for any help. And also, if anyone wants a special function (ie, something that is not just a on/off light/switch or lit button(like autopilot buttons, dlink etc)) please tell me so i can make sure it is supported in the first release and if you know, what commands in lua are needed to get the information. I have made a special function for the burst length setting making it different colors for the three settings, maybe that gives you an idea what i mean. Hopefully this post made some sense, i am in quite a hurry...

No, sorry, but in a week it hopefully will ;)