zorlac

so, its working now? The next major release will have less "new features"* and more "making it look nice and slick", with things like a preferences program to make all this stuff point-n-click. Also looking at other things to make TouchBuddy more user friendly, to give better and more detailed error reports. (* - There will still be new stuff, there are several things whizzing around my brain right now).

As Rugg has mentioned, this got fixed yesterday (how this one got missed I do not know!), so go download the latest version (v1.3.0 revision 12), and all should be working correctly.

maybe these guys like making things, doing something unusual, making/doing something that others in the community might be interested in seeing, just to see if it can be done, to see if it would lead to others having ideas or tips that could help, maybe they didnt want to waste a whole load of money of vastly expensive cockpit setups, maybe they just wanted to add specific pieces of kit that they thought mightbe useful/helpful for them when they fly.... or maybe they just shouldnt have bothered :thumbup:

new version going up as we speak that allows you to define the priority that TouchBuddy will run at. TouchBuddy is always fighting for a slice of processor time, and its fighting a program (the game) that never sleeps and is always trying to run on the CPU. If TouchBuddy does not get that CPU time often enough, it will appear "sluggish". Hopefully with the above option, you can fine tune this problem. Running it at "high" will give TouchBuddy some CPU time, but at the expense of CPU time for the game. I would try "above_normal" if you are running in local mode. Give it 10 minutes or so and the full and core builds will be uploaded and available.

here goes: For "local" mode only: - copy the touchbuddy-export.lua file from the touchbuddy\lua folder into the "C:\Program Files\Ubisoft\Eagle Dynamics\Lock On\Config\export\" directory - open the file "C:\Program Files\Ubisoft\Eagle Dynamics\Lock On\Config\export\export.lua" in a text editor, scroll RIGHT down to the VERY bottom and add the line: dofile("./Config/export/touchbuddy-export.lua") - As someone else has pointed out to me, you may also want to open the file "C:\Program Files\Ubisoft\Eagle Dynamics\Lock On\Config\export\config.lua" and ensure that the "EnableExportScript = true" - open the touchbuddy.cfg file in a text editor, and change: lomac_data_file = .\touchbuddy-export.dat to read lomac_data_file = C:\Program Files\Ubisoft\Eagle Dynamics\Lock On\touchbuddy-export.dat For client/server, you need to do the above on the "server"... i.e the PC running the game, and the TB client will request the info from the TB server. That should do it. Obviously, if you lockon is installed somewhere other than in the default location on C: then you will have to make allowances for that when reading the above instructions

i`m not aware of any limitation on window size (I certainly dont impose one anywhere)... ah.... just found out that the Toolkit imposes this limitation (3200 is fine, 3201 and a warning messages pops up). I`ll mention this to WBK (if he doesnt spot this first) The first 6 weeks of TocuhBuddy development was done without a touchscreen. I knew the idea should work, but if I was handing out a lot of money for a touchscreen, I needed to be absoluetly sure my idea would work. The first time I hooked up the touchscreen, started lomac, and pressed a button on the touchscreen was quite magical to me.... i couldnt quite get over the fact that (a) it worked and (b) the WOW factor.... you have no idea how long I spent on the runway, opening and closing my canopy :) press.... whirrr....woohoo!... press... whirr... woohoo!... press... whirr... woohooo (repeat over and over again). There was a HUGE grin on my face for hours after that.

New v1.3.0 revision 11 builds up and online: http://www.touch-buddy.com/forums/local_links.php?catid=1 Cheetah - thanks for heading me in the right direction for finding the bug, its greatly appreciated.

lockon folder\Temp\Error.log

OK, what does humble pie look like? anyone know the recipe? :eek: :confused: :( Even though I have disabled debug, its turning itself back on again, so yes, its spitting out shedloads of text to disk. New build on its way shortly, once I can convince my code to behave

if debug is disabled (i.e. debug = 0) in both touchbuddy.cfg *AND* touchbuddy-local.cfg, then the debug-<HOSTNAME>.txt file should only be written to at startup to show some basic info. After that, it should not be written to during run time. I am just double checking this right now on a "clean" machine. With debug disabled, the debug text file should only be 10-20 lines long. If its being written to during program run, then either debug si still enabled, or my code is screwey :)

