zorlac

TouchBuddy v1.0.1 Stable Release Available here: http://www.touch-buddy.com/forums/local_links.php?catid=1&page=1 or here: http://www.syn-ack.com/touchbuddy/releases/touchbuddy-1.0.1-20060712.zip Some big additions here (predef macros, profile scaling, "touch" button types), so have a good read of the release notes. As usual, the simple-layout.tbc file uses as many of the available features. A quick word about profile scaling. Previusly, if someone created a profile for a 800x600 screen, and another user loaded in on their 640x480 screen, the profile and buttons wouldnt fit, unless they ran their screen at the non-native resolution (800x600). Profile scaling fixes this at load time by scaling the profile to fit, using the size of the window in the profile as the "original" size, and scales it down to the size of your own screen. There is an option flag to prevent the profile from being squashed during load (for wide-screen users) Example 800x600 profile Scaled on load to 640x480 Widescreen (ignore aspect) Widescreen (Preserve aspect) Wild Bill Kelso will be along shortly with download details of the stable TouchBuddy Toolkit v1.0.1.

(If I could it easily + quickly, I would... honest!)

its shouldnt make any difference... so long as the data comes out :)

TouchBuddy is written on a win32 system, and runs on a win32 system.... there are no native ports for anything other than x86 CPU machines running windows. No IPaq, Arm, PalmOS, TI Calculators, Abacus, etc... just x86 Windows based systems. I do not have any of these other systems lying around to play with, and am not sure I could port them over anyway because of a lot of very specific win32 code. About WINE (http://www.winehq.com)

you REALLY dont want to be exporting before/after every frame.... thats a heavy workload, so stick with your code that uses the event timer function LuaExportActivityNextEvent(t) local tNext = t -- Put your event code here and increase tNext for the next event -- so this function will be called automatically at your custom -- model times. # do some stuff here tNext = tNext + <number-of-seconds-until-next-update> return tNext end

I didnt go (was unable to), so post away :)

Duxford isnt that far from me (10-15 miles I guess), and I regularly see/hear some awesome airframes flying over our house, especially over a bank holiday weekend.

I know that LoGetWorldObjects() is totally disabled (usually) and enforced by the server, but is LoGetObjectById() totally disabled locally, even if you only want to obtain your own aircraft's information?

link to the Bullseye software download appears to be non-responsive.... anyone got an updated link?

You will be invoiced for the beer when you leave ;-)

scrolling? digital? pah.... show off :) EDIT: OK, so thats weird.... Dmut, did you create then delete a post?

Why do I get this mental picture of Dmut posting this message, whilst gently stroking his own copy of this book, located on the table next his monitor.... <shudder>

whoah! Myself and Dodger talked briefly about this only a few days back, and it was on my ever-increasing list of things to look at. Which two dlls was it btw?

I think he means that the same graphic/image can be used in both games for the same function, but in different profiles and with different macros/keypresses.

one thing to watch for is that most gfx cards use the DVI as their primary display if there is a monitor attached. No problem, use the DVI + adapter for your normal screen (the one you play games on), and use the VGA port for the touchscreen... or vice versa... i am sure you can work something out that would work

all the touchscreens I have seen use a VGA cable, so you should be able to use a DVI to VGA adapter and run TB on the second screen (via the DVI connection)

make sure you read the how-to and the README files first, and play with the bundled profiles. All the config files are plain text, so you can read them in your favourite text editor. Once you have scared yourself silly with the config file syntax, go grab TouchBuddy Toolkit, which make sthe profile creation so much easier. The problem with writing a program and then letting other have it is that I know how it all works, and quite often miss things in the docs about how to make it work.

in a client/server setup, you run two instances of TB On your game machine, you select "server" mode and start it On the second machine you select "client", select the profile to use, then start that. when you click on buttons on screen displayed by the TB client, the info is sent across the network from the TB client to the TB server, and the TB server finds the correct window (if configured to do so), and sends the macros/keypresses. Yes, it really is that simple... no magic involved... :)

download TBTk and try. I knocked up an EECH profile last night, and it took me longer to create the image files than it did to load them into TBTk and create the config.

yes, that will work... I test in local mode without a touchscreen, just using my mouse on my second screen, and it works fine. I use my Touchscreen on another PC but can also use the mouse on that to select the buttons.

TekaTeka - for... err.. just about everything he has done :)

Screens - we have a list of screens that are known to work over here: http://www.touch-buddy.com/forums/showthread.php?t=53 and http://www.touch-buddy.com/forums/forumdisplay.php?f=8 (The list of tested screens needs to be updated!) As for ease of use, probably best to ask one of the other guys in here who use TB + TBTk (I may be a bit biased if I replied :) )

The forums are working again now (theydown due to a problem at the hosting site): http://www.touch-buddy.com/forums/index.php

its dodgers site, and he is "idle" on his instant messenger, so I am logged in and trying to work out what went wrong (and fix it maybe)

just noticed that the TouchBuddy forums are currently unavailable (for an unknown reason).... sorry!