Touchbuddy and Tacview

S77th-ReOrdain · 01-18-2007, 02:49 PM

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".

Dodger · 01-19-2007, 01:51 AM

Hey ReO... thanks for the info. How are you these days? Long time no speak. Did the S77th get the squad campaigns up and alive again? Miss those days.

S77th-ReOrdain · 01-19-2007, 06:09 PM

Howdy Dodger.
Good to here from you Bro! Yeah, we're still campaigning at the S77th. We've got a whole new format with reporters, fictitious generals, insurgents and more. We've even got an interactive .htm that gives situational info in key areas and hotspots. We're continuing to strive to do things to keep Lock On fun and alive for dedicated simheads (kinda like you guys).

zorlac · 01-19-2007, 08:02 PM

Quote:

Originally Posted by S77th-ReOrdain

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")

weird... will look at this (this is the order mine have always been in, so I may not see this problem happenning)

Quote:

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.

weird... I will check to see if Lomac is still exporting the damage info, or if TouchBuddy is having flashbacks

S77th-ReOrdain · 01-19-2007, 11:01 PM

Hey Zorlac,

Yes, initially I had problems setting up the active plugins until I realized how to point touchbuddy.cfg to the proper locations. My initital setup was done with (build 9), and I may be incorrect, but for whatever reason I didn't find the lua folder with touchbuddy-export.lua in it.

My mistake for not reading the entire touchbuddy.cfg file at that time, but after doing so, I followed the instructions literally as are also posted in the FAQ active plug-in setup here:

http://touch-buddy.com/forums/showthread.php?t=632

which states that you should scroll down to the bottom and add the "dofile" line. To top that off, I was pointing the touchbuddy-export.dat file to the one contained in the touchbuddy folder (intended for the demo) until I realized there was one that was generated after opening touchbuddy (in the main Lock On directory).

Long story shortened, I was thrilled once I got everything working properly, but hadn't checked Tacview to see if it was generating files. When I finally did, after build 12 and your helpful instructions, I noticed the problem. The line switcheroo corrected this, so all is well. Didn't want to make a big deal of it, but I wanted others to be aware of how to solve it if they've experienced the same.

01-18-2007, 02:49 PM	#1 (permalink)
S77th-ReOrdain Addict Join Date: Jun 2006 Posts: 11	Touchbuddy and Tacview 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". Last edited by S77th-ReOrdain : 01-18-2007 at 02:53 PM. Reason: didn't include version

01-19-2007, 01:51 AM	#2 (permalink)
Dodger Admin Join Date: May 2006 Posts: 338	Hey ReO... thanks for the info. How are you these days? Long time no speak. Did the S77th get the squad campaigns up and alive again? Miss those days. __________________ Simulator Realism with Touch-Buddy

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

01-19-2007, 06:09 PM	#3 (permalink)
S77th-ReOrdain Addict Join Date: Jun 2006 Posts: 11	Howdy Dodger. Good to here from you Bro! Yeah, we're still campaigning at the S77th. We've got a whole new format with reporters, fictitious generals, insurgents and more. We've even got an interactive .htm that gives situational info in key areas and hotspots. We're continuing to strive to do things to keep Lock On fun and alive for dedicated simheads (kinda like you guys).

01-19-2007, 11:01 PM	#5 (permalink)
S77th-ReOrdain Addict Join Date: Jun 2006 Posts: 11	Hey Zorlac, Yes, initially I had problems setting up the active plugins until I realized how to point touchbuddy.cfg to the proper locations. My initital setup was done with (build 9), and I may be incorrect, but for whatever reason I didn't find the lua folder with touchbuddy-export.lua in it. My mistake for not reading the entire touchbuddy.cfg file at that time, but after doing so, I followed the instructions literally as are also posted in the FAQ active plug-in setup here: http://touch-buddy.com/forums/showthread.php?t=632 which states that you should scroll down to the bottom and add the "dofile" line. To top that off, I was pointing the touchbuddy-export.dat file to the one contained in the touchbuddy folder (intended for the demo) until I realized there was one that was generated after opening touchbuddy (in the main Lock On directory). Long story shortened, I was thrilled once I got everything working properly, but hadn't checked Tacview to see if it was generating files. When I finally did, after build 12 and your helpful instructions, I noticed the problem. The line switcheroo corrected this, so all is well. Didn't want to make a big deal of it, but I wanted others to be aware of how to solve it if they've experienced the same.