I've experienced one small issue that that was easily corrected when using Touchbuddy in conjunction with Tacview. Be aware that this has only been confirmed on my system (using v1.0.3 build 13).
The suggestion when setting up touchbuddy is to copy the dofile to the bottom of the "export.lua" file. When putting the touchbuddy dofile last, I found that Tacview would no longer process the "tacview.acmi.txt" file. Don't no if anyone else has experienced this or not. I run a client/server setup.
To correct the problem, put the tacview dofile last at the bottom of export.lua. Like this:
dofile("./config/export/touchbuddy-export.lua")
dofile("./config/export/tacview.lua")
The results - Both programs are
Another small issue on my system involves the MCP plugin. When receiving damage to a plane that involves the autopilot, The system display will retain an autopilot failure once a new mission is loaded and the MCP display is reset. To correct this I've found it necessary to close touchbuddy (both client and server programs) in order for the failure to go away. Nothing major and obviously only confirmed on my sytem, but something I wanted to make people aware of.
Touchbuddy - "Oh, how wonderful".