Making Elevator Trim work in FS9

[Bill Clark]

WBK,

It should work for both with a few exceptions......once I get all the bugs out, I was going to modify it for FS9.

The Trim Commands are the same for FS9 and FSX.

Bill

[Wild.Bill.Kelso]

Basically, it looked ok. I changed the Trim Up to use a Touch and repeat sending the Numpad7 key repeatedly as long as you touch the button. This type of button could have 2 images for the up and down state if you wanted. It worked fine with the Calculator.

I changed the Trim down to be a 'Hold' button with 2 images. It just sends the keystroke once.

I don't know what else to tell you. I think I do remember FS9 needing the Numlock on or off maybe depending on what your doing. But it seems to me that TB is working as intended and sending the keys. If it sends the keystrokes to the Calculator and also to Notepad, then TB is doing it's job I think...

[Bill Clark]

Wild Bill,

This profile will work for both fs9 and fsx.....with a few exceptions.

Trim is the same for both flight sims.
Bill

[Bill Clark]

Bill

I thought I responded earlier to your question.

The profile should work for both fs9 and fsx, with some exceptions.

Trim is the same for both fs9 and fsx.

Bill

[Bill Clark]

Originally Posted by Wild.Bill.Kelso

Basically, it looked ok. I changed the Trim Up to use a Touch and repeat sending the Numpad7 key repeatedly as long as you touch the button. This type of button could have 2 images for the up and down state if you wanted. It worked fine with the Calculator.

I changed the Trim down to be a 'Hold' button with 2 images. It just sends the keystroke once.

I don't know what else to tell you. I think I do remember FS9 needing the Numlock on or off maybe depending on what your doing. But it seems to me that TB is working as intended and sending the keys. If it sends the keystrokes to the Calculator and also to Notepad, then TB is doing it's job I think...

Bill,

I installed touch screen on my Flight Sim PC (now in local mode) and I'm still having issues with Numpad7 and Numpad1.

In fact, I even downloaded your zip file and copied your version of the .TBC file where you used the following command into my system:

macro_select = predef:NUMPAD7

Note - I tried this with numlock on and off and it still failed. The manual keyboard command Numpad7 will cause the trim wheel to move. The macro_select keystroke you used caused the view to flash quickly and then it returned to the view originally selected.

I even opened up the Microsoft Calculator and it accepted the Numpad 7 inputs. The flaps and other functions work, it is just the commands with Numpad that are causing fits.

Sorry my issue is such a pain......
Bill

[Wild.Bill.Kelso]

So, the profile works, and sends the numpad keys to the Calculator and to Notepad? Then TB is working it seems.

Maybe try this in Windows Safe mode? Maybe you have something else runnng that is stopping TB from working with the game?

[Bill Clark]

WBK,

A summary about the Numpad key issue:

1) I experience this issue (Numpad 1 and Numpad 7) under both FS9 and FSX and in both local and client/server modes.
2) Also, other TB commands (like flaps, views, etc.) works ok with both FS9 and FSX.
3) Falcon AF 4.0 uses quite a few of the Numpad commands without any problems. The window environment for Falcon is the same as for FS9 and FSX
4) I don't have any other applications running, at least that I'm aware of, while troubleshooting this issue.
5) In FS9 I have the following add-ons (Genesis mesh scenery, Southern California Megascenery, LevelD 767, Traffic 2006, and Ultimate Terrain)
6) In FSX I have SP1, and Acceleration.
7) I'm running TB Version 1.3, version 4

Some questions for you:

a) Did you actually test my profile with either FS9 or FSX?
b) Are there many other users running TB, at least you are aware of, in either the FS9 or FSX environments?
c) Have many FS9 of FSX users ever run across this issue before.....there has been no feedback except from you?
d) Any other suggestions you can offer?

My opinion, with limited knowledge at this time, would suggest that there is an incompatibility between TB and Microsoft sims for certain keypress combinations?

So far my combat sim profiles (IL2 and Falcon) work great........this is really strange!

Bill

[Wild.Bill.Kelso]

Originally Posted by Bill Clark

Some questions for you:

a) Did you actually test my profile with either FS9 or FSX?
b) Are there many other users running TB, at least you are aware of, in either the FS9 or FSX environments?
c) Have many FS9 of FSX users ever run across this issue before.....there has been no feedback except from you?
d) Any other suggestions you can offer?

My opinion, with limited knowledge at this time, would suggest that there is an incompatibility between TB and Microsoft sims for certain keypress combinations?

So far my combat sim profiles (IL2 and Falcon) work great........this is really strange!

Bill

a) No, I didn't as I don't have either of them installed.
b) I have see a few posts of other users using both FS9 & FSX. If you do a search you could maybe PM them and as them about these problems.
c) I have never heard anybody post this problem.
d) Ask some of these other users who are actually doing what your doing. Maybe PM them...

Sorry, I can't help more. If you find the fix or your problem, please post it here, as I am very curious...

WBK

[Bill Clark]

WBK,

As per your suggestion, I'm going to PM all the FS9/FSX users who have posted on your site. Also, I plan to post a similar message on the major Microsoft flight sim forums to see if I can get some help or ideas from the general community.

Do you have any suggestions as to wording or anything else?

Bill

-----------------------------------------------------------------------

Hi,

Wild Bill Kelso, the TouchBuddy forum administrator suggested that I PM you and others to see if you have experienced similar issues regarding TouchBuddy use with either FS9 or FSX.

The crux of my problem is that I have been unable to send elevator up/down trim commands to FS9 or FSX. When I do send a command, all that happens is that the view changes or flickers, but the trim wheel does not move at all (when viewed in the virtual mode with the view).

To move the trim wheel in manual mode, via a standard keyboard, all that is necessary is to do the following:

1) Turn off the Num Lock pressing Num Lock key (if Num Lock light is on)
2) Press either Num Pad 1 or Num Pad 7 to cause the trim wheel movement.
3) Turn on the Num Lock by pressing Num Lock key (if Num Lock light was previously on)

I have tried the following TouchBuddy commands both in the Client-Server and Local modes without success:

Example 1 (type = button)

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

Example 2 (type = button)

macro = predef:SHIFT, KEYDOWN
macro = predef:NUMPAD7
macro = predef:SHIFT, KEYUP

Example 3 (type = hold)

macro_select = predef:SHIFT, KEYDOWN
macro_select = predef:NUMPAD7, KEYDOWN
macro_deselect = predef:NUMPAD7, KEYUP
macro_deselect = predef:SHIFT, KEYUP

Here is what works, Num Pad keys work with Falcon 4.0 Allied Force

Here is what I think, if any of you have been able to make the trim function work, then I have to suspect there is a issue with my FS9 or FSX configuration or add-on causing this issue.

-------------------------------------------------------------------------------------------------------------

So what I'm looking for from you as help:

1) Have you experienced this before, if so, is there a solution or workaround?

2) Any suggestions as to any other command sequence(s)?

3) Any ideas on how else I can better troubleshoot this?

Bill

[Wild.Bill.Kelso]

That looks good to me...