TouchBuddy FC2 Export - Beta Testers Needed!

[Wild.Bill.Kelso]

I need some Beta Testers!

Attached to this post you will find a fixed Export Script for use with Flaming Cliffs 2. If you want to test this out please agree to at least post back here with your findings good or bad. I want to know if it works for you, as well as if you have any problems.

So, Please post back here after your testing either way!


NOTES:
The Export Scripts for DCS Lockon FC2 have changed a little from the old Lockon FC1. Also, Zorlac had 'no' error handling in his script , which was the major problem, causing it TouchBuddy to stop reading the data if you crashed your aircraft! So, it would work once, (or until you crashed your aircraft), then stop working.

I tested this while crashing a lot and it seems to be working fine now online and offline. Please report back...

WBK

[Wild.Bill.Kelso]

Anybody tried this yet?

[Wild.Bill.Kelso]

Oh well...

I will assume that no response is a good thing and this must be working fine.

This has been moved into the TouchBuddy Downloads section.

[blaster454]

I'm working on it! Give me a few days and I'll get some feedback to you! I'm trying to combine the export scripts for a few different functions and it is challenging!

[Wild.Bill.Kelso]

Today I tweaked my lua script to write the touchbuddy-export.dat file out to C:\touchbuddy-export.dat. Then I put it in BlackShark as well, so both LOFC 2.0 and BS would both write out the script to C:\ and then changed TB to look for the touchbuddy-export.dat file also at C:\

So, now I can play either FC2 or BS and both will write out the export data and my TB profile will always see it. But BS seems to only provide the weapons loadouts, not warning panel info or RWR/TWS info, so it really doesn't help much for BS... It was just a test.

[Scrambler]

Sorry for not posting sooner but don't have a touch screen connected at the moment.

Fired it up in Client/server mode with the laptop [using your LomacFC2-Exeter-WBC profile] and seems to work fine

Well done for sorting this out.

[Wild.Bill.Kelso]

Good Test. I don't have a Client/Server setup. Thanks.

[MackTheKnight]

I'm a bit new to touch-buddy so maybe I'm doing something completely wrong here.

Trying to get your new lock-on 2.0 lua export file to work but I keep getting this annoying pop-up error in TouchBuddy whenever I enable the lua pointer in the config file.


My config file is in the attached zip... Any advice would be greatly appreciated.

Thanks,
Mack

[Scrambler]

Hi

It can be difficult to tell from your cfg file exactly what the problem is, I have checked the file and the pointer to the Lua data export file may be incorrect. TheTouchbuddy cfg file should point to the touchbuddy-export.dat file not to the TouchBuddy_FC2_Export.lua file. This is what I have in my cfg file :-

lomac_data_file = C:\Games\Eagle Dynamics\LockOn Flaming Cliffs 2\touchbuddy-export.dat

Note the touchbuddy-export.dat file gets written to the root directory, yours should probably look like this , taking into account your FC 2 install directory :-

lomac_data_file = C:\Games\LockOn Flaming Cliffs 2\touchbuddy-export.dat

Another thing to bear in mind is that any settings in the Touchbuddy-local.cfg will take priority over settings in the touchbuddy.cfg file. It is probably better to set the pointer to the lua file in the "local cfg" file. Check it anyway to make sure you don't have any conflicting settings.

A few other points, are you runninng in local or client/server mode. [If the latter your IP settings look a bit odd]

Have you modified the FC2 config.lua file, you need to enable the export for it to write the data file that Touchbuddy needs i.e config.lua needs to have the EnableExportScript set to true:-

EnableExportScript = true


The export.lua file must have the following line added at the end

dofile("./Config/Export/TouchBuddy_FC2_Export.lua")


Note you must edit the Lua files with Notepad ++ or they may get corrupted.

Hope this makes some sense, let us know how you get on.

[Wild.Bill.Kelso]

Thanks for helping Scrambler!

The only other things I would say is that I don't think that EnableExportScript needs to be set to true. Mine is set to false and it works. That variable confsues me because it's name seems to want us to turn it on to export stuff. But again, I have it to false and always have had it to false.

The other thing you should check is look for those lines in your error message:
<-- Here in m/--[ <-- Here [/

That looks like some bad text or comments in one of the files. But it says it is in TouchBuddy.exe, so that is strange.

What version of TouchBuddy are you running? You should have 1.3.0.17. (This is really Rev18, but Zorlac just forgot to up the version number when he made it. That is what we have in our downloads section