ah yes, i never did get around to posting my TEWS FAQ. Read the first few lines of the "touchbuddy-export.lua" file, which explains how to get it working: Right now, I have two users that have some very strange "slowness" when TB is running, taking several minutes to load a profile, and several second delays between pressing the screen and the macros being sent. I have no idea so far as to what is causing it, I cannot recreate the problem on any of my machines, and the two users in question are nowhere near me so I cant even pop over and take a look myself. Its frustrating to say the least, but I will be spending a LOT of time looking at my code, and talking to the two affected users in an attempt to work out wtf is going on and how I can fix it.

I OH so know what you are talking about here :thumbup:

Hi all After rather a bit longer than we had imagined, and also with more features added than we had planned, here is the release of TouchBuddy v1.3.0. This time round, we are making two different downloads available. The smaller file is the "core" build, and contains the core TouchBuddy application, plus the supporting DLLs, and the demo-profile (and images). The larger file is the "full" build, and contains everything in the "core" build, but has some of the better user supplied profiles bundled in with it. As the release notes are now just so vastly huge, I wont be posting them in here, but I will quickly go over some of the new features: Button Tooltips A sent "macro list" available on the *TB* tab Button visual "Feedback" (optional) Remembers the last mode and profile used No more "lost" events when multiple buttions are pressed quickly Lomac Active Modules (TEWS, Payload, MCP) Active "click-through" Module Selective Transparency on a per tab basis * Selective Translucency on a per tab basis * Hold "expiry" times "Iconify" TouchBuddy to display the window contents behind it New "clone" button type Keyboard shortcuts to bring up the *TB* window or Iconfify it Progress bar during profile loading Ability to use multi-frame GIFs (with ImageMagick) * sending macros when entering/leaving tabs "invisible" tabs And much more... (* - Transparency/Translucency and ImageMagick animated GIFs only supported on Windows 2000 and higher) For the full list of what was added/fixed/broken/fixed-again, please take a look through the RELEASE_NOTES.txt file. You can find both the core and the full downloads in **HERE** WBK will be along shortly and will post the link to the new and improved Toolkit that supports the new features in TouchBuddy v1.3.0 Enjoy! (I`ll post a couple of "how-to" messages soon, to explain how to get the Lomac TEWS working, and also a more in depth look at the active "click-through" module, how it works, what it can (and cant do), etc....)

I get the same problem... while paused, VP shows "connected", but as soon as I hit S to unpause, it says disconnected. the error.log file shows this: LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed

because TouchBuddy is so flexible with it layout, and so "powerful" with the options available, making the Toolkit do everything it does has been an astonishing feat by WBK. OK, it does take a little getting used to the basics (because it is so powerful/flexible), but once that has been done, the toolkit is a joy to use. if you have questions, just ask... thats what we are here for.

the magictouch screens are placed on the front of the screens, the touchpanel i have requires that the front bezel on my TFT was removed, the touchpanel stuck to the front of the TFT panel, then the bezel placed over the top again. It *ALMOST* fits properly :) Yes, it has a ribbon cable out the side that fits into an adapter, which in turn provides a USB connection. The auctions for these work out a lot cheaper than the magic touch panels

I have one of these on my secondary 19" screen: http://cgi.ebay.co.uk/TouchScreen-Touch-Screen-Panel-Kit-for-19-Display-POS_W0QQitemZ150079625857QQihZ005QQcategoryZ174QQrdZ1QQcmdZViewItem I also have a 17" touchpanel unit lying around, waiting for me to find a cheap 17" screen to fit it to.

sadly lomac doesnt export enough data to provide me with the correct info for a a VSD :(

do you mean the in-cockpit TVs on the MFDs? Then probably not....

http://forum.lockon.ru/showthread.php?t=20665

will be looking at it right after v1.3 release... honest :)

Use LockOn Track Util, available at all good lockon file sites :)

I cant wait.... am very intersted in try this.

wow! OK, I`m impressed... I think its time to find an old x45 on ebay :)

oooo! I can see what I`ll be playing with tomorrow... thank you!