Teamspeak Module Support In Client Mode?

[44th_eightFive]

Hey everyone, long time no see .

I'm finally getting back to Lock On and of course I'm putting my Lilliput and TouchBuddy to good use. Everything is working superbly aside from this one minor quirk with the Teamspeak module.

Let me flesh out my setup details first:
- PC1 runs Lock On and TB in server mode.
- PC2 runs Teamspeak and TB in client mode.

I have Teamspeak running on PC2 in order to have voice comms separately through my headset without having to enable PC1's CPU cycle eating on-board sound card.

The problem I am having is that the TS module in TouchBuddy is not working correctly in client mode. The module loads, but remains in its default state. If I load the same profile in local mode, however, the TS module comes alive with all the appropriate data.

I did notice this in "touchbuddy.cfg" while trying to diagnose the problem:

# if you are planning to use the TeamSpeak module, then you will
# need to set this path to point at the "tscontrol.exe" program
# on the PC running TouchBuddy in Local or Srever mode (It isnt
# used in Client mode at all). If you are using the TeamSpeak
# module, and you havent set this option, the TeamSpeak module
# will fail horribly

Does this mean that client mode and the TS.....



I figured it out... just needed to point the touchbuddy.cfg tscontrol.exe path to its location on the shared drive on PC2... crisis averted, and, TouchBuddy is now perfect .

Well sorry for the long self-answered post. I figured I'd still post just in case someone else runs into the same trouble and well, just to say hello again!

[44th_eightFive]

Looks like I jumped the gun... now the TS module shows the server I'm connected too, however the status bar at the top reads "No TeamSpeak Client Running" "Users:0/0", and the channels appear empty. Any ideas?

[Dodger]

Hey 8five, thats probably one for Wild.Bill, Ruggbutt or Zorlac, as I've always run in local mode.