Han Schouten

You may safely wipe out the FSUIPC solution that I have mentioned before. Unexpected side effects make this solution useless! So, buying a second (or a third) BU0836A might be the best possible solution, after all.

The ipc.setowndisplay statement will produce a pop-up window with the name at the spot and with the dimensions that you have specified. Each subsequent ipc.display statement will display its content in this pop-up window and for the duration that you possibly have specified along with its contents. At http://forum.simflight.com/topic/68257-lua-package-for-fsuipc-and-wideclient/ you will find a review of all new functions with a short description. These functions are available from FSUIPC v. 4.95. I can live with errors that don't harm. It's just that the LINDA editor produces a lot of noise while editing and while saving your work. Regards, Han

I ran into a nice IPCready.LUA example conerning vertcal speed at landing. The first statement was ipc.setowndisplay("FRM", 0, 60, 6, 1) and the LINDA editor qualified this with " 6: attempt to call field 'setowndisplay' (a nil value)". A search on the Internet reveiled that this a new function that comes with FSUIPC v. 4.95. After installing this version, the sample code functions correctly, but LINDA continues to report the error message mentioned. With this new FSUIPC release, a number of new functions are introduced that also may need attention.

The BU0836A interface board accommodates up to 8 axes and 36 buttons, four of which are grouped into a hat button arrangement. If you don't need a hat button, this is a waste of four ordinary buttons. FSX, P3D and LINDA don't offer a solution for this. FSUIPC, however, provides a possibility to assign some behaviour to any of the four buttons, as if it were ordinary buttons. LINDA got me programming my button behaviour in LUA. The assignment of LUA functions to buttons in LINDA is much more elegant and better maintainable then calling LUA files in FSUIPC. There are at least two ways to get around this limitation in LINDA: buy another BU0836A (not expensive anyway) or store your LUA procedure without enveloping function ... end block as a conveniently named file with the extension ".lua" in the Modules folder of FSX or P3D and assign this behaviour with "LUA " to some button in FSUIPC. I got my "ordinary" buttons 32 to 35 working in this way. Yet, for reasons of uniformity and maintainability, I would prefer a solution comparable to the one of FSUIPC in LINDA.