DickDastardly

Just got them working together too and the results are stunning: The Payload, MCP, TEWS & gauges in the (scaled down) image above are all displaying live data from LOMAC -this absolutely kicks ass and I encourage everyone to try both programs. Many thanks to both Zorlac and Mnemonic for your wonderful work on this stuff. Cheers, DD EDIT: Just to stress to anyone who (like me) doesn't have a touchscreen - you don't have to have one to run touchbuddy! So all that's needed to use these utilities is a spare screen (and preferably a 2nd PC too to minimise fps impact on the sim, although that isn't strictly necessary).

Thanks very much m8. Cheers, DD

If I'm understanding the touchbuddy.cfg file correctly, it seems to be using port 12000 so I don't think a port conflict can be the cause of the problem. I'm very new to touchbuddy though, so I may be missing something obvious. Cheers, DD

Fantastic :) BTW just to confirm that the fixes in the new version seem to work great - changes to regional settings are now unnecessary and the panel no longer crashes after ejecting. Great job m8! One problem I have had, though, is in getting the Virtual Panel to work with the Touch Buddy TEWS. If i add the line dofile("./Config/export/touchbuddy-export.lua") ...to the end of export.lua to enable the TEWS then I no longer get a "connected" message from VP and the dials don't function. Has anyone else been able to get both working at the same time? Cheers, DD

Woohoo! New version is up at Lock On files: http://lockonfiles.com/modules.php?name=Downloads&d_op=viewdownloaddetails&cid=83&lid=852&title=LockOn%20Virtual%20Panel%20v.1.3#dldetails

To be honest m8, I know quite a few English people whose English spelling is far worse than yours, none of whom know any Russian words beyond "Vodka". :) BTW I've just been having fun playing with the gauges some more, but I came across another small bug: When I eject, the gauges continue to work fine, but when my plane then hits the ground I get an "Invalid floating point operation" message which pops up repeatedly forcing me to kill LOVP.exe in the task manager. The bug doesn't always occur (and seems to happen less often in the SU-25T for some reason). Cheers, DD

You crazy Ruskies with your mixed up commas and decimal points ;). Seriously though, great job in tracking down the problem Mnemonic. The gauges work superbly for me now after following your suggestion. BTW if anyone else is trying the decimal change before the new version comes out, you only need to do it on the PC running Virtual Panel - it's not necessary to edit anything on your LOMAC PC (unless, of course, you're running both from the same machine). Cheers, DD P.S. A very very minor point, but in the dialogue box which appears after clicking Restore Gauges, "sure" is misspelt "shure".

I too am getting a "connected" message when the mission has loaded which changes to "disconnected" as soon as I unpause. None of the needles move for me at any time. I tried the debug version too and got the following in the text box (after unpausing): 0,00 127,48 138,89 8,00 0,99 -0,00 2002,10 1839,13 0,12 0,00 2,45 0,43 6,28 6,28 6,28 -35438,66 2000,00 408091,25 -35439,17 2002,10 408091,58 0,00 0,00 0,00 89,58 89,58 617,72 617,72 3775,00 0,00 If there's anything else I can do to help in tracking down the cause just let me know, as the program looks great and I'm very keen to get this working. Cheers, DD P.S. I have the original English LOMAC CD, and the download version of FC (patched to 1.12a). EDIT: I don't know anything about lua, but I noticed that the last line of export.lua refers to a file called "tacview.lua" which I don't seem to have. Could this be anything to do with the problem?

I seem to have the same problem as everyone else - when my mission loads I get a "connected" message at the top left of VP, but as soon as I hit "S" to unpause the game, the text in VP changes to "Disconnected". None of the gauge's needles move from their default positions at any time. I've tried running VP on the same PC as Lock On, using the following line: host = host or "localhost" ...in export.lua and I've tried running VP on a second PC which is networked to the first, using the line: host = host or "192.168.0.221" (which is the I.P. address of the PC running VP). In both cases I get the same results. I'd love to get this working as it looks like a great utility so any ideas/fixes would be much appreciated. If it's any help, my main PC is an Athlon XP3000 with 2 gigs of ram and an nvidia 7600GS video card. I'm running Lock On 1.12a and both PCs have Windows XP Pro. The only firewall software I'm running is the Windows one and I've given VP permission to get through on both PCs. Cheers, DD Edit: My Error.log file is as follows: 17/01/2007 10:23 V512091930 TrackIR DLL path: C:\Utilities\TrackIR4\ NPClient interface -- initialize OK NPClient : Window handle registration successful NPClient : NaturalPoint software version is 4.00 NPClient : Data transmission started TrackIR DLL path: C:\Utilities\TrackIR4\ NPClient interface -- initialize OK NPClient : Window handle registration successful NPClient : NaturalPoint software version is 4.00 NPClient : Data transmission started Dispatcher: track version = 512091930 Dispatcher: initial random seed = 9401375 Dispatcher: apply random seed = 9401375 Cosmos: Mission date assigned - Year:2004, Month:6, Day:22 DXDefTexture: failed to load knopki.tga, D3DXERR_INVALIDDATA. DXDefTexture: failed to load pribory-1-39.bmp, D3DXERR_INVALIDDATA. wHumanPlane::Init(InitData): New Flight Model of the Su-25T: Init starting... wHumanPlane::Init(InitData): New Flight Model Init finished. Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported. LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed LuaExport::LuaExportAfterNextFrame: closed Repeated many times, followed by.... LuaExport::LuaExportStop: closed

sheesh I get the exact same error message. It staggers me that a company which obviously contains numerous employees with large amounts of technical expertise can't organize something as simple as a straightforward e-commerce transaction. Distributing games directly over the net should be a win-win situation for developers and users. The developers don't have to share the profits with retailers and publishers so they should be able to charge considerably less than the game would have cost in a shop AND still make more from each copy they sell. Unfortunately at $35 for an expansion pack ED seem to have decided not to pass any of the savings onto the users. (In fact, by the time you factor in the cost of having to print your own manual you're probably paying more than you would for a typical store-bought expansion pack). I was prepared to overlook this however as I'd enjoyed playing the FC demo and wanted to support one of the very few developers of good flight sims. I was even prepared to overcome my reservations about the odious "Star Force" protection s/w despite having read some pretty horrendous stuff about it. (I'm sure I'm not the only one who regards the limit of 5 reinstalls or "system modifications" as pretty outrageous - in the last couple of years I've completely rebuilt my PC once, reformatted at least 3 times, replaced my main hard drive and upgraded several other components, presumably meaning that if I'd bought FC 2 years ago then I'd no longer be allowed to play the game by now). And now I find out that the payment processing system doesn't even work - it's as if ED are deliberately trying to shoot themselves in the foot. They seem to have gone out of their way to deter potential customers. DickDastardly