TouchBuddy FC2 Export - Beta Testers Needed!

[Scrambler]

Originally Posted by Wild.Bill.Kelso

What version of TouchBuddy are you running? You should have 1.3.0.17. (This is really Rev18, but Zorlac just forgot to up the version number when he made it. That is what we have in our downloads section

Thats strange as my version says 1.3.0 [Rev 18]

[Wild.Bill.Kelso]

The Touchbuddy title bar or somewere in it's window might say that, but look at the file version number. Right-Click Touchbuddy.exe and select properties to see the actual file's version.

[MackTheKnight]

Originally Posted by Scrambler

lomac_data_file = C:\Games\Eagle Dynamics\LockOn Flaming Cliffs 2\touchbuddy-export.dat

Hi Guys,

Thank you both for your replies. Scrambler hit the nail on the head - after changing my touch-buddy cfg file to match the above, all is well.

Thanks so much for your help, guys!

btw, I'm running the current version rev 18 from the downloads section.

Regards,
Mack

[blaster454]

Originally Posted by Scrambler

Fired it up in Client/server mode with the laptop [using your LomacFC2-Exeter-WBC profile] and seems to work fine

Hi, Scrambler. I've been trying to set this up in client-server mode but can't seem to get it to update correctly. I'm assuming I have my pointers whacked! I wonder if you could share how you set up the config files?

[9JG54_Kirin]

Hey WBK

I've just now come by to test your updated export script and it works like a charm. Great work WBK.

[Scrambler]

Originally Posted by blaster454

Hi, Scrambler. I've been trying to set this up in client-server mode but can't seem to get it to update correctly. I'm assuming I have my pointers whacked! I wonder if you could share how you set up the config files?

Not certain where to start as I am no expert in this but have done it on two machines now and seemed to work OK.

Have you followed WKB's instructions for installing the TouchBuddy_FC2_Export.lua file and modified the export.lua file.

If you have done this FC2 should generate the touchbuddy-export.dat file in the LockOn Flaming Cliffs 2 root directory. It may be worth checking to see if this file has been generated after running FC2.

[I hope you have not installed FC in the Programe File (X86) folder ! - by all accounts it could be the source of some grief if you have]

If the touchbuddy-export.dat gets generated then you need to modify the cfg file to point to where it is, this is the line in my local.cfg file
lomac_data_file = C:\Games\Eagle Dynamics\LockOn Flaming Cliffs 2\touchbuddy-export.dat Yours may be slightly different, modify it to suit your actual install folder.

In client/server mode does anything actually work, i.e. normal button presses etc. If nothing is actually working then there may be problems with IP config, let us know and I could go through setting that up also.

It is worth making the status bar visible on the client m/c, you should be able to see it communicating with the sever, any error message may help to diagnose what is going wrong.

Below is a coply of my touchbuddy-local.cfg file. Your IP settings and lomac_data_file settings will probably be different.

Hope this ramble is of some help. I think someone needs to write a FAQ for this.

# TouchBuddy **LOCAL** Config file
#=====================
debug = 0
module_debug = 0
fdebug = 0
enable_threads = 0
lomac_data_file = C:\Games\Eagle Dynamics\LockOn Flaming Cliffs 2\touchbuddy-export.dat
#force_window_xpos = 10
#force_window_ypos = 10
#=====================
#Server stuff
#port to listen on when in "server" mode
listen_port = 12000
#The password used for the server
#(checked against the password the connecting clients use)
server_password =
#list of IP addresses allowed to connect as clients
#when in "Server" mode
allowed_ip = match:192.***.0.5 [Deleted]
allowed_ip = partial:192.***.0. [Deleted]
#=====================
#Client stuff
#IP address and port of the server to connect to
#when in "Client" mode
connect_ip = 192.****** [Deleted]
connect_port = 12000
#The password used by the client
#(Used when connecting to a server)
client_password =
#====================
mouse_position_after_press = previous

#======================
#=====================
# In Local mode, when you press on the TouchBuddy window, the mouse/cursor
# will move to the area of the button, but after pressing the button, the
# cursor will stay there. By defining the following value, TouchBuddy will
# move the mouse/cursor to the defined position after a button press.
# If its defined as "centre", the mouse/cursor will be moved to the centre
# of the currently active window.
# If its defined as "previous", the mouse-cursor will be moved to where
# TouchBuddy saw it last time round its 1 second timer loop (this option works
# remarkably well from my limited testing!)
#mouse_position_after_press = 320,240
# or
#mouse_position_after_press = centre
# or
#mouse_position_after_press = previous
#=====================

[blaster454]

Thanks. Scrambler! I have had the TB client-server running OK for some time. The problem appears to be with pointing to the export data file from the client. I'll just have to chase it down piece by piece ... or go nutso trying!

When run in C-S mode, I have most button press macros sending to FC2 OK but the data remains stale. The export data file is being written OK so it has to do with the way I am defining my network addressing. The IP path between the computers is running fine.

Bill (Snacko), I did set this up in local mode and tested with FC2 ... it seems to be running fine although there are a few button macros that may be incorrect for FC2 ... that will be easy to troubleshoot. Good job on the new export.lua file!

[Wild.Bill.Kelso]

Thanks. I just put that FC2 profile together quickly a few weeks after it came out. It was not tested or completed. But some users were asking for it, so I posted it for them. Still needs some tweaking, but works for the most part...