TouchBuddy Supported Game List
The following list shows games that have been tested with TouchBuddy, whether they work or not, and explains any problems discovered during the test. Games marked as "*TB-Team Tested*" have been tested by a member for the TouchBuddy test team. This is by no means a complete list of games. If a game is not listed on here, it does not mean it will not work. It also does not mean it will work. It just means it has not been tested yet :)
If you are using TouchBuddy with a game not listed here, please let me (Zorlac) know on the Touch-Buddy.com forums, and report as much as you can about your experiences (local or client/server, "SetCapture" or "ClipCursor" issues, etc)
(This list will be updated as often as I can find time)
Quick Note: Although TouchBuddy supports FPS type games, its does not really suit them well. Its something about FPS games requiring you to not look at the keys to press, and being able to "feel" the edges of the buttons just by putting your fingers on them, and that is feedback that a touchscreen just cannot provide the user with. Also, when pressing a locally attached touch screen (i.e running TouchBuddy in "local" mode), the game "sees" the mouse cursor move to the touch screen and moves the player's orientation. It also see the "touch" as a left mouse click, and starts firing your currently selected weapon. I think this will affect most/all FPS type games unless you run TouchBuddy in Client/Server mode.
|
Game |
Local Mode | Client/Server Mode |
|
Lockon (Note: TouchBuddy was started, coded and tested on Lomac initially) |
Supported:
YES Issues: NONE, other than any external views "panning" when touching the touch screen (mouse move is the default setting for external view movement, you may need to unmap this in the game controls). |
Supported:
YES |
| Lockon: Black Shark (Beta) | Supported:
YES Issues: I think it is working the same way as the Lockon entry above, but as the product is still in beta, the testers are not giving much away :) |
Supported:
YES |
| iL2 (And Pacific Fighters, and Ace Expansion Pack) *TB-Team Tested* |
Supported: YES (Many thanks to Retrofish on the Ubi.com forums for showing us this fix) |
Supported: YES |
| iL2
1946 *TB-Team Tested* |
Supported: YES |
Supported: YES |
| Falcon
4 : Allied Forces *TB-Team Tested* |
Supported: YES |
Supported: YES |
| Falcon 4 (Original) | Suported:
NO Looks like "SetCapture" issues, but this hasn't been tested by any TB team members. |
Supported: Untested as yet |
| Enemy Engaged: EEAH / EECH *TB-Team Tested* |
Supported:
YES ("ClipCursor" can be overridden) Issues: Can cause some weird behaviour, having two cursors on screen (one in game, one on the real windows background). |
Supported:
YES |
| Janes F/A-18 *TB-Team Tested* |
Supported:
YES ("ClipCursor" can be overridden) |
Supported: YES |
| Microsoft
Flight Simulator 200x *TB-Team Tested* |
Supported: YES | Supported: YES |
| Microsoft
Flight Simulator X (10) *TB-Team Tested* |
Supported:
NO (kind
of) When in Full Screen Mode, MS FS-X blanks out the second display for some reason, and as yet, we have no idea why, or how to disable this "feature". It works fine if you use windowed mode (ALT + ENTER) |
Supported: YES |
| rFactor | Supported: YES | Supported: YES |
| Ghost Recon Advanced Warfighter | Supported: Untested as yet | Supported: YES |
| Battlefield2 (and exp. packs) | Supported: Untested as yet | Supported: YES |
| Silent Hunter III | Supported: Untested as yet | Supported: YES |
| EA FIFA Football (Soccer) | Supported: Untested as yet | Supported: YES |
| SteelBeasts
Pro PE *TB-Team Tested* |
Supported:
YES ("ClipCursor" can be overridden) |
Supported: YES |
| Strike
Fighters (P1 or Gold) Wings Over Europe Wings over Vietnam |
Supported:
NO Looks like "SetCapture" issues, but this hasn't been tested by any TB team members. Unlike the problem with iL2, there does not appear to be any config file entry to bypass this problem. |
Supported: Untested as yet |
|
Operation Flashpoint |
Supported:
NO (kind
of) When pressing a locally attached touch screen, the game "sees" the mouse cursor move to the touch screen and moves the player's orientation. It also see the "touch" as a left mouse click, and start firing your currently selected weapon. I think this will affect most/all FPS type games :( |
Supported: YES |
|
GTL/GTR/GTR2 |
Supported: YES | Supported: YES |
| Armed Assault | Supported:
NO (kind
of) When pressing a locally attached touch screen, the game "sees" the mouse cursor move to the touch screen and moves the player's orientation. It also see the "touch" as a left mouse click, and start firing your currently selected weapon. I think this will affect most/all FPS type games :( |
Supported: YES |
| X3: Reunion | Supported:
NO In both full screen and windowed mode, the game prevents the mouse cursor from leaving the game area, preventing the cursor from moving over to any locally attached touch screen. Unlike the problem with iL2, there does not appear to be any config file entry to bypass this problem. |
Supported: YES |
Notes:
"SetCapture" - This issue affects games where the developers have prevented the mouse/cursor from leaving the game window area (Using SetCapture). This can cause an issue if you are running TouchBuddy in Local mode (i.e. attached as a second screen to the PC you will be running the game on). When you press on the touchscreen, the drivers for the screen will try to move the mouse cursor across to that position so that you can click on a button or area, but if the mouse is locked to the game window area, then the mouse cursor can never get there. This means that a game that uses this "SetCapture" cannot be used with TouchBuddy in Local mode :(
"ClipCursor" - Some games use another method to "trap" the mouse inside the game window area, and its called "ClipCursor". This behaviour disabled by TouchBuddy to allow the mouse cursor outside the game window area, but can sometimes have some odd side effects if you do so.