Capt Zeen

Hola a todos ! Por fin he acabado el perfil de Helios para el MI-8MTV2 ! ! En esta ocasion he conseguido implementar la cabina completa, y sincronizar completamente entre Helios y DCS. Tambien es compatible DCS 1.2.16 y DCS 1.5, por supuesto con todas las implementaciones nuevas con las que nos sorprendió Belsintec en la ultima version ! Lo podeis descargar desde mi web: http://captzeen.com/helios tambien podeis seguir el hilo principal en : http://forums.eagle.ru/showthread.php?t=150479 Espero que os guste ! ! ..

Hello all ! At least! i finished it ! DCS 1.5 and DCS 1.2.16 Compatible Several month ago, I start the project, width the goal to make a profile for MI-8, width full cockpit implementation, instruments, lamps, switches, and everything syncronized between Helios and DCS. The big problems for that was the lack of interfaces in Helios. At the moment, Helios only support A10C, KA50, and a simplified FC interface, so, implement new aircrafts is not easy. My first idea was to create a MI-8 interface for Helios, giving support to that helo, but thats means learn how interfaces works in Helios, and then create a new compilation of the program, and for that i need support from Gadroc. So, my final solution was to send all the data from the cockpit across the FC interface. Thats solve the input side in Helios, and the output part was solved creating a complete keyboard configuration, prepared to work from Helios. The resoult is a fully functional MI-8 profile, width all the data from the cockpit and full clickable and syncronized from Helios. In other words, same funtionality as KA50 and A10C profiles. This time, i created, aswell, a program to convert the profiles to diferent international keyboards. Now this operation only take me some seconds, before this taked me days! So for this one you have ENGLISH, FRENCH, SPANISH, ITALIAN, GERMAN and for the first time, RUSSIAN keyboards ! I implemented, too, all the new improvement Belsintec did on the MI-8 for DCS 1.5 for this profile i exported all the instruments, lamps, selectors, switches and levers in the cockpit, the collective and the rotor brake. Of course i added the navigation panel from others profiles, so you can check airport charts, tactical maps, ndbs, etc Hope you like it ! You can get it in my site: http://captzeen.com/helios EDIT: New default.lua for the MI-8 profile !! 10/Aug/2016 Lasts changes and improvements on the MI-8 module, changed the original default.lua, so i prepared a new one, with all the new changes and the keys definitions for my profile. You can get it from the download section on my site ! ..

Hello all. Setting the last keys on my helios profile i detected this error: Reset G indicator button turn OFF the UV-26 !! I checked the Clickeabledata.lua and i found the two buttons width the same device number. Is that correct ?? elements["PTR-RSPE-TMB-WINK002"] = default_button(_("Accelerometer Reset Button - Push to reset"), devices.CPT_MECH, device_commands.Button_6, 910) elements["PTR-UV26-ONOFF"] = default_2_position_tumb(_("CMD Power Switch, ON/OFF"), devices.UV_26, device_commands.Button_10, 910) also happens width this two: elements["PTR-RSPE-LVR-REDGRP005"] = default_axis_limited(_("5.5V Lights Brightness Rheostat"), devices.LIGHT_SYSTEM, device_commands.Button_11, 914, 0.0, 0.2, true, false, {0.0, 1.0}) elements["PTR-L45-BTN"] = default_button(_("CMD Num of Sequences Button"), devices.UV_26, device_commands.Button_4, 914) Thanks ..

Hello all ! I just see this thread and i found it very interesting. As you may know, i create Helios profiles for diferents airplanes. Due to the limitations of Helios avaiable interfaces, (a10c, ka50 and FC) i need to work in the export.lua everytime i make a new profile for a specific airplane, like P51, Mi-8, Su27 etc. Till now, i am trying to mantaing a export.lua capable of work width all my profiles, but everyday this export.lua is growing in size. Normaly i check what kind of airplane we are flying, and then i run a specific function for that airplane, where i collect all the data i need to send to Helios. One of the things i notice is the fact that several info is captured several times for different purposes, for example, i need the information of the radios freq and channels, so i get this info from the devices, but later, Ptars ( a comunications sofware we use in our scuadron) do exactly the same. So this info is captured two times. if you need my help for something just let me know. My background and career is a Lead Artist, but i have some programming experience aswell.

