Logitech G940

[Stanger]

Wow thanks for the quick reply. I see you like to tinker with things. So do I. I have a lot of spare time on my hands. The group I fly with is AG-51. We are a Pacific carier operations with 20 active members. We even meet once a year for a tailhook lan party.

I see you are a moddeler. We have one fellow on our squad I think he does it full time. lol. Post a pic when you are done with that Hellcay if you like. Love to see it. My fav plane is the P-51.

O yea I think my shaking is mostly from the plane shaking from the guns firing. It is like a double effect. I want the shake becuase I want to feel the edge of a stall. I noticed how wing mounted guns shake a lot more than nose guns in which it should. When you take shake out it will shake just a little bit when you use guns. Put shake back in and when you use guns it is a lot worse. Seems like a multiplier thing going on.

If you need some one to help with the tinkering or a tester with this project on the g940 let me know.

Thanks again.

[ECV56_Guevara]

I got a 940 since about a month. I got an issue whit the FF: The FF disengages sometimes an re engage a few minuts later later. Any clue? thanks in advance

[MikkOwl]

Good news everyone - managed to make autohotkey (the program I use) to control the leds on the G940 throttle. So far it's not connected to the game however and so I can only control stupid things and assumptions like "press landing gear button = turn it yellow. wait 5 seconds then red" or "arm cannon = turn it red" and other things. Could get 'out of sync' compared to what is really going on in the game but would be better than nothing.

Working on getting info from game through devicelink to make the game info be able to affect the lights. Difficult...

I did manage to get my G940 throttle to control throttle in game using devicelink as well, but not two engines yet. WOrk work work

[TheGrunch]

Originally Posted by MikkOwl

I did manage to get my G940 throttle to control throttle in game using devicelink as well, but not two engines yet. WOrk work work

DeviceLink is definitely the way to go, MikkOwl, thanks for the heads-up on Autohotkey, though, I've been using it since you mentioned it.

[Stanger]

Originally Posted by MikkOwl

Good news everyone - managed to make autohotkey (the program I use) to control the leds on the G940 throttle. So far it's not connected to the game however and so I can only control stupid things and assumptions like "press landing gear button = turn it yellow. wait 5 seconds then red" or "arm cannon = turn it red" and other things. Could get 'out of sync' compared to what is really going on in the game but would be better than nothing.

Working on getting info from game through devicelink to make the game info be able to affect the lights. Difficult...

I did manage to get my G940 throttle to control throttle in game using devicelink as well, but not two engines yet. WOrk work work

Thanks for your hard work, care to share that hotkey mod to control the lights.

[JG301_HaJa]

Great work. It's people like you that drive this great hobby of ours to new heights and joy.

Keep it up but don't overwork yourself I imagine you have a life outside in RL aswell..

//
Håkan

And this must be a sign of old age since I forgot posting a similar comment in the other thread you made LOL.....

[MikkOwl]

Some progress on pulling information from devicelink (IL-2 thus) and getting it to autohotkey, but it is damned difficult. I can't get it to talk directly to autohotkey, working on solving that.

At the moment the current setup is making use of the following:

"G940Leds110" - A program made by another hobbyist for making leds work with the Ka-50 black shark simulator. Part of it is an executable he made (I suppose) that listens on a UDP port for commands sent there, and then changes the lights when recieving valid commands.

"GUI NetCat" - a little program that allows connecting to the left and right using TCP and UDP.

"AutoHotKey" - The scripting program I've been using up to this point. It's like c++ but with a focus on interface things and controllers.

"IL-2 Device Link" - the part of the game that can listen and send UDP packets with information.

I set one instance of NetCat to connect a path to IL-2's device link. And this NetCat is partially connected through 'piping' with one instance of AutoHotKey that is set up to send the 'right' commands to IL-2. This is the way to send throttle inputs and all that stuff.

Another instance of NetCat is set up connected to the G940 led program by the other amazing fellow, and it too is 'piped' to another AutoHotKey script, which is set up to send the right LED color commands at the right time.

I can get the first NetCat+Devicelink to output the 'answers' from IL-2's devicelink to a text file, but I have not gotten further than that. I need to get it into autohotkey so it can get info about the status of your instruments/plane in the game, and then pass the info along through this path into the G940 led changing program, changing the leds.

Skipping all the IL-2 related stuff, it is much easier to get the autohotkey programs to talk to the led changing program and making it change colors. I already set up some stuff for myself - I have three seperate buttons on the throttle base set up with the following names. "MG 17", "MG 151", "AUFRÜSTEN BOMBEN". They each control the arming/safety of these weapons (I fly the bf 110G2 mainly). When they are not armed, the lights are off. When armed, the button goes yellow. It's very neat.

I also made the landing gear button work somewhat. Labeled "FAHRWERK" (Such a Luftwaffe theme isn't it? haha). It just assumes that when you start you are on the ground with gear out, and the button is green. Clicking it makes it dark for about 6 seconds (and that's normally how long your gears take to rise in game), then it goes red. Much like the indicator in the luftwaffe plane cockpits.

Airbrake, tailwheel lock, instrument lights, prop pitch manual override - similar story.

It's better than nothing for sure. But I'd like to get the info straight from the game somehow... I don't know how to do it yet. I'm not a real programmer. When reading formum posts and instructions about all these things, it's like 90% gibberish.

A shitty thing is that the devicelink connection offers almost nothing and has similar limitations to using the keysending in the current multi throttle versions I made. It works in the same limited way, have to select engine 1, send new value. Select engine 2, send new axis position. Only real difference is that you can send the exact lever position instead of the closest 5% position, which is barely any gain. But you don't have to bind any keys, freeing up those keys to use with mods and other stuff. That was disappointing.

The G940 led controlling stuff is NOT user friendly or even customizable at this point, and I don't know how to make it that yet (everything would be 'hard coded', only be able to launch it and it will change lights the way I set them to beforehand, nothing you could change). I'll work on it a bit and see if I can make it customisable enough to be able to set stuff up a bit more to your liking. Believe me though, it goes a very long way to just 'guesstimate' what's going on with your systems as long as it 'starts' from the correct position (so they are synced). When you hit 'refly' you hit a reset button to reset all the lights/guesstimation assumptions. So even without device link, it's still highly useful.

[Matze81]

My question is not Il-2 related, but I would like to know, whether the throttles of the G940 have an afterburner detent?

[MikkOwl]

Originally Posted by Matze81

My question is not Il-2 related, but I would like to know, whether the throttles of the G940 have an afterburner detent?

The big post by myself on page 2 covers this. Go there and search for 'detent'.

[Matze81]

Originally Posted by MikkOwl

The big post by myself on page 2 covers this. Go there and search for 'detent'.

Thank you!