Touch-Buddy v2.0

[Dodger]

Greetings Touch-Buddy fans.

It has been a while since we've released a new version of Touch-Buddy. As you may know, the current code-base can not support further features / enhancements.

So we are looking to put together a list of features that you would like to see added. We will compile a list and then put a case together for building Touch-Buddy version 2.0.

Regards,

Dodger (TB Team Admin)

[Corsair8X]

That's really amazing news. I know that it will be a major undertaking. Good luck to you all.

A strange feature that I would really like to see (but I'm not even sure if it's possible) is to have some communication going the other way - to the TB. My reason for this because I forsee myself having as close to the real-thing as possible as far as layout goes (just like an amazing F-16 layout that got released just a short time ago - truly outstanding work). I know there are tabs for switching to the different panels, but I would really like to see something where I could hit a button on my hotas to scroll through the different tabs or even have one button associated with each tab (of course what I'm really talking about is some type of key-stroke - say, CNT SHT ALT s). This way the panel would be ready for me to interact when my hand got there. I suppose if each individual tab had a keystroke you could even use voice comms to activate it too.

Kind of a strange request I'm sure, but it may keep down the need for multiple touch-screens which I don't think is feasable for me right now.

[Bill Clark]

This is good news:

I would like to see TouchBuddy work better with FS9 and FSX. Currently, TB works with all the default aircraft, but doesn't with LevelD 767 add-on. In this case, when the LevelD 767 remaps some of the key presses when loaded and running, it will take input from the keyboard, but not TB. I've tried it in both local and client/server modes, and it doesn't work.

Also, it would be great if TB could receive inputs from the application. In the case of FS9 and FSX, you could use Peter Dowson's FSUIPC or MS Simconnect tools as the input vehicle.

Also, fix known existing bugs.

I may have other suggestions later.............

Bill

Bill

[Hipshot]

[/IMG]

[CajunRon]

Here's a few thoughts

1. Rotary switch with multiple positions, each position programmable

2. Sliding switch that multiple "detent" positions (for example to simulate notch positions of railroad locomotive throttle)

[Dodger]

Originally Posted by CajunRon

Here's a few thoughts

1. Rotary switch with multiple positions, each position programmable

2. Sliding switch that multiple "detent" positions (for example to simulate notch positions of railroad locomotive throttle)

Thanks Cajun. Sounds like a profile requirement. You are looking for ability to animate a sliding switch for a particular profile?

Originally Posted by Bill Clark

This is good news:

I would like to see TouchBuddy work better with FS9 and FSX. Currently, TB works with all the default aircraft, but doesn't with LevelD 767 add-on. In this case, when the LevelD 767 remaps some of the key presses when loaded and running, it will take input from the keyboard, but not TB. I've tried it in both local and client/server modes, and it doesn't work.

Also, it would be great if TB could receive inputs from the application. In the case of FS9 and FSX, you could use Peter Dowson's FSUIPC or MS Simconnect tools as the input vehicle.

Also, fix known existing bugs.

I may have other suggestions later.............

Bill

Bill

Thanks Bill. Another request for the capability to input data to TB.

Originally Posted by Corsair8X

That's really amazing news. I know that it will be a major undertaking. Good luck to you all.

A strange feature that I would really like to see (but I'm not even sure if it's possible) is to have some communication going the other way - to the TB. My reason for this because I forsee myself having as close to the real-thing as possible as far as layout goes (just like an amazing F-16 layout that got released just a short time ago - truly outstanding work). I know there are tabs for switching to the different panels, but I would really like to see something where I could hit a button on my hotas to scroll through the different tabs or even have one button associated with each tab (of course what I'm really talking about is some type of key-stroke - say, CNT SHT ALT s). This way the panel would be ready for me to interact when my hand got there. I suppose if each individual tab had a keystroke you could even use voice comms to activate it too.

Kind of a strange request I'm sure, but it may keep down the need for multiple touch-screens which I don't think is feasable for me right now.

Thanks Corsair. This shouldn't be too hard to implement.

[Corsair8X]

I'm really excited that you said it was possible. I think it would help reduce the need for having multiple touch screens (not that there is anything wrong with that). If each tab that was created could have a sepparate keystroke assigned to it then I think it would be awesome to say "ICP" and have it go there just as your hand is getting there. I think it would save just those fractions of a second that may make all the difference.

Other people have some really great ideas too. As Bill Clark has menioned, getting input from things would be cool. Black Shark may allow export of data and so that would make for a pretty awesome ABRIS that you could also interact with.

[Mag_maverick]

Having the ability to associate a sound file with a button would be a nice feature, i.e. sound of a switch being engaged/disengaged. Currently, our only option is to rely on the weak, unrealistic sounds from the touchscreen. I believe Zorlac had previously added this to his "to do" list.

Thanks,

[Tankbuster]

Originally Posted by Mag_maverick

Having the ability to associate a sound file with a button would be a nice feature, i.e. sound of a switch being engaged/disengaged.

Thanks,

Seconded....

[Corsair8X]

Again, I may be asking for the impossible. It sounds like you may be reconsidering several factors as to how TB is built and opperates as well. I would like to touch on the subject of multiple monitors. I know that currently TB supports multiple screens through a client/server type of arrangement. I often wonder if that type of complexity is a turn off for some people. I say that because it is something of a turn-off for me. I know that because of this, I would have to have a setup that would only contain one touchscreen which is the reason for my first request.

What I'm about to ask is based on my lack of knowledge about PCs in general, and in particular how video cards work. So what I'm asking for is possible not possible due to hardware limitations and has nothing to do with TB and if so I apologise in advance. Is it possible from the ground up for TB to deal with multiple touch screens, but in the local mode? It may be a significant change - but I think that it would really allow for some awesome cockpit setups for a minimum of hardware requirements (and the looking after of said hardware). I know there are usb video outputs now that allow for a signal to be transferred to a monitor without the need of extra video cards. Because I don't think TB really involves complex animations like games do, perhaps TB can output these graphics, act as a traffic-cop for the signals to different monitors, and then the usb video output would take care of the signal processing. Perhaps then on TB client could utilize a number of monitors (2, 3, more?) and the processor overhead would not be significat to make that impossible?

Again, what I ask for may not be possible, but I think it may make the more complex multi-touchscreen cockpits that are so attractive that much more accessible. It may assist in converting more people to adopt TB as their cockpit manipulation of choice.