Helios for A-10 Warthog and Ka-50 Black Shark at same time

[Loophole]

I love the Helios software - it is really great, but I was a little frustrated that I could not easily switch from flying the A-10 to the Ka-50. The problem is the Export.lua file, which exports different data for each aircraft.

 

I decided to have a crack at addressing the problem, and hacked together a combined A-10/Ka-50/FC3 Export.lua file based on Gadroc's individual Export files. It's not the most elegant LUA code in the world, but it seems to work OK. I have attached a copy for anyone who would like to use it.

 

It currently handles A-10C, Ka-50, and the Flaming Cliffs 3 aircraft. It should be possible to extend it to handle the other high-fidelity aircraft, once I get around to it. If anyone has Export files for other DCS aircraft, I'm happy to take those and merge them into the logic.

 

I hope this is of use to some of you!

 

Revision History

 

Updated 27/7/2013 to add FC3 support

Updated 06/01/2014 with FC3 AOA fixed, plus tidier and more comments

Updated 28/07/2014 with fix for F-86F-related crash

Updated 7/08/2014 previous fix broke the A-10C, now fixed

Updated 20/08/2014 fixed some logic issues that crashed the script when changing aircraft during a mission

Updated 11/09/2014 Re-enabled HSI export for FC3 aircraft; now seems to be working.

Updated 24/09/2014 Added some improved HSI logic from Capt Zeen (thanks), and cleaned up code a little.

 

Installation

 

Drop the Export.lua file into <your user folder>\Saved Games\DCS\Scripts

Export.zip

Edited September 24, 2014 by Loophole
Newer version of Export script.

[LNR212]

Great!

 

I will check it out tomorrow... just what i was looking for...!

 

Btw, is it possible to get an mustang helios profile or at least to use the standard-gauges from helios for other aircraft (mustang) to create a simple similar cockpit?

[agrasyuk]

Excellent. thank you

[Loophole]

lnr212, I think the Export.lua will have to be enhanced in order to get gauges working for the P-51 and other aircraft; I can see how the Export works, but have not yet found out how to determine the new aircraft-specific parameters for the P-51 and others. Not even sure if the older-style 'FC' aircraft support that sort of export at all. It is on my 'to do' list, though.

[Barrakooda]

Loop

 

Thx will come in handy especially as modules get added

[LNR212]

...hm, doesent work for me :(

am i doing something wrong?

 

i just took your lua file, but i cant use both helios profiles. i have to quit the game, set the other game up in the profileeditor and start the game again. then it works (as before).

 

how are you doing?

 

when i set up black shark in the profileeditor, a10 is gone, and vice versa...

[agrasyuk]

I just dropped the attached export file.

Both profiles for BS and Hog were working, nothing to re-setup

[LNR212]

ok, ok, ok... it works! :-)

 

Thanks!

[Loophole]

Not sure what the problem might be - but if you use Helios to set up the Export.lua that will overwrite my customised version. Are you sure you copied it into the correct location?

[cichlidfan]

Cool. I was going to poke around in those export files this weekend. I will have to give this a shot.

 

EDIT: Btw, I would love to have the exports work for the P-51. I have been toying with a profile for some of the switch panels but gauges would be sweet.

Edited March 1, 2013 by cichlidfan

[Loophole]

I haven't investigated the P-51, but it ought to be possible. So should FC3, but I have not had any success with that; not sure if the problem is in the Exports or with Helios.

[tietze]

It works nicely!

[doveman]

I believe this has to go in Saved Games\DCS\Scripts now with 1.2.3.

[tietze]

I believe this has to go in Saved Games\DCS\Scripts now with 1.2.3.

 

Yup!

 

You can further append the following when TACView 1.2.3 and TARS 1.0.2.b2 is installed and configured (TARSExport.lua & TacviewExportDCS.lua should also be present as well as the relevant files in the DCS World folder in Program Files):

dofile(lfs.writedir()..'Scripts/TARSExport.lua')
local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewExportDCS.lua')

Edited March 1, 2013 by tietze

[Chazz Ulric]

Yup!

 

You can further append the following when TACView 1.2.3 and TARS 1.0.2.b2 is installed and configured (TARSExport.lua & TacviewExportDCS.lua should also be present as well as the relevant files in the DCS World folder in Program Files):

dofile(lfs.writedir()..'Scripts/TARSExport.lua')
local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewExportDCS.lua')

 

I have the do file in my save games dcs scripts you know the rest. However my file does not look like yours dofile. Do I need to ammend it to look like yours? This getting confusing to me.:helpsmilie:

[doveman]

I have the do file in my save games dcs scripts you know the rest. However my file does not look like yours dofile. Do I need to ammend it to look like yours? This getting confusing to me.:helpsmilie:

 

It's the export.lua in your Saved Games\DCS\Scripts folder that you need to add those lines to, if you're using TARS and TACVIEW that is.

 

dofile is just a command so you shouldn't have a file called do or dofile!

[DickDastardly]

Thanks very much for putting this together Loophole - it works great :thumbup:.

Cheers,

DD

[_Dredd]

Excellent work, thanks very much.

 

I don't intend to throw this thread off; does this work with FC3 F-15C?

I've got A-10C working but unsure if FC3 works also? I can't find another thread that mentions whether FC3 exports work?

If it does, I guess my Helios profile is wrong, is their a sample Helios profile to test with ?

[Loophole]

It does not work properly with FC3 at the moment. You can use FC3, but you won't get any exports. It ought to work, but so far I have been unsuccessful, and I don't know what the problem is - either Helios doesn't like the FC-style exports, or FC3 works differently to FC and they haven't documented the API changes.

 

I have a profile that works with FC3 as far as sending keystroke macros, but no live instruments or switches that mimic the 3D cockpit controls.

[Loz]

Thanks Loophole. This solved my probs trying to get my exports going with BS into Helios. Great work!

Rep Inbound :)

[Loophole]

A related suggestion...

 

In case people haven't seen it, I should also mention this post: http://forums.eagle.ru/showthread.php?p=1430336#post1430336

 

It's a simplified standard for the Lua changes needed to export an instrument display on to another monitor.

[argento]

Works like a charm, thanks!

[Loophole]

Updated the Export.lua file to include FC3 support- finally figured out where it was broken and managed to fix it! Use the Flaming Cliffs 2 "interface" in Helios in your profile.

[Loophole]

Note - it now works with FC3! yay!

[McMicha]

Do you post a sample (or your) Export.lua?