![]() |
|
|||||||
| IL-2 Sturmovik The famous combat flight simulator. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Try JoyToKey.
http://www.electracode.com/4/joy2key...%20Version.htm I use buttons 3 & 4 on my joystick to zoom in & out, it changes FOV with 25 steps per second. Really terrific program. |
|
#2
|
|||
|
|||
|
Quote:
However, it makes little sense to try to implement this into the software, because few people have the same requirements and preferences for keybinds for those functions. As mentioned, there's tons of software you can use, including probably the basic profiler software for your controller, to just bind the joystick button to "F10" (I did the same with my pinky button on the G940, to talk on Teamspeak 2). As for the wep when throttle range, your profiler software might support this. Otherwise it is a bit trickier. In real life in spits, they could not run WEP with open throttle, had to reduce it a bit. Quote:
|
|
#3
|
||||
|
||||
|
Yes, I have the ability to change the FOV in a smooth way.
Download JoyToKey, here is my Config file: [General] FileVersion=37 NumberOfJoysticks=2 Use8Axes=0 UseDiagonalInput=0 UsePOV=0 Threshold=0 KeySendMode=0 [Joystick 1] Axis1n=0 Axis1p=0 Axis2n=0 Axis2p=0 Axis3n=0 Axis3p=0 Axis4n=0 Axis4p=0 Axis5n=0 Axis5p=0 Axis6n=0 Axis6p=0 Axis7n=0 Axis7p=0 Axis8n=0 Axis8p=0 POV1-1=0 POV1-2=0 POV1-3=0 POV1-4=0 POV2-1=0 POV2-2=0 POV2-3=0 POV2-4=0 Up-Right=0 Up- Left=0 Dn- Left=0 Dn-Right=0 Button01=0 Button02=0 Button03=1, 4F:00:00, 25 Button04=1, 49:00:00, 25 Button05=0 Button06=0 Button07=0 Button08=0 Button09=0 Button10=0 Button11=0 Button12=0 Button13=0 Button14=0 Button15=0 Button16=0 Button17=0 Button18=0 Button19=0 Button20=0 Button21=0 Button22=0 Button23=0 Button24=0 Button25=0 Button26=0 Button27=0 Button28=0 Button29=0 Button30=0 Button31=0 Button32=0 (END OF FILE) What this says is that it polls button 3, 25 times per second, and then inputs anywhere the letter "O" (zoom out), which in IL2 is configured to Increase Field of View. Button 4 is inputs the letter "I" again 25 times per second, which gives Decrease Field of View. |
|
#4
|
||||
|
||||
|
MikkOwl,
Thanks for explain, I think that implement these buttons are easy. Sorry. As I use NewView to smooth Pan View, I continue use this for Spit WEP in end of throttle course. My HOTAS is old gameport "USBified", dont have programming software, for Teamspeak PTT I use another software, SVMapper - that allow use toggles switchs, with one mapped function in press and another in release. Quote:
BTW - Tested your new multi-throttle version, 3.2. Work fine. My only problem is related Alt+E to easy the program, for years I use Alt+E to start engine (cause is near to Alt+1, Alt+2, that previous used to select engines). Now every time I hit refly, I unconscious end MikkOw Multi-Throttle when try start engines . now I use with Alt+I - (Alt is "swtich cover"), but my brain... But it is a personal matter, solve with Alt+Tab. BTW- Just to inform: Flying single engine aircraft (ie fighters) using Multi-Throttle (without axis assigned to power in IL-2 Controls>HOTAS) work like when you use one axis, or maybe better, cause with Multi-Throttle I have linear 1/2% increments in power. Thank you. Sokol1 Last edited by Sokol1; 02-02-2010 at 11:56 PM. |
|
#5
|
|||
|
|||
|
Hi MikkOwl, I have something wonky going on with my throttles sometimes, If I take one throttle while both are at 0% and bring it up it works fine but if I park it at 100% and then bring the other throttle up, sometimes (most, but not all) it takes that one parked at 100% and brings it back down to just bring it up again.
its like both throttles on the g940 only run one in game, but if I move them together they then separate again and I get left right movement respectively. Seems to only do this when both are at 0% or both at 100% Very odd, and Ideas, suggestions? Thanks, Ghost33 |
|
#6
|
|||
|
|||
|
Quote:
You might have left one of them bound to 'power' in IL-2 which could cause some wonkiness. I suspect this because to control more than one engine in IL-2 seperately, one must tell IL-2 to 'switch' to the engine one wants to move (if not selected), and then give it the power setting we want to set it to. Assuming the theory is correct, see if you can follow: Device link is probably not as intensely updatingly fast as IL-2's in-game native controller assignments. When you first move up the one that is not bound to power in IL-2 to 100%, all works as intended. But when you try to move the other one (which IS bound to power in IL-2), it will be read first by IL-2, giving IL-2 an instruction to change the power reading to whatever position it is in - but because the 'last' moved engine is still selected (the one moved to 100%) it moves instead! And mere milliseconds later, my software reads the one you are moving as usual, and tells IL-2 to switch engine selection and to set the power to whatever, as it should. And multi-throttle, not knowing that the 100% engine was moved by something else, does not try to update that engine back into the proper position (it only sends updates when you move your controller into a new position, not otherwise). Go check if the suspicion was correct. If so, just unbind it (try binding power to elevator trim or something, then bind that axis back to elevator trim, that clears 'power' from any binds) and you can stop reading the stuff below The software has not used any kind of special 'moving them synced' method since it made the switch from keyboard emulation to device link. I want to try to replicate the issue but your description is a bit unclear to me. 1. Which version are you using of Multi-Throttle? 2. What kind of plane was it - single engined, twin, triple, quad? 3. How did you go about configuring your G940 throttles for Multi-Throttle? Did you UNBIND them both from 'power' in IL-2 as well? 4. The two throttles behave absolutely normal in every other situation for the same engine configuration aircraft? 5. Assuming you have hud log enabled, what does it say about which engines are being selected when moving a throttle and it malfunctions? 6. From what you describe, you put one throttle at 100% and leave it there. Then when moving the other, only the one you are not touching moves? What about the one you are moving by hand, does that one move at all? |
|
#7
|
|||||
|
|||||
|
3.2
Quote:
Quote:
I used the SETUP - G940 BASIC.exe Optional - ENABLE R1 AND R2 AS TRIMS.exe Quote:
Quote:
Quote:
Its odd also because as I was writing this post I fired everything up again and now I cannot duplicate the behavior. It's as if nothing was ever wrong. "THROTTLE_1_REVERSAL_BUG_TWEAK_AMOUNT=1.546" up from 1.508 to what it is above as my % still jumps like 51 53 55 56 58 60 58 56 54 52 51 50 and I was trying to clear it up a bit. Ghost33 |
|
#8
|
|||
|
|||
|
Whatever it was (or wasn't) it appears to be gone and un-replicatable so who the heck knows.
That it moves in 1 and 2% increments up and down seems to be something about the math that IL-2 uses to read controls. One needs devices with massive amounts of resolution (if one changes sensitivity one can see that it moves in 1% consistently, on devices with already high resolution, but not otherwise). I suppose that the different numbers you see on the way back could be either the strange IL-2 math or that the reversal bug fix is slightly too much or too little, so you might be able to get it completely consistant with some of that tweaking. When tuning the amounts originally myself when seeing if it could be done or not, I used the AutoHotKey (the programming language I made this stuff in) debug features where I could see the exact indicated positions of the axes, and then I would check how much one 'normal' step was, compared to how much the fix was 'off', then adjusting over and over until they matched almost exactly. But each throttle was a bit different, and other throttles can be too. Unfortunately for you there's no way to see the numbers straight, all you have to go on is the in game %, which could be unreliable. Either way, changing that value by some fraction cannot be responsible. Even if set to crazy amounts it would not influence the other throttle in any way. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|