As Cloudie did, i copied the export.lua. monitor configurations, and init luas. I just run the Caploz profile and it works. I have the same problems width the viewports.

I got mine working on 1.5. I dont tested all the keys but i was flying those days and no problems at all. I checked http://forums.eagle.ru/showthread.php?t=122790&page=5&highlight=devrim and no changes on KA50 keyboard as far as i see.

Sobe, this afternoon i am going to implement the caploz a10C profile in my 1.5 beta. I let you know how it goes and the steps to do it.

Hello all. One of the more tediuos tasks i need to do when i finish a helios profile is create the diferent versions for diferent international keyboards. This take me hours of works changing switches assignaments. So at the end, i decided to make a tool to do the process automaticaly. I started this afternoon, and the tool is ready and works! now i convert the profile to another languaje width only one click ! Still dont know why i dint make this before, haha ! Well, the question: I just want to confirm, specialy width german, french and russian users if the table i am using to convert the keys is correct. i am using the keyboard configuration in windows to create the tables, but i am not sure. Here you got the tables: Dim spanish(47) spanish(0)="º" spanish(1)="1" spanish(2)="2" spanish(3)="3" spanish(4)="4" spanish(5)="5" spanish(6)="6" spanish(7)="7" spanish(8)="8" spanish(9)="9" spanish(10)="0" spanish(11)=chr(39) ' simbolo del rem spanish(12)="¡" spanish(13)= "q" spanish(14)= "w" spanish(15)= "e" spanish(16)= "r" spanish(17)= "t" spanish(18)= "y" spanish(19)= "u" spanish(20)= "i" spanish(21)= "o" spanish(22)= "p" spanish(23)= "`" spanish(24)= "+" spanish(25)="a" spanish(26)="s" spanish(27)="d" spanish(28)="f" spanish(29)="g" spanish(30)="h" spanish(31)="j" spanish(32)="k" spanish(33)= "l" spanish(34)= "ñ" spanish(35)= "´" spanish(36)= "ç" spanish(37)= "z" spanish(38)= "x" spanish(39)= "c" spanish(40)= "v" spanish(41)= "b" spanish(42)= "n" spanish(43)= "m" spanish(44)= "," spanish(45)= "." spanish(46)= "-" Dim french(47) french(0)="²" french(1)="&" french(2)="é" french(3)=chr(34) ' comillas dobles french(4)="´" french(5)="(" french(6)="]" french(7)="è" french(8)="!" french(9)="ç" french(10)= "à" french(11)= ")" french(12)= "-" french(13)= "a" french(14)= "z" french(15)= "e" french(16)= "r" french(17)= "t" french(18)= "y" french(19)= "u" french(20)= "i" french(21)= "o" french(22)= "p" french(23)= "`" french(24)= "+" french(25)="a" french(26)="s" french(27)="d" french(28)="f" french(29)="g" french(30)="h" french(31)="j" french(32)="k" french(33)= "l" french(34)= "m" french(35)= "ù" french(36)= "ç" french(37)= "w" french(38)= "x" french(39)= "c" french(40)= "v" french(41)= "b" french(42)= "n" french(43)= "," french(44)= ";" french(45)= ":" french(46)= "!" Dim english(47) english(0)="`" english(1)="1" english(2)="2" english(3)="3" english(4)="4" english(5)="5" english(6)="6" english(7)="7" english(8)="8" english(9)="9" english(10)="0" english(11)="-" english(12)="=" english(13)= "q" english(14)= "w" english(15)= "e" english(16)= "r" english(17)= "t" english(18)= "y" english(19)= "u" english(20)= "i" english(21)= "o" english(22)= "p" english(23)= "[" english(24)= "]" english(25)="a" english(26)="s" english(27)="d" english(28)="f" english(29)="g" english(30)="h" english(31)="j" english(32)="k" english(33)= "l" english(34)= ";" english(35)= chr(39) ' rem symbol english(36)= "\" english(37)= "z" english(38)= "x" english(39)= "c" english(40)= "v" english(41)= "b" english(42)= "n" english(43)= "m" english(44)= "," english(45)= "." english(46)= "/" Dim german(47) german(0)="^" german(1)="1" german(2)="2" german(3)="3" german(4)="4" german(5)="5" german(6)="6" german(7)="7" german(8)="8" german(9)="9" german(10)="0" german(11)="ß" german(12)="´" german(13)= "q" german(14)= "w" german(15)= "e" german(16)= "r" german(17)= "t" german(18)= "z" german(19)= "u" german(20)= "i" german(21)= "o" german(22)= "p" german(23)= "ü" german(24)= "+" german(25)="a" german(26)="s" german(27)="d" german(28)="f" german(29)="g" german(30)="h" german(31)="j" german(32)="k" german(33)= "l" german(34)= "ö" german(35)= "ä" german(36)= "#" german(37)= "y" german(38)= "x" german(39)= "c" german(40)= "v" german(41)= "b" german(42)= "n" german(43)= "m" german(44)= "," german(45)= "." german(46)= "-" Dim italian(47) italian(0)="\" italian(1)="1" italian(2)="2" italian(3)="3" italian(4)="4" italian(5)="5" italian(6)="6" italian(7)="7" italian(8)="8" italian(9)="9" italian(10)="0" italian(11)=chr(39) ' simbolo del rem italian(12)="ì" italian(13)= "q" italian(14)= "w" italian(15)= "e" italian(16)= "r" italian(17)= "t" italian(18)= "y" italian(19)= "u" italian(20)= "i" italian(21)= "o" italian(22)= "p" italian(23)= "è" italian(24)= "+" italian(25)="a" italian(26)="s" italian(27)="d" italian(28)="f" italian(29)="g" italian(30)="h" italian(31)="j" italian(32)="k" italian(33)= "l" italian(34)= "ò" italian(35)= "à" italian(36)= "ù" italian(37)= "z" italian(38)= "x" italian(39)= "c" italian(40)= "v" italian(41)= "b" italian(42)= "n" italian(43)= "m" italian(44)= "," italian(45)= "." italian(46)= "-" Dim russian(47) russian(0)= "ё" russian(1)= "1" russian(2)= "2" russian(3)= "3" russian(4)= "4" russian(5)= "5" russian(6)= "6" russian(7)= "7" russian(8)= "8" russian(9)= "9" russian(10)= "0" russian(11)= "-" russian(12)= "=" russian(13)= "й" russian(14)= "ц" russian(15)= "у" russian(16)= "к" russian(17)= "е" russian(18)= "н" russian(19)= "г" russian(20)= "ш" russian(21)= "щ" russian(22)= "з" russian(23)= "х" russian(24)= "ъ" russian(25)= "ф" russian(26)= "ы" russian(27)= "в" russian(28)= "а" russian(29)= "п" russian(30)= "р" russian(31)= "о" russian(32)= "л" russian(33)= "д" russian(34)= "ж" russian(35)= "э" russian(36)= "\" russian(37)= "я" russian(38)= "ч" russian(39)= "с" russian(40)= "м" russian(41)= "и" russian(42)= "т" russian(43)= "ь" russian(44)= "б" russian(45)= "ю" russian(46)= "." Thanks in advance ! ..

