I wish there was more info that could be gotten by devicelink to be used to control the G940 leds. Most of what is allowed to be read when in multiplayer is added... but I want to add more. I have some ideas on how to figure out ways to make very accurate guesses on the state of some systems. Like nav-lights for example. There's no way to read if nav-lights are on or off. But I have found ways to check if someone is in control of an aircraft or not (already implemented), but also a check on if the plane type can be read or not. If it cannot be read, it means that the player has not even selected or loaded up a plane. Soo, using a combination of the two above, I could make it, for example, switch nav lights only when allowed to, and reset the guessed state of the navlight system to off each time it is clear the player restarted the flight. I don't know if this makes any sense to anyone, but it does to me, and it can probably add many more systems.
The current wishlist for 4.1 (definitely not adding the whole list!) is:
1. Separate engine-off button for each engine (requested by sokol - I just didn't have the time to do it and get the release out with all the other things I added)
2. Add more systems for the G940 leds, through guesstimation.
3. Make the LED assignments also trigger the function they were assigned to. For example, WEP button triggers WEP, gear triggers gear. Now they only assign the lights inside the buttons, not the function itself. It could save time if people can just assign the function directly through multi-throttle (quick to change between planes, just alt-tab, close M-T, run setup, etc).
4. I would like to have separate trim tweak profiles for different planes available. This is planned for Storm of War, but I already have some neat trim tweaks implemented - just need to add the (quite large and complicated) infrastructure for loading them in multi-throttle, the setup program, and editing them, and saving them. I think that limiting the amount of profiles and all the variants of the planes can be done by reading keywords of the aircraft's name. Like one profile can be 'spitfire', and includes all spitfire models. Another is 109, another is 110, another B-17, another P-51, P-47, P-38, LAGG, Pe-2, Fw-190, Ju-88 and so on. That will allow us to have our trims tweaked just right for different planes.
5. If I add profiles for aircraft, then maybe also be able to add LED button assignments saved in the profiles. Means the buttons could change their LED light display, as well as their function, depending on the type of aircraft.
6. Perhaps integrate some of my previous work. For example:
I made a music player that allows you to play pre-defined tunes for what is going on around you (to match the setting) by the use of one top hat. I tried this myself, thinking it would be cool. It was cool. But I am already too nervous online and this made it crazy nervous.
Need all my concentration just on flying.
A smooth fov switcher that can use a single button to zoom in and out between wide and realistic fov, and if held for just a moment it zooms in maximum (and also makes TrackIR go into super smoothing mode, making the view very stable). This function was quite useful, as it takes up only my S4 (middle left) thumb button on the G940 and controls all my viewing and does it in a logical, fast and easy to control way. I had many different versions for viewing in the past until I arrived at this configuration. Before I had smooth fov switching, I would lose sight of enemy aircraft when zooming in maximum, because the zoom is the 'middle' of the screen and sometimes I was not centering the enemy aircraft in the middle properly. Zoom being instant, I saw an empty sky and could not determine where the enemy was. With smooth zooming it was easy to see where I was looking.
Made a stay-in-cockpit-view-when-bailing-out, with a sound effect of trying to jettison the canopy and loud wind noise. In fact, I also flew online with this and added the feature of muting teamspeak completely as soon as I bailed out. This meant no one could hear me after I bailed, and I could not hear them either.
Safety switch for weapons. Can be a master-arm button for all weapons, or individual (it's not complicated). In this way, a single joystick button (the trigger) can be made to fire MGs or cannons, or both, by arming and disarming the weapon systems individually.
Scroll in-game map by using a top-hat. I made it and it works, but only on my monitor display resolution. Uses mouse emulation to click drag the map around. And I don't think it was practical. Reaching for the mouse was much faster and better, sadly.
Function not yet made, but possible to do: Read the log file generated by IL-2 (in real time when flying). And using that data, I can make the rear gunner in planes like the Bf 110 and bombers speak a little bit in multiplayer. Only some of the things they can say in single player.. But even that is better than complete silence. They can scream if wounded or killed, and they can comment on when targets are destroyed or aircraft was shot down "Target destroyed, great hit!". And only if they are still alive. Not really anything else. I most of all wish that they could speak if they see an enemy plane but that's not possible to do.