|
|
#19
01-16-2010, 02:04 AM
|
|||
|
|||
Mega-reply
Quote:
Quote:
Speaking of IL2 with G940 and TrackIr5 - I keep trying to optimize the way the view controls are set up. Current revision is programmed to make use of the mid-stick thumb button "S4" - clicking it toggles between wide fov and 'realisticformymonitorsize' fov, while holding it sets maximum zoom and the precision mode in TiR5 - until released, when it reverts to whatever fov mode it was in before. Seems to work fairly well. The lower castle hat on the stick (push right) is TiR center. I found that it's very easy to push the hat to the right from the left with the thumb (coming from the red thumb "FIRE" button), not having to place the thumb inside the hat. Pinky button for radio transmit (just like the real world Fw 190, yum!). One of the backside throttle buttons toggles between gunsight position and 6DoF position. Comes in handy for certain messed up models. And all this of course with autohotkey. I'll mention more about it at the end of the post. Quote:
 Logitech did have some explanations for what the force feedback settings are, but I recall that none satisfyingly explained it until I dug around deeper, especially with some force feedback testing programs + a few manuals for coders of devices (one was for some FF for handicapped people article). I think one of the more important things is finding out by experimentation how spring forces work in IL-2 - that the range utilized is limited to about 130km/h (no resistance) to 300km/h (max resistance). Hopefully Storm of War will have a much larger range and tons of other improvements. Happy to share my findings with others. I get pleasure from helping (so it's a selfish motivation when it comes down to it. Though that's why we do just about everything we do). SDK tailoring of forces though? Are you talking about the .ffe files in the IL2 force feedback folder? There wasn't that much to change there to be honest, mainly just tweaking the RPM and more importantly, power, of the gun effects seperately from all the others. Could be useful though. If I remember correctly you rely more on FF due to having impaired hearing? If so tweaking it right would have more significance than for the average user. I have the opposite problem, hypersensitive hearing (not that I have better hearing than others, I just experience things as louder and distressful). Use a lot of earplugs, sealed headphones and even got hearing protectors that I often wear just to shut up the neighbors and traffic. ---- Throttle LED tips: If you look in your logitech profiler folder, there's a LedSDK app that can be run. You can move this executable anywhere convenient. When run, it allows you to set the colors you want for each button. As far as I can tell, the throttle permanently remembers the settings until you open the program and change them again at some later point. It helps to categorize the functions a bit by how critical they are or what systems are affected. My "Master Arm" button is red, for example. Engine ignition 1 and 2 are red also. When you feel like making things dark for sleep or whatever, you can go into the game controllers in the control panel, open up the throttle device, and click 'advanced' or whatever it is. There you will find a master light switch that turn off all the lights. Repeat to turn them on again (they'll resume the colors you programmed earlier). I hope Storm of War will have LED light support directly. ----------------- Autohotkey stuff: I think people out there still need convincing, so here are a few examples. It is awesome for the G940 (and anything else for that matter). Example 1: having a "Master Arm" switch (G940 shipped with such a cutout paper thingy that I put under one of the throttle buttons): The script is set up along these lines: If the masterarm button is pressed, then toggle 'safety off' or 'safety on' inside the script. Bind the weapon 1, 2, 3 and 4 to numpad 1 2 3 4. When script senses that a stick button is pressed, it looks if safety is on or off, and if it's off, it pushes the numpad key to fire weapon 1, etc. If it's on, nothing happens. It's very basic yet functional and useful. I've had 'accidents' happen, mostly inadvertant firing of a cannon or MG; but also heavier stuff. Ever drop a bomb during take off? Ooops. ----- Bailing out realism: Make you stay in cockpit view when initiating the bailing out sequence, and even play a sound file that has the sound of seatbelts being detached, windscreen being jettisoned and louuud wind noise. It just checks if your bail-out button (a stick button perhaps?) is pushed. If it is, it sends "F1" right away to bring you instantly back to cockpit view, and also starts playing the sound file specified. I made one of my own and it works quite nicely, fitting what is seen. ----- No more mouse map crap: Instead of having to use the mouse (letting go of the G940 stick tends to not have good effects) and click the right mouse button continously inside the map window to go through all the zoom levels (what a pest), and using left click and drag to move the map, have one zoom in button, one zoom out button, and use a hat to scroll around on the map. No mouse involved at all. This one was very tricky to cook up. Mouse coordinates is nearly completely unsupported in IL2, and figuring out how to cause two buttons to send the right amount of rightmouseclicks to either zoom one step in or out depending on the button pressed, but it works . I don't think I can explain it in a short enough text, and in a useful way here.---- Make buttons make sounds when pressed (as well as released): Super easy. Just tell the script to play a soundfile of our choice when a certain button is pressed (and another when released if one so wishes). Turning off the HUDLOG means there's no indicators when WEP is on, when fuel tank is jettisoned, navlights are triggered, engine key bla bla. There's usually not a single sound effect from inside the game to let you know that you did something. Adding a sound effect makes you hear that you did indeed press the button. In my case, I've made it keep track of if wep is on or off, if the safety is on or off, and it plays a different sound file to let me know that WEP Is turned ON for example. In both cases I used a little alarm buzz of the same kind that the Bf 109 uses (sort of) when deplying flaps without the gear down. Knowing that WEP is on or off or the master arm switch, not to mention the rather critical tail wheel lock function, is important, and this is one way to deal with it when getting rid of the HUD Log. ---- Any kind of view controls one can imagine: I have mentioned it before. Tell it to send the max zoom + smooth headtracking button when a certain button is pressed, then upon release, send max fov or medium, or anything one wants. Can cycle through things, make things activate when held longer than a certain time, two buttons held together, there's no limit. ---- Radio commands through single key: Can do this with the Logitech Profiler as well. Just look up what keys need be pushed in what order to send a certain command. Tab + 7 = "help me anyone!". Tab + 8 + 2 = request vector to home base. And so it goes. I have one such similar macro set up to toggle that 'zoom when moving forward with TrackIR' off, as I prefer to do my zooming with keys instead. It requires pushing a numpad * key and then numpad 1 together. Other small things is having right + left mouse button = Escape. Right mouse + scroll wheel up/down is alt-tab (no need to reach for the keyboard anymore). Another useful thing is binding the Trim 3 knob to volume control. Yes, instant volume 'trim', accurately and easily. In this one tells autohotkey to scan the trim3 axis and then to convert the position of it onto the system volume setting something like 10 times a second. Last edited by MikkOwl; 01-16-2010 at 02:11 AM. 
|
|
|
Threaded Mode