My first experiences using Helios width DCS 1.5 (still in windows 7): - I was abble to run my mi-8 helios profile whidhout problems. Everythings work the same way. - I was abble to run my ka-50 helios profile whidhout problems. Everythings work the same way. - I was abble to continue working on the helios profile editor, implementing all the new 1.5 features of the mi-8. No problems at all. - I was forced to change some export.lua data to fix the uv26 digits in the mi-8 profile. In the 1.2.16 version the indicator you need to export is the 4, and in the 1.5 version the indicator changed to 5. i can export the abris and the Skhival too: still need to test pvi digits and ekran ..

i see.... looks like it is dx10.1 only

I got the same problem, i can run the game, but no trails on missiles and flares. Don't know if i am missing something else. My card is an ATI Radeon 4870

Yes! i got version 1.0 of the profile ! Everything is working, all switches, instruments and lamps (Thanks to [FSF]Ian for the help in UV26 digits and MyG for his help in the breakers switches) Now the question: Make sense wait a couple of days and implement all the new features promissed in the new beta 1.5, before publishing? I got all the art and mechanics ready, only need the data from the new switches and instruments.

Thanks a lot MyG, now it works ,!

Hello all. Some of you know i am creating a mi-8 helios profile, and that force me to create all the key commands needed for all the switches and buttons of the cockpit, even the undefined yet. Doing that, and revising the keyboard/default.lua and clickabledata.lua, i found several errors and duplicity of some commands. I am going to prepare a list of those in a different thread. Another thing i found is the imposibility to assign key command to the breakers switches from the number 75. I made a picture to show you wich ones dont work when i assign a key: The green ones works perfect, i just asign a new key combinations on the keyboard/default.lua and the keys work on the game and active the switch on the cockpit, but the red ones ( from number 75) dont move. it seems they dont have any input from keyboard. Any ideas about that?

Hello akuma. Can you give more details about the gauges that are you using and dont work ?

Thanks a lot for your help Ian. As always, you are a light on the darknest !!!

Well ! almost finished, only need to solve how to implement the UV26 digits. New Screenshots

Hello all I got everything exported from the MI-8, but i miss the UV26 digits. I search everywhere to get this data but no joy. At the end i made the ka50 solution, export the viewport to the second monitor, but i got this weird effect, the digits are backwards ! Any idea? Any solution to get the digits in the correct direction? or another way to get the digits from any device? thanks a lot !!

Yes, you can use it.

Hello all ! Just in case any of you dont visit the input and output subforum, take a look at the MI-8 Helios profile i am creating. I need to implement a couple of panels more and will be ready for be published. http://forums.eagle.ru/showthread.php?t=146458 Hope you like it.

Hello all I little update on the MI-8 progress, Version 0.7: Everything you see here is working!, instruments, lights, switches etc, syncronized in boths sides, from helios and from the cockpit. All the panels are compacted so you can arrange later the position of each one, to adapt to diferent monitor configurations. Hope you like it : . . . .

Hello all ! I am trying to define key asignaments to the undefined MI-8 commands and i have problems when i try to asign keys to a multiposition switch. Lets see. I can do something like this: {combos = {{key = '9', reformers = {'RWin','LWin'}}}, down = device_commands.Button_1, cockpit_device_id = devices.R_828, value_down = 0.1, name = _('R-828 Radio channel selector right'), category = _("Added by CaptZeen")}, {combos = {{key = '9', reformers = {'RWin','LWin','LShift'}}}, down = device_commands.Button_1, cockpit_device_id = devices.R_828, value_down = 0.0, name = _('R-828 Radio channel selector center'), category = _("Added by CaptZeen")}, {combos = {{key = '8', reformers = {'RWin','LWin'}}}, down = device_commands.Button_1, cockpit_device_id = devices.R_828, value_down = -0.1, name = _('R-828 Radio channel selector left'), category = _("Added by CaptZeen")} But width this, only can move one position on the selector to the right and one to the left. It seems like the value down 0.1 is absolute, not a increment. I can create a key asignament for each position, for example 0.2, 0.3, etc, but for big selectors can be a pain! There is no way to create a key assignament, and put a value as an increment, or decrement instead absolute values? Thanks a lot

This is what i got at the moment: Everyting is working ! , lamps, switches, instruments, and all syncronized, so you can click on the helios screen or in the cockpit. The same experience as the Ka50 helios profile ! Pilot console Central console Electric panels Start engines panel Right now i am worknig in the radio panel, is very advanced ! Next one, weapons.

OMG ! i forgot the tune button ! After years using it in the KA50 !! Thanks Ciribob, good point !