FSUIPC, will it work with TouchBuddy touch screen SW?

[sbclark]

Peter,

I've been using TouchBuddy software for about 4 months now and just love it as it works well with combat sims such as Falcon 4, IL2-1946, and it appears to work well with all the FS9 and FSX default aircraft. However, I have run into problems when I load an A/C such as the LevelD 767. In this case, the panels such as the MCP panel, that have LNAV, N1, LOC, and other buttons just flat don't work. For example:

I'm trying to map key presses via a touch screen using TouchBuddy software to interact with the LDS 767 MCP. For example, the letter "A" I choose for this example is used for "ADF Select" on a default FS9 A/C. However, when running LevelD 767, the letter "A" is re-assigned (by LevelD SW) to select the "Left Autopilot" function. And if I press "A" on the keyboard, the left auto pilot gets activated when in the proper phase of flight. However, when I press the touch screen symbol for Left Autopilot, which is programmed to send an "A," nothing happens. It's as though LevelD doesn't recognize TouchBuddy SW, but it does see the keyboard

To verify what I'm sending via the touch screen, I open up the FS9 LevelD key pull down custom assignment menu, and initiate a change the key press request. Rather than change from the letter "A," I press the touch screen which has been programmed to send the letter "A," and sure enough, the "A" character shows up as the replacement character, thereby confirming I'm sending the correct character, which is an "A." But when the 767 is flying, nothing happens when using the touch screen.

BTW, I can use TouchBuddy touch screen software successfully on many other functions, but certain LevelD 767 features just don't work. I suspect it is due to some sort of key mapping issue?

The TouchBuddy SW website URL: http://www.touch-buddy.com/forums/

So my question is - can I use the FSUIPC to solve this problem?

I'm not familiar with using "Key Presses" tab of FSUIPC, but I have the documentation printed out and I'm willing to experiment.

Any suggestions you have to offer would be welcomed.

Bill

[Pete Dowson]

However, I have run into problems when I load an A/C such as the LevelD 767. In this case, the panels such as the MCP panel, that have LNAV, N1, LOC, and other buttons just flat don't work

...

I'm trying to map key presses via a touch screen using TouchBuddy software to interact with the LDS 767 MCP. For example, the letter "A" I choose for this example is used for "ADF Select" on a default FS9 A/C. However, when running LevelD 767, the letter "A" is re-assigned (by LevelD SW) to select the "Left Autopilot" function. And if I press "A" on the keyboard, the left auto pilot gets activated when in the proper phase of flight. However, when I press the touch screen symbol for Left Autopilot, which is programmed to send an "A," nothing happens. It's as though LevelD doesn't recognize TouchBuddy SW, but it does see the keyboard

I don't know "touchBuddy". What is your input (control) for this?

It may be that the Level D software is reading the keyboard at a lower level than that provided by your TouchBuddy software.

BTW, I can use TouchBuddy touch screen software successfully on many other functions, but certain LevelD 767 features just don't work. I suspect it is due to some sort of key mapping issue?

Not "mapping", just the different method used in LevelD to read the keyboard.

So my question is - can I use the FSUIPC to solve this problem?

Not to convert a keypress into another keypress. FSUIPC offers nothing like that. It can convert keypresses into FS control actions, but I doubt that any of those will operate the LevelD autopilot. The joystick button assignment facilities allow keypress assignments -- whether the latter would work with Level D I don't know, and it wouldn't help in any case unless your TouchBuddy software can provide button presses ...

... actually, I say that, but there is ONE possibility. It is a bit complicated though. If the TouchBuddy keypresses are seen by FSUIPC (which is another question), then you could assign them to internal FSUIPC controls (for offset byte bit set, clear or toggle) to "press" virtual buttons (FSUIPC offers 288 virtual buttons). Then if that works you could assign the virtual button press to a keypress to operate the Level D autopilot -- assuming of course that the Level D software accepted FSUIPC's keypresses, which is another big question.

That's a lot of "ifs".

There is one other possibility. If the LevelD autopilot is amenable to the recent Mouse Macro facilities in FSUIPC, and if FSUIPC does see your TouchBuddy keypresses, then you could use that facility (mouse macros).

That's two more ifs.

Not having either TouchBuddy of the LevelD aircraft I am afraid I can't really help further, unless you need more explanation of any of the above ideas to try them?

Regards

Pete

[sbclark]

Pete,

Thanks for your very fast response!

I'll try to answer your questions as best I can:

First of all, in case I misunderstood one of your comments, TouchBuddy is a separate program effort from LevelD 767 development team and are not connected in any way.

1) First Question: "I don't know "TouchBuddy." What is your input (control) for this?

All I can say is that pressing the touch screen (via TouchBuddy SW) issues key press commands. For example, I can open up NotePad, and if the touch screen icon I touch is programmed to send the character "J," then a "J" will appear in NotePad, or any other text capable program, like MS Word, MS Excel, etc..

2) Second Question: "Not mapping just different method used in LevelD to read keyboard"

That could be, but I'm not as much of an expert as you would be about this. It seems to me reading a keyboard would be the same for all applications. I will say this, I can press the touch screen and can successfully send a key press to any of the following:

a. Any default aircraft within FS9 (including autopilot commands)

b. The custom key press menu within LevelD - the change key press feature recognizes the touch screen activated character sent to it.

c. FSUIPC, when I run it within FS9, also recognizes and accepts a character sent by the touch screen S/W whenever the "Key Presses" tab in FSUIPC is open, and the "Set" button has been pressed . Not only can I send one character, but key combinations such as "SHF+d" as well, for example.

So everything seems to work, except LevelD.

3) Other comments you made:

a. As far as I'm concerned, TouchBuddy can and does issue key presses, but they apparently are ignored by LevelD.

b. So the big question you raised is, does FSUIPC even work with LevelD? Is there an easy way to determine this?

4) Options you suggested:

Option # 1 - One possibility you suggested, and I believe I have confirmed that FSUIPC sees the touch screen key presses, is to use the off-set method and internal FSUIPC controls to assign a virtual button. I'm willing to try this, but I'm not quite sure on how to set up? Are there any examples I can refer to that would be helpful?

Option #2 - Using your new feature (Mouse Macro) - I'll have to upgrade to the newest version as I believe I am currently running only 3.71. As in the above, an example would be helpful.

Regards,

Bill

[Pete Dowson]

First of all, in case I misunderstood one of your comments, TouchBuddy is a separate program effort from LevelD 767 development team and are not connected in any way.

I assumed so. I've heard of VoiceBuddy. Not sure what "touchbuddy" is for.

All I can say is that pressing the touch screen (via TouchBuddy SW) issues key press commands.

Ah, for a touch-sensitive screen? I see.

That could be, but I'm not as much of an expert as you would be about this. It seems to me reading a keyboard would be the same for all applications.

No, not at all. You can read the keyboard at key level, at Windows KEY message level, and at Windows CHAR message level. Also there's a Windows HotKey facility which can undermine most of the others.

I will say this, I can press the touch screen and can successfully send a key press to any of the following:

Yes, but i don't think that helps really. If the thing you want to send them to doesn't see them then it doesn't matter how many other things do, does it?

So everything seems to work, except LevelD.

So, maybe you should ask them to change their programming?

Option # 1 - One possibility you suggested, and I believe I have confirmed that FSUIPC sees the touch screen key presses, is to use the off-set method and internal FSUIPC controls to assign a virtual button. I'm willing to try this, but I'm not quite sure on how to set up? Are there any examples I can refer to that would be helpful?

No, because it is a facility for programmers, though it is also used in WideClinet -- in fact Wideclient implements a touch-screen button array, something I added specifically to support the two 7" touch screens I added to my cockpit.

As I said in my last message, if you want to proceed down this route I will explain. But before you start you should really check that FSUIPC's keypresses are recognised by the LevelD autopilot. If not you will be wasting your time. To do this without much trouble you need a joystick button to program. Try programming one to send your letter "A" for instance, see if it selects the left A/P.

Option #2 - Using your new feature (Mouse Macro) - I'll have to upgrade to the newest version as I believe I am currently running only 3.71. As in the above, an example would be helpful.

What? I shouldn't even be talking to you if you are using an unsupported version! What's the point of sticking to such old outdated and unsupported versions? I really don't understand why folks don't keep up to date -- especially when coming here requesting support. Please read the Announcements at the top of the Forum!

The documentation contains examples already.

Please use a supported version of FSUIPC before you come back.

Regards

Pete

[sbclark]

Pete,

Sorry, I apologize, and will update to the latest FSUIPC and WideFS........I was going to anyway before trying out any suggestions you would have made.....I know his is standard SOP everywhere if you want to get support.

Also, I'll checkout to see if LevelD accepts a Joystick input for one of the Autopilot features first. I'm using the Thrustmaster Cougar throttle/stick combo.

I'll get back to you later once I have accomplished these two items.....as well as reading your documentation further.

I know you are a busy, but if you find the time, it might be worth it to check out this software tool. For $100 to $300 for a touchscreen, plus the TouchBuddy SW, it provides a very inexpensive way to setup profiles for many sims, be they flight or racing. It is very easy to program and setup.

TouchBuddy Screen Shots - http://www.touch-buddy.com/ppost/showgaway=&cat=2

Appreciate your help,

Bill

[Pete Dowson]

I'll checkout to see if LevelD accepts a Joystick input for one of the Autopilot features first.

Well, joystick button programmed to send a keypress in FSUIPC.

I know you are a busy, but if you find the time, it might be worth it to check out this software tool. For $100 to $300 for a touchscreen, plus the TouchBuddy SW, it provides a very inexpensive way to setup profiles for many sims, be they flight or racing. It is very easy to program and setup.

The only touch screens I have are in my 737NG cockpit, used to select options for RC and other programs, things that don't "fit" in a "real cockpit". They are little 7" affairs screwed to the sides, below the side windows, handy for pilot or copilot. They are both connected to the same PC and do identical jobs. If you look in the WideFS documentation you will see the details of the facilities WideClient offers for them.

For all other cockpit operations I prefer the real switches. ;-)

Regards

Pete