MikkOwl

Very strange about that controller switching like that. MT doesn't set flaps at all (but it can set prop pitch if one sets it to). Hmm. I don't know. Maybe it is the profiler as you said. It is possible to switch axes around between mode 1, 2 and 3 in the profiler for the G940, which would totally switch the use of those things depending on what mode one was in, and depending on the mood of the profiler (Haven't had good experiences with it). The profiler itself has a major bug in it when set to "apply persistent profile" where it keeps switching to mode 1 when editing other modes, and then switching back if one happens to move any axis on the controller being set up. I'd go out on a limb and say this switching is probably not due to MT. The throttle LEDs: are programmable (supposed to be from a game). There is a master switch for them in the windows control panel > game devices > G940 throttle > advanced (I think). MT doesn't use the master switch and it is probably not involved in your troubles. But, the G940 throttle seems to remember the last lights it was set to have. MT shuts down the lights when not in the cockpit/flying, and when exiting the program. Since nothing else is telling them to change color, they remain dark for you. Solution without MT should be to either just unplug the throttle from the comp (and the G940 stick), and then plug it in again. It does some red/green light up routine, then sticks in green mode. A better solution is to go into your program > logitech > Gaming software (if you have it) > and look for the JoystickSDK. Unpack it, and run the demo program contained within. It's a little app Logitech supplied to demonstrate the color changing features. Can set them to anything from there and they should stick until something else comes along changing them. Trims on the base = yes, it sucks. I don't accidentally touch them, but it's a hell of a stretch to reach them with the left hand (stick is mounted on the right side, near the thigh) and to manipulate them accurately while trying to fly straight. And just forget about taking the hand off of the stick to use the right - stick will sag forward and left when released and my plane will head for the comfort of mother earth at 480km/h. In my case, I set elevator trim to R2 (throttle) and rudder to R1. Aileron can use the knob at "TRIM3" on the stick base. This sorts out the accidental stuff. If you want trim realism, nothing beats those 900 degrees sim racing wheels set on the left in the correct position and assigned to elevator trim I'll put mine back as that for SoW for sure. __________ I knew I forgot to mention something. The G940 stick sagging and the plane reacting like that, meant one has to fly gripping the thing the whole time if online (no pause button). That's fatiguing for the hands and plain not healthy. Also inconvenient. Even if the plane is perfectly trimmed, taking hand off stick = dive and roll left. ---- When removing the damned reversal bug from the stick in new MT, I put in a feature for locking the stick position in complete center. The pinky button toggles setting the output to center. This means if I am not maneuvering, I press the pinky once and can completely let go of the stick. Then I can work the trims to fly perfectly straight, set the engine levers right, grab a cup of tea, check email on the phone, get up and let the cat out of the room, take a piss etc... And the plane will still be flying straight when I get back (or at least hasn't nose-rolled into the ground). Moving the stick around in this mode does nothing. Tapping the pinky button again re-enables the stick movement as normal. For me, this removes a big pet peeve about the G940 stick and makes flying a -lot- more comfortable. Earlier I could barely look down on the throttle base on the low left without starting to veer off. Reading printed real maps was also a no-no (and I want to do that! Realism immersion ftw). I'd love to fly with you people sometime. Need to get my computer back in working condition first, and hopefully get the new MT out the door with it.

Hello all. I'm gratified to hear all the positive (and of course, negative) commentary on that piece of software I made. The negative is particularly interesting. I apologize in advance for the long post, but there is a lot to reply to. Based on some feedback from Kimosabi earlier, as well as my own desires, I had worked on the next version which would probably address a lot of the bad sides. Most of the main improvements were done, but only functionally, not polished and user configurable properly etc.. And then, my damned C: drive started dying. Bad sectors, read errors. Already got a replacement drive and saved most of my data, but I only have Linux (Ubuntu) working at the moment. Yeah, it works for any hardware that is directinput. Not sure if it can replace that Saitek profiler completely though. Depends on what you want to do. It's not really meant to be a setup program to replace what we have, but instead complement and add to what we don't have. For example, using individual toe brakes on rudder pedals that support it. I'd like to think that another big feature is the trim tuning that is possible (can limit the range, and move the range so it is only left of center, for example, making trimming much less overly sensitive, and being able to make use of the whole range of the device trim wheel/etc). Especially though, it fixes a lot of crap with the G940. You are an awesome man of integrity, Kimosabi. This would be a show stopper. The only time I have heard reports (or seen it myself) of controls performing different functions at the same time is when the same axis was bound to something inside of IL-2 natively too. In each case that was the issue and it was sorted by making sure axis was not assigned in IL-2, etc. If it isn't that though, then I don't know - must be something I'm not seeing. This is the only reported case so far. Especially due to Kimosabi's generosity and feedback, I made a very major effort to address this issue. Procedure to run the next version of Multi-Throttle changed to the following: At ANY point, one just runs the launcher app. Whenever. Its icon appears next to your clock in the task bar and a little taskbar msg lets you know that it is standing by. Takes no CPU and only a few megs of RAM. And that's it. Can shut it down when not needing it if one needs the few megs of RAM. Can be started before or after IL-2, makes no difference. Can start it hours ahead if one wants. There's nothing to click, no ALT-E to exit, no pop-up windows. Behind the scenes, this little launcher app just waits for IL-2 to be running, and then runs whatever parts of Multi-Throttle it needs. Completely hidden and in the background. No more console (DOS) windows or anything else. If alt-tabbing out of IL-2 one can see a few more icons in the task-bar next to the clock, but that's all. It similarly also shuts down all the processes it needed to function when IL-2 is closed. Remaining is only the tiny launcher, waiting for the time IL-2 is launched again. I tested this pretty thoroughly to make sure it really works and I think I managed to make it rock solid and stable. Can alt tab, start this and that, close, alt tab more, open, close etc, seems to always work the way it should, in game and out. I think this is more in line with what people really wanted it to work like. Took a bunch of time and resources away from other features, but it seemed important enough to warrant it. I can understand if it seems complicated. It used to be really bad before. The current version isn't so bad though, and the next version makes it very straightforward. Just unzip, edit conf.ini file to activate devicelink, run SETUP and bind your controls, start app/IL2 (in any order). Just have to remember to not double assign controls in the app and in IL-2. Any future uses is just remembering to start it. I don't agree with the devicelink speed objections though. Not sure what it is you need it to do so quickly. The response time from you moving a controller to it being sent into IL-2 is measured in milliseconds mostly, which is pretty close to the default IL-2 response time. And it is mainly used for trims, throttles and toe brakes (and radiator on axis if one wants, and prop pitch, and in some versions, fuel mixture on axis), which cannot move instantaneously in IL-2 (there's a limit on how fast trims move for example). It sends controls very quickly to IL-2, and reads them a bit slower (not really relevant for much since it doesn't have gauges or other real-time data showing. Except I suppose light changing on the G940 throttle buttons, but it's not exactly time critical for them). They are implementing three features that my app has: Multi throttles, multi-prop pitch and radiator on axis. They are not implementing: 1. More advanced trim options (offset from center, range) 2. Fuel Mixture on axis (not really activated in the recent versions of my app, so doesn't quite count) 3. Toe brakes/differential braking 4. G940 LED support 5. G940 reversal bug removal from axes 6. Individual prop feathering 7. Individual Engine start/stop 8. G940 throttles sync adjustment (they tend to not match their output completely, but I made it possible to tweak their positions to match) New version contains one button fov changing, with precision mode activation for TrackIR if one has such a device, when in the zoomed in mode. Also contains reversal bug removal for the G940 stick and rudder (a hell of a lot easier to do precision aiming I find) They are bound to the rudder. But only some planes worked like that in WW2 (Brit planes in particular, like the Spitfire). Luftwaffe planes tend to have toe brakes instead. IL-2 does not support toe brakes, which is where this app comes in. It has to manipulate the rudder and the brakes to get the results, but it works pretty much as it should in practice. I have to agree. In IL-2, which is very simplistic in engine management and overly forgiving, it's more of a novelty/immersion thing than a necessity. In reality, I doubt the throttles were 100% linked and the engines identical, and engine damage and problems were far more likely. The pilot would look at the manifold pressure gauges when moving the throttles to make sure the pressure matched rather than the sticks themselves. I'm sure this will change with Storm of War.