s1man

Ideal :) Glad you got it working :thumbup:

Cool, Yep i had to combine my export.lua to have the ka50/a10 etc exporting depending on aircraft your flying

Hi Cowboy, Yep helios does still work with the latest build. Though the A10 radio's dont. Capt Zeen has made some great profiles for different aircraft using the FC2 interface http://www.captzeen.com/helios/index.asp Currently im working on a Mig21 Interface for open source helios which is coming along nicely. I cant comment on whether its worth setting it all up again. Thats up to you. Though i know i couldnt live without it.

I would have to agree with this, until you have the gloves to go with it VR will be nice but i would have to go back to using a mouse to click on things which i would not enjoy.... once the gloves are here my pit can go bye bye :)

There wouldnt be any issue with the different resolutions, i used to have a few different res monitors working with dcs and helios. actually i still have one thats different and its working fine. Just my 2 cents for what its worth i would definitely recommend a capacitive multi touch touchscreen. I still have a small resistive but its really only good for a couple push buttons.. terrible for rotaries. Optical worked fine but i couldnt get on with it, seemed to press buttons before my finger had hit.. maybe it was because it was fairly cheap, or maybe just personal preference... so i ended up replacing with 2 capacitive touchscreens and kept my small lilliput resistive just for rarely used pushbuttons.

Well im trying to create a Mig21 interface... though if i need help again from Gadroc i will double check my code first :wallbash: got most of the axis/switches/buttons working so far, just going through the annunciators at the moment. I know i can get all the flight gauge data out of dcs (currently using that to run the built in gauges through the fc2 interface on the final closed source version for myself while i continue doing the proper interface) though i have no idea how to create the actual gauges yet... even if i manage to work it out... im definitely no artist though. i have a lot more to learn yet. Though the gauges will be the last thing for me to worry about, ive got lots more to do yet. Never realised how much work it was to do at first... hats off to Gadroc for all the work he put in thats for sure. If i manage to get it all working i will certainly put in a pull request though.

From what i remember it was a pic by MontyPython76 in the user files section http://www.digitalcombatsimulator.com/en/files/1026153/ I just cut out bits i needed for explaining the switches i still haven't mapped.

Thats a pity, well hopefully LN will sort it out at some point.

Cool, thanks, yes i can get the IFF button on the front panel to work, just not on the right panel. As you say though i guess it must be implemented i just cant find out the right panel keybindings for those IFF switches

Thanks Home Fries, yeah i see the axis, yes its a pity you cant set hotkeys for some things. Initially i was hoping i was being stupid and just couldn't find them... im guessing not now. Well hopefully LN will read this and think about setting it all up in a future patch.

Hi guys, hopefully someone can help. Im trying to map all the switches to keybindings so i can map them in my helios profile, i have found the keystrokes required i can use for most things and mapped, however the following things that are circled in yellow im unable to find. Like radio on R panel, or SPO10 volume (found an axis but not keybindings in the mig21 options) The hardest part for me has been trying to work out what things are called. There seems to be a few discrepancies between what a switch is called when you hover over it in the cockpit compared to what its called in the keybindings.... Any help would be much appreciated

Very nice :thumbup:

Bit late but just worked out some bits, using the FC2 interface for helios and just exporting to that in the export.lua. what ive got so far.. though some of the numbers are a bit out at the moment, lots of trial and error. Hopefully some of the great lua peeps can do much better. function ProcessMig21Exports() MainPanel = GetDevice(0) --IAS local ias = MainPanel:get_argument_value(100) local airspeed_normalized = MainPanel:get_argument_value(100) local airspeed = (airspeed_normalized * 1000) * 0.561 --eng rpm local engRpm = MainPanel:get_argument_value(50) local engOut = engRpm * 100 --pitch local pitch = MainPanel:get_argument_value(109) pitch = pitch * 1.5 --bank local bank = MainPanel:get_argument_value(108) bank = bank * 3.4 --vvi local vvi = MainPanel:get_argument_value(106) vvi = (vvi * 20) * 2 --aoa aka uua local aoa = MainPanel:get_argument_value(105) aoa = aoa * 0.75 -- baro alt local altBar = MainPanel:get_argument_value(112) altBar = (altBar * 10000) * 3 --radio Altimeter local altRad = MainPanel:get_argument_value(103) altRad = (altRad * 1000) / 2.5 --hsi aka ksi course indicator local hsi = MainPanel:get_argument_value(111) hsi = (math.pi * 2.0) * hsi hsi = hsi * -1 --log_file:write(hsi) --log_file:write("\n") SendData("9", string.format("%.2f", engOut) ) SendData("14", string.format("%.2f", airspeed ) ) SendData("1", string.format("%.2f", pitch * 57.3) ) SendData("2", string.format("%.2f", bank * 57.3) ) SendData("16", string.format("%.2f", aoa * 57.3 ) ) SendData("13", string.format("%.2f", vvi) ) SendData("4", string.format("%.2f", altBar) ) SendData("5", string.format("%.2f", altRad) ) SendData("8", string.format("%.2f", (hsi * 57.3)) ) FlushData() end

This is great news indeed :thumbup: After all the hard work Gadroc put in i would love to see a number of people take up the challenge of helping out on this project.

Happy new year, hope you all at LN have a great one and keep up the good work in the new year. P.S Loving every minute in your MiG-21 :thumbup: