Making Elevator Trim work in FS9

[Bill Clark]

WBK,

I did the PM thing......so I'll wait to see what develops.

Maybe I'll get lucky!

BC

[Bill Clark]

WBK,

As you can see I have not given up on this NUMPAD issue yet!

As another approach, I took the time to install a "pristine" version of FS9 on another, older computer I have running Win XP. The installation of FS9 in this case has no add-ons, except the SP1 that Microsoft did later to correct some missing bridges and some other minor bugs. I also installed touch screen HW and TB software........ran it in "Local" mode.

What I discovered, is that no matter which set of TB commands used (all the commands suggested by you listed above in this thread, as well as other combinations I came up with ), I essentially got the same results as before.

However, I did try something different this time, while FS9 was running in "windowed mode" I noticed that I could open up the "Controls Assignments" dialog box in FS9 and select any command to initiate a new keystroke assignment.

What I discovered is that FS9 is always seeing the following input, which is "SHIFT + Num 1," whenever I sent commands from TB. This happened every time, regardless of whether the Numlock LED indicator on the keyboard was on or off. One of the command strings was as simple as sending macro = predef:NUMPAD1. It should have only seen "Num 1".

Conclusion - It appears that either TB is automatically adding a shift to the NUMPADx number, or FS9 is?

What are your thoughts on this? Any other ideas?

Bill

[Bill Clark]

WBK,

Have you had a chance to look at my post above on another test I ran last week?

I have attempted to contact others via forums and also PM'ed others on this forum about Microsoft flight sims, but I haven't been able to conclusively determine if commands involving some NUMPADx numbers just don't work with TB. But based on my new results, it looks like something is broken, or else I'm still doing something wrong?

Anyway, I just thought you may have missed my post.

Regards,
Bill

[Wild.Bill.Kelso]

Hmmm... Yes, I did miss that post, so I replied yesterday.. But I don't see my post! Maybe I didn't click submit??

Anyhow, the only thing I could think of is that maybe the Shift key is left pressed down by some other command. Is the Numpad 1 button the first one you try every time, or is there some other buttons you press first that may be leaving the shift key down?

In my FS9 profile there are several Shift keys used.

If TB is holding the Shift key down, then if you open notepad and type a letter: a, b, c... it should be in capital letters I would think. I just tried that with your 'Bingo' FSX profile and didn't get any caps. I also tried it with my FS9 profile, pressing buttons and the 'x' key and got this:

1xxxx7xxxxxxxxxxxxxxxxx7xx1xxxxxxxxxx1xxxxxxxx1xxx 7xxxxxxx1

No caps here, but of course I didn't press all of the buttons in the profile. I did search both profiles in notepad for the 'shift' command and didn't see any of them left down. But it appears my FS9 profile does send the numpad 1 and seven keys to notepad just fine.

macro = rawkey:NUMPAD1, EXTENDEDKEY
macro = rawkey:NUMPAD1, EXTENDEDKEY | KEYEVENTF_KEYUP

macro = rawkey:NUMPAD7, EXTENDEDKEY
macro = rawkey:NUMPAD7, EXTENDEDKEY | KEYEVENTF_KEYUP

Have you tried just making a simple profile with only these 2 trim buttons in it? That should be a good test on your 'pristine' FS9 computer.

WBK

[Bill Clark]

Originally Posted by Wild.Bill.Kelso

Hmmm... Yes, I did miss that post, so I replied yesterday.. But I don't see my post! Maybe I didn't click submit??

Anyhow, the only thing I could think of is that maybe the Shift key is left pressed down by some other command. Is the Numpad 1 button the first one you try every time, or is there some other buttons you press first that may be leaving the shift key down?

In my FS9 profile there are several Shift keys used.

If TB is holding the Shift key down, then if you open notepad and type a letter: a, b, c... it should be in capital letters I would think. I just tried that with your 'Bingo' FSX profile and didn't get any caps. I also tried it with my FS9 profile, pressing buttons and the 'x' key and got this:

1xxxx7xxxxxxxxxxxxxxxxx7xx1xxxxxxxxxx1xxxxxxxx1xxx 7xxxxxxx1

No caps here, but of course I didn't press all of the buttons in the profile. I did search both profiles in notepad for the 'shift' command and didn't see any of them left down. But it appears my FS9 profile does send the numpad 1 and seven keys to notepad just fine.



Have you tried just making a simple profile with only these 2 trim buttons in it? That should be a good test on your 'pristine' FS9 computer.

WBK

WBK,

Thanks for your response!

I tried this command sequence (but not on my pristine system) and I did not find any evidence of the Shift key being held depressed. It was also the first command attempted. I verified this by only being able to type the lower case characters, I got no capital letters.

I did notice, that when pressing the touch buddy buttons, it would send either a "1" or "7" to Notepad no matter if the NUMLOCk key was on or off. If I purposely held down the shift key, nothing was sent to Notepad. However, Notepad would show either a 1 or 7 when TB sent characters if the SHift key was not depressed.

I will set up my "pristine" system again, but I believe I will get the same results.

This one is wierd,
Bill

[Wild.Bill.Kelso]

Also, maybe test a new profile with just those to numpad buttons?