Lomac Active modules trouble

[Lopez]

Hi, I'm a new user of touch buddy with my touchscreen.

this is my touchbuddy.cfg

(posted on next post)

and i have put in my export lockon directory the touchbuddy-export.lua


and inside export.lua dofile("./Config/export/touchbuddy-export.lua")


and in config.lua export is true.

and always i have the same result of tews and payload






always the same image and the same information

Can anybody help me please

[Lopez]

# TouchBuddy Config file
[....]# audio feedback
# if audio_feedback is set (1) then every button press
# will create a short beep. (Server and Local mode only)
audio_feedback = 0

#=====================
# 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 :)
#
# *FULL* path to tscontrol.exe
tspath = C:\Archivos de programa\Teamspeak2_RC2\client_sdk\tsControl.exe

#number of seconds between "normal" teamspeak tab refresh/updates
ts_refresh = 60

#=====================
#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 = **change_this!**

#list of IP addresses allowed to connect as clients
#when in "Server" mode
allowed_ip = match:127.0.0.1
allowed_ip = partial:172.16.254.

#=====================
#Client stuff
#IP address and port of the server to connect to
#when in "Client" mode
connect_ip = 172.16.254.12
#connect_ip = 127.0.0.1
connect_port = 12000

#The password used by the client
#(Used when connecting to a server)
client_password = **change_this!**

#=====================

# Processor Affinity
# You can use this option to tell TouchBuddy
# to only run on a single specific CPU or Core.
# CPU numbers start 1 and work ther way up.
# If you have a dual core or dual CPU machine,
# then you can choose to run TouchBuddy on 
# CPU/Core 1 or 2. To let TouchBuddy run on any
# CPU, comment this line out.
# If you specify a CPU/Core that isnt valid for
# your hardware, and alert will be displayed.
#
# NOTE: THIS DOESNT CURRENTLY WORK! And will
# be ignored totally :)
run_on_cpu = 2

# Set the process priority of TouchBuddy. This option can be set to:
#	below_normal
#	normal
#	above_normal
#	high
# (I *REALLY* do not recommend using the "below_normal" option in Local mode)
cpu_priority = normal

#=====================

# enable/disable profile scaling.
# This enables TouchBuddy to scale all the buttons, images and 
# screen positions at initial load time, so that they fit on a 
# screen of any size (within reason!). If you enable this option, 
# set the native size of your screen below in "screen_resolution".
# NOTE: The scaling only happens once, when you load the profile.
# It will not scale the profile if you resize the window with 
# after you have loaded the profile.
profile_scaling = 0

# set the *NATIVE* screen resolution of your screen here
# (Width, Height)
screen_resolution = 800,600

# Tells TouchBuddy to not "squash" the profiles if you have
# profile_scaling enabled
preserve_aspect_ratio = 1

#=====================

# The initial value of whether or not to display button borders when 
# TouchBuddy is displaying a skinned tab (Has no effect when displaying 
# the old style "normal" buttons). This can be toggled on/off from
# within TouchBuddy by using the "Toggle Button Borders" button on
# the *TB* tab
display_button_borders = 0

# This defines the color to use for the borders when display_button_borders
# is enabled. Color is defined as R,G,B (0-255 for each)
default_border_color = 255,0,0

#=====================
# Some games prevent the mouse cursor from leaving the game window area.
# Enabling this option allows TouchBuddy to try to release the cursor
# (Note: This option does not work on all games!)
clip_cursor = 1

# this is another way to try to unlock the game mouse, but it does cause a
# LOT of problems. I highly recommend you do not use this unless you
# absolutely have to!!
release_capture = 0

#=====================
# 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

#=====================
#enable/disable the memory check routine
memory_check = 1

#=====================
# Finally, I get around to doing this :)
# TouchBuddy will now remember the last mode (Client/Server/Local) and 
# the profile you selected, and will use those parameters when it starts 
# up again next time. Disable option if you dont want this behaviour.
remember_config = 1

# define the default startup mode you want TouchBuddy to start with
startup_mode = local
#startup_mode = client
#startup_mode = server

# define the default startup profile you want TouchBuddy to start with
#default_profile = C:\Program Files\TouchBuddy\profiles\something.tbc

#=====================
# force the display of the tab strip 
# (helps when a badly written profile leaves you "stuck" on a tab with
# no means of selecting another tab)
force_display_tabstrip = 0

# force display of status bar if the required
force_display_statusbar = 0

#=====================
# enabling this option will momentarily show a border around the button  after 
# being pressed to provide some visual feedback that the button has actually
# been pressed
feedback_flash = 0

#=====================
# This option enables/disables the display of button "tips" when moving the mouse
# over a button. Note: will probably cause a large CPU load compared to running 
# with it disabled.
display_button_tips = 0
# This option defines how long (in seconds) to show button "tip" if the mouse is stationary, or
# if the mouse remains inside the same button area. Default is 5 seconds.
button_tips_timeout = 5

#=====================
# Animation update rate
# On tabs that have multiple image buttons or tabs (i.e animation), this value determines
# how often window updates happen. The value is in number on 0.1 seconds to wait between
# updates. A vaue of 10 will give you 0.1 x 10 seconds delay (or 1 second).
# WARNING: Decreasing this value increases the CPU time that TouchBuddy will use. Ideally
# anim_update and active_plugin_update (below) should be the same value, but they dont have to be.
anim_update = 10

#=====================
# Active "plugins"
#
# Active Plugin update rate
# On tabs that have active plugins (The Lomac TEWs for example), this value determines
# how often window updates happen. The value is in number on 0.1 seconds to wait between
# updates. A vaue of 10 will give you 0.1 x 10 seconds delay (or 1 second).
# WARNING: Decreasing this value increases the CPU time that TouchBuddy will use. Ideally
# anim_update (above) and active_plugin_update should be the same value, but they dont have to be.
active_plugin_update = 10

# filename of the data file exported by Lomac
# NOTE: THIS ENTRY IS JUST A DEMO ENTRY!!! Remove this and enable the entry below
#that is commented out!!!
lomac_data_file = .\touchbuddy-export.dat

#this is the REAL location of the data file, the above line is just to demo
#the active Lomac TEWS plugin.
lomac_data_file = C:\Documents and Settings\Administrador\Escritorio\touchbuddy\touchbuddy-export.dat

#
# Active Lomac TEWS
# enable this option to allow the Active TEWS display to show all the "extras" available
# If you have any moral reasons for classing this as cheating, and want the TESWS to act
# fairly close to how it does in game, just set this value to 0
active_lomac_tews_extras = 1

#where appropriate, use metric or imperial measurmeents in the active plugins
use_dimensions = metric
#use_dimensions = imperial

#====================

# Hotkey definitions
#
# Enable/disable creation and use of hotkeys (set this to 0 if you dont want them to do anything)
enable_hotkeys = 1
# These hotkey definituons are the single character to be pressed in combination with
# SHIFT +ALT + CTRL (all at the same time, plus the key in the config entries below).
# Please refer to the predef and rawkey reference HTML file (in the docs directory)
# to obtain the correct "VK_" code of the keys your require.
#
# hotkey_tb_tab will show the window, and select the *TB* tab
hotkey_tb_tab = VK_T
#
# hotkey_iconify will allow you to toggle between the iconified and normal state of
# the Touch window
hotkey_iconify = VK_I
#
#====================
#
# Client Keyboard passthrough
# Another "Moon on a stick" request from SytRep :)
# If you enable the following option, then when running TouchBuddy in "Client" mode,
# it will try its very hardest to pass on any keyboard presses on the "Client" to the 
# TouchBuddy "Server" instance. This (I think) was to allow other gamepads and
# controllers on the "Client" to be used to control the game on the "Server".
# Actually, I think this is a very cool idea.
# NOTE: This only works in Client/Server mode... it is totally ignored in "Local" mode
enable_client_keyboard = 0
#
#====================
# Enable/Disable the use of the "Iconfift" window (set to 0 to disable)
enable_icon_window = 1
#
# Enable/Disable the ability to use Transparency/Transluceny on tabs (set to 0 to disable)
enable_transparent_tabs = 1
#
#set this value to configure how many days between online web check for new TouchBuddy updates
check_update_days = 3

[Wild.Bill.Kelso]

Hi Lopez, Welcome to the forums...

In your TouchBuddy.cfg file look at this section near the bottom:

:
:
:
# filename of the data file exported by Lomac
# NOTE: THIS ENTRY IS JUST A DEMO ENTRY!!! Remove this and enable the entry below
#that is commented out!!!
# lomac_data_file = .\touchbuddy-export.dat

#this is the REAL location of the data file, the above line is just to demo
#the active Lomac TEWS plugin.
lomac_data_file = C:\Documents and Settings\Administrador\Escritorio\touchbuddy\touch buddy-export.dat
:
:
:

Just comment out that first lomac_data_file line with a # as the first character in the line. Then post back and let us know if that fixed it.

WBK