Problem with keymapping for Lock On

[Bluebeard]

I recently bought and loaded Lock On and began to create a keymap using CM 3.0 for my Fighterstick, Pro Throttle and Pro Pedals (all USB). When I tested the partially completed map, many of the programmed functions did not work properly in-game. The corresponding keyboard inputs work normally. For example, the air brake toggle, programmed to Hat 1 on the Pro Throttle as the default "b", works to deploy the brake but does not work to close it. The landing gear key (g) does not operate the gear at all (although I see a quick flicker on the undercarriage of the plane near the gear doors when I hit the Pro Throttle button). The same problem exists with several other key inputs. On the other hand, several of them work fine with the Throttle and FIghterstick. Autopilot (a) seems to work, panning and recentering (programmed to the ministick) work fine, and Cockpit view (F1) works fine. The pause key (s) pauses the action but will not restart it. On that one, I saw a note in the LOMAC readme file that some USB keyboards have trouble controlling the pause function with the s key. So maybe that issue applies to any USB input device, like the Pro throttle? All of these inputs work properly when using the keyboard.
I'm running Windows 98 SE on a Pentium system. I'd appreciate any help I can get with this.

[531_Ghost]

Are you all patched up? Altho, LO-MAC when I was running Win98 had issues with with that OS. Then again LO-MAC didn't remember keystrokes assigned to controllers either before the latest patch. NOW LO-MAC sometimes remembers keystrokes assigned to controllers and sometimes it don't, for me anyway. It's probably nothing you are doing wrong (unless you aren't patched), I've found it to be the game itself. Wish I had better news for ya but....

:cheers:

[MichaelCHProd]

Some commands say they are "Shift /" but they should say that some of them only work for "LEFT Shift /". I have foudn this on more than one key and this alos holds tru for some of the "ALT" modified commands.


After you patch you might want to go into LOMAC and check them with your keyboard.

[Bob Church]

Just to add a little on the shift, the default is left shift for "SHF /". For a Right Shift you have to use "HOLD RSHF /", for example. That may also take CHARDLY in some cases to get things spaced out a little. Also, in most cases the shifted character will accomplish the same thing, e.g. "SHF /" sends the same thing as "?" and automatically inserts the delay between the SHF and the character itself.

A couple of other notes, I don't know if they'll make any difference, but try raising or lowering the Character Rate setting and try putting a NULL on the thing so it only sends one. A high frame rate (takeoff, looking at blue sky) combined with a slow character rate can cause the sim to see two characters in a hurry. For toggled things they can go down and come right back up again before you know it.

- Bob

The StickWorks
http://www.stickworks.com

[Bluebeard]

I really appreciate all the responses. I should have added that I have loaded the latest patch (version 1.02). One strange thing, though--when I try to open any of the document files added by 1.02, Word reports an error. Before doing anything else, I will download the patch again and reload the game, in case something was corrupted in my copy of the patch. I'll report my progress after that. Thanks again, guys.

[Bluebeard]

I wanted to let you know the outcome of my efforts to get LOMAC to accept key inputs from the Pro Throttle and the Fighterstick. After reloading the game and trying every programming idea in CM 3.0 that were suggested in you Replies and everything else I could think of (to no avail), I started trying illogical things. And everything works now! What worked is going into the game's options and clearing the key inputs that I want to control with the CH devices. SO, in-game, it appears that no key is assigned to those functions. Now, both the default keyboard inputs and the programmed CH devices control every function normally. So, I think you could say reverse psychology of a sort works on LOMAC--at least with my W98SE configuration. There must be some technical reason why that works but it's beyond me. Thanks again for helping me think through this. (Now, if I could just get better frame rates...)