Capt Zeen

Black Shark 1? Do you know that you can update the serial of your Black Shark 1 to Black Shark 2 in the dcs site?

The UH1H profile was made it, long time ago, using the old FC2 helios interface. And all the outputs are done directly by key commands. So the permormance was to bad, and of course the refresh rate of the key commands depend directly from the key repetition time in windows. The good news: i am working right now in the new UH1H v2.0 using the new general purpuse interface, so soon, the new version is going to be published, without all the old problems. Probably is going to be finish this week. I let you know how it is going.

Hello all. Right now i am in the mainland, in holidays. I come back home next week. Then, I am going to make a video tutorial about how install Helios and the profiles for newbies.

Hello VirusAM Right now, i am on the mainland in holidays, and don't have here the saitek panels, so i can't test it. I come back home the next week. As soon i arrive i can check it.

Just that !! Happy new year to all the dcs virtual pilots ! :pilotfly:

Open the profile with the helios control center and make a screenshot of the complete desktop. Then send it to me. I am going to prepare you the config file.

you problem is in the monitor configuration Read the instructions, and use the files in the profile package to configure where the viewports need to be show.

Using the export.lua you can access to all the information of the airplanes in real time. If you want to use that info for hardware, i recomend you to take a look to DCS-bios, with that you can get all the data you need. and of course, visite this section of the forum: https://forums.eagle.ru/forumdisplay.php?f=101

ill try tonight to sse if it works,

I am not at home now, tonight i am going to take look. i prepared time ago, default.luas for differents airplanes and what you want, can be done. i let you know how it goes

Hello all! i just published a new improved Helios profile for the MI-8 using the new Helios 1.4. Here you got the official post: https://forums.eagle.ru/showthread.php?t=227088 Hope you like it !

MI-8MTV2 v2.0 ! (Helios 1.4 or later required) After looking for several solutions to create a complete input/output MI-8 Helios profile, i decided to create a new interface for Helios, that permits me make profiles more easely. Once started with the new general purpose interface i discover other people working on a new version of Helios! So... i decided to colaborate with that project, and include my new interface on that new Helios version. This is the first profile created with this new Helios 1.4 interface. A complete new MI-8 Helios profile! Whats new on this version: - New Helios general purpose interface: Using the new general purpose interface in Helios 1.4 i was able to create a full profile, with inputs and outputs directly to DCS, so we do not need the default keyboard luas anymore, and of course, no more files for diferent countries and keyboards. - New inputs values for each instrument Now the inclusion of direct inputs make the profile more eficient and fast, so all the instruments move smoother that previos versions. - Copilot instruments: The copilot console, now, uses the apropiated values for his instruments, and are not just mirrors of the pilot console. I added aswell the copilot radio panel, just waiting for some day whe multicrew become operative for the MI-8 - New MI-8 instruments: I created a brand new ADI and altimeter for the MI-8, so we dont need to use the KA50 ones on this profile. - New Cover switches: I created aswell, a new Cover switch for Helios, that permits create the cover switches of the cockpit with a more cleaver solution and fast response to open/close actions. - Improved art: I revised all the art of the profile, adding better details and improving the visuals. - Placement for the Garmin: I prepared the profile to be Garmin "compatible" if you want to implement it on the second screen. IMPORTANT NOTICE: This profile uses the new Helios 1.4 version, so you need to install this version to run the profile. You can download the Helios 1.4 from here: https://www.digitalcombatsimulator.com/en/files/3302014/ Pilot panel Engineer panel Copilot panel with Garmin enable Engine panel Weapons panel ARC panel Weapons and anti-icing panel - PROFILE FILES: MI-8_v2.hpf .........................16:10 monitor resolutions MI-8_v2b.hpf ........................16:9 monitor resolutions - EXPORT FILES: Included in the Scripts folder, you can find the export.lua, and a folder with the Helios export files. With them you can export data for the A10C, KA50, FC3, F-15C, P-51D, UH-1H, A10C radio fix, SA342, Mig21bis, L39ZA, F/A-18C and this MI-8 v2.0 profile. This file is a modified version of the Loophole Updated version from 09/11/2014, ( http://forums.eagle.ru/showthread.php?t=97222 ) - Monitor aspect resolutions: I made two different profiles, v1.0 for 16:10 monitors and v1.0b for 16:9 monitors. Use the one better fit width you monitor resolution. - Thanks: I made the entire graphic art, based on screenshots of the simulator, and the textures folder of the game. I used the airport charts from http://www.virtual-jabog32.de and the tactical chart TC-1 created by =MAF=Mongoose and the NDBs list created by Lino_Germany. For the export.lua i used the Loophole version, compatible width KA50, A10c and FC3 as a base for all my implementations. In the export.lua i include a couple of functions by [FSF]Ian to export the digits of the UV26 for the MI-8 I want to thanks aswell to all the people who help me, in the DCS forum, every time i reached a deadlock, somewhere! And of course to Gadroc for creating Helios, this great software. I want to give thanks to Bluefinbima, for let me include my new general purpose interface on the new Helios 1.4 project. And of course Cylution, yzfanimal and Damien022 for the good work done. PROFILE FEATURES - Pilot Dashboard: - All the instruments, switches and lamps - Copilot Dashboard: - All the instruments, switches and lamps. - Prepared to implement the Garmin panel - Ingeneer Dashboard: - All the instruments, switches and lamps. - Added lamps to check if radios are ON - Added R828 channel and freq used - Collective width implementation for cargo drops switches and guards, Gas max/min lever and rpm less/more switch - Rotor brake - Left UP console: - All the instruments, switches and lamps. (including all dcs 1.5 implementations) - Rockets / anti ice console: - All the instruments, switches and lamps. - Weapons panel: - All the instruments, switches and lamps. - Complete breakers panel switches - Engines panel: - All the instruments, switches and lamps. - Added engines cutoff valves - Added main arm weapons switch with his red lamp - Breakers panel: - Complete breakers panel switches. (including all dcs 1.5 implementations) - ARC and KO50 panel: - All the instruments, switches and lamps. (including all dcs 1.5 implementations) - Right UP panel: - All the instruments, switches and lamps. (including all dcs 1.5 implementations) - AUX panel: - All the instruments, switches and lamps for the R828, UV26 and Jadro Radio - radio panels: - SPU floating panels for pilot and copilot, width all the switches - Bomb and ESBR Panel: - All the instruments, switches and lamps. - Freq panel: - Open a panel width a list of the airport fequencies - Navigation panel: -Airports visual operation charts v4.04 -Airports diagramss v4.04 -TC-1 Tactical Chart -Caucasus general area map, with airports and table width freq, locations, ids, etc. -Airport Circuit Example -List of the NDBs - Exterior background panel: - Panel to change the exterior background you can see beyond the dashboards. You can select between: airport Day, airport Night, flyind Summer and flying Winter - About panel: - Info about the profile and version. INSTALLATION -Install the new Helios 1.4 or later if you don't have it yet. https://www.digitalcombatsimulator.com/en/files/3302014/ -Copy the profile you need, for your resolution, on the profiles folder, usualy in user/my documents/helios/profiles -Copy the content of the folder Images on the helios images folder, usualy in user/my documents/helios/images -Run the Helios Profile Editor, load the profile MI-8 you want to use, and perform a Reset Monitors from the menu Profile. -Save the profile -Copy the content of the folder "scripts" in C:\Users\yourusername\Saved Games\DCS\Scripts, but first make a backup copy of your actual export.lua, just in case! -If you use Tackview, Simpleradio or another external scripts, copy the corresponding lines from your old export.lua to the new one. RUNNING THE PROFILE -Open the Helios Control Center, select the profile and start it. CONFIGURING THE SECOND MONITOR You dont need to use any special configuration to use this profile, because dont use any viewport from the game. Unless you want to use the Garmin in the 2nd monitor. in that case, you need to expand the viewport to the second monitor, and move the 2d garmin there. Only if you want to use the garmin on the second monitor: Included in the package, there is a folder called "DCS Monitor Configuration" Modify the 2_monitors-MI8.lua width your correct numbers, and you can now copy folder "Config" over the main DCS innstallation. OTHER CONSIDERATIONS If you use Helios and TARS or TACKVIEW you can have miss workings due to the way Helios works width the export.lua. To prevent this, just move the lines for Tars or tackview to the very end of the export.lua in C:\Users\yourusername\Saved Games\DCS\Scripts. MORE TO COME i started the new UH-1H V2.0 ! download from the site: www.captzeen.com Hope you like it ! ..

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\SA342\Cockpit\clickabledata.lua There you got all the information you need for that.

Hello all, just for your info: The data from IFEI and UFC can be extracted using the List_Indication function. So you can access the engines rpm data. I created this code to implement the IFEI and UFC, but at the end, i dont use it because the viewports export do the same job. You can use it if you need it to implement the engines rpm Of course you can delete all the data you dont need: function parse_indication(indicator_id) -- Thanks to [FSF]Ian for this function code local ret = {} local li = list_indication(indicator_id) if li == "" then return nil end local m = li:gmatch("-----------------------------------------\n([^\n]+)\n([^\n]*)\n") while true do local name, value = m() if not name then break end ret[name] = value end return ret end function check(indicator) if indicator == nil then return " " else return indicator end end function check_num(indicator) if indicator == nil then return 0 else return 1 end end function Process_FA18C_HighImportance(mainPanelDevice) -- Capt Zeen code local _LAST_ONE = 0 -- used to mark the end of the tables local MainPanel = GetDevice(0) --IFEI data local IFEI_Data_table = {} for i=1,21 do IFEI_Data_table[i] = "" end --IFEI textures local IFEI_Textures_table = {} for i=1,16 do IFEI_Textures_table[i] = 0 end --UFC data local UFC_table = {} for i=1,17 do UFC_table[i] = "" end -- getting the IFEI data local li = parse_indication(5) -- use 5 for IFEI, 6 for UFC if li then --IFEI data IFEI_Data_table[1] =check(li.txt_BINGO) IFEI_Data_table[2] =check(li.txt_CLOCK_H) IFEI_Data_table[3] =check(li.txt_CLOCK_M) IFEI_Data_table[4] =check(li.txt_CLOCK_S) IFEI_Data_table[5] =check(li.txt_DD_1) IFEI_Data_table[6] =check(li.txt_DD_2) IFEI_Data_table[7] =check(li.txt_DD_3) IFEI_Data_table[8] =check(li.txt_DD_4) IFEI_Data_table[9] =check(li.txt_FF_L) IFEI_Data_table[10] =check(li.txt_FF_R) IFEI_Data_table[11] =check(li.txt_FUEL_DOWN) IFEI_Data_table[12] =check(li.txt_FUEL_UP) IFEI_Data_table[13] =check(li.txt_OilPress_L) IFEI_Data_table[14] =check(li.txt_OilPress_R) IFEI_Data_table[15] =check(li.txt_RPM_L) IFEI_Data_table[16] =check(li.txt_RPM_R) IFEI_Data_table[17] =check(li.txt_TEMP_L) IFEI_Data_table[18] =check(li.txt_TEMP_R) IFEI_Data_table[19] =check(li.txt_TIMER_S) IFEI_Data_table[20] =check(li.txt_TIMER_M) IFEI_Data_table[21] =check(li.txt_TIMER_H) IFEI_Data_table[22] =check(li.txt_Codes) IFEI_Data_table[23] =check(li.txt_SP) IFEI_Data_table[24] =check(li.txt_DrawChar) IFEI_Data_table[25] =check(li.txt_T) IFEI_Data_table[26] =check(li.txt_TimeSetMode) IFEI_Data_table[27] ="" for i=5,8 do-- Helios dont like the ":" so i replaced it for another character if IFEI_Data_table[i]==":" then IFEI_Data_table[i] = "x" end end --IFEI textures IFEI_Textures_table[1] =check_num(li.RPMTexture) IFEI_Textures_table[2] =check_num(li.TempTexture) IFEI_Textures_table[3] =check_num(li.FFTexture ) IFEI_Textures_table[4] =check_num(li.NOZTexture) IFEI_Textures_table[5] =check_num(li.OILTexture) IFEI_Textures_table[6] =check_num(li.BINGOTexture) IFEI_Textures_table[7] =check_num(li.LScaleTexture) IFEI_Textures_table[8] =check_num(li.RScaleTexture) IFEI_Textures_table[9] =check_num(li.L0Texture) IFEI_Textures_table[10] =check_num(li.R0Texture) IFEI_Textures_table[11] =check_num(li.L50Texture) IFEI_Textures_table[12] =check_num(li.R50Texture) IFEI_Textures_table[13] =check_num(li.L100Texture) IFEI_Textures_table[14] =check_num(li.R100Texture) IFEI_Textures_table[15] =check_num(li.LPointerTexture) IFEI_Textures_table[16] =check_num(li.RPointerTexture) IFEI_Textures_table[17] ="" end -- getting the UFC data local li = parse_indication(6) -- use 5 for IFEI, 6 for UFC if li then UFC_table[1] =check(li.UFC_MainDummy) UFC_table[2] =check(li.UFC_mask) UFC_table[3] =check(li.UFC_OptionDisplay1) UFC_table[4] =check(li.UFC_OptionDisplay2) UFC_table[5] =check(li.UFC_OptionDisplay3) UFC_table[6] =check(li.UFC_OptionDisplay4) UFC_table[7] =check(li.UFC_OptionDisplay5) UFC_table[8] =check(li.UFC_OptionCueing1) UFC_table[9] =check(li.UFC_OptionCueing2) UFC_table[10] =check(li.UFC_OptionCueing3) UFC_table[11] =check(li.UFC_OptionCueing4) UFC_table[12] =check(li.UFC_OptionCueing5) UFC_table[13] =check(li.UFC_ScratchPadString1Display) UFC_table[14] =check(li.UFC_ScratchPadString2Display) UFC_table[15] =check(li.UFC_ScratchPadNumberDisplay) UFC_table[16] =check(li.UFC_Comm1Display) UFC_table[17] =check(li.UFC_Comm2Display) UFC_table[18] ="" for i=8,12 do -- Helios dont like the ":" so i replaced it for another character if UFC_table[i]==":" then UFC_table[i] = "x" end end end -- sending IFEI and UFC data SendData("24", string.format("%s", table.concat(IFEI_Data_table,", ") ) ) -- IFEI data >>> "ADI", "Slip ball" SendData("21", string.format("%s", table.concat(IFEI_Textures_table,", ") ) ) -- IFEI data >>> "ADI", "Pitch Steering Bar Offset" SendData("20", string.format("%s", table.concat(UFC_table,", ") ) ) -- UFC data >>> "ADI", "Bank Steering Bar Offset" FlushData() end

Other panels are supported too. I use the multipanel to display other info like altituded, speed, vvi, etc. In the leds of the gear i use to display the airbrakes, hood and gears. On.

Yes, use "CENTER_MFCD"

Your dcs.log dont show any problem with the export.lua, so the problem can be on the profile . Send me your profile, after doit the reset monitors.

TROUBLESHOOTING: Wen you install a Helios profile, and you got a problem, try to identify exactly what happens. Usually two issues can show up: 1 - The gauges, switches, lamps, etc, don't work 2 - The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work. In the FIRST case: The gauges, switches, lamps, etc, don't work Helios is probably not getting the DCS info needed, and thats because the export.lua is not doing his job. So... - check if the export files are you using are the correct ones - check if the place where you installed is the correct one: Export.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\ HelioCore.lua and HeliosExport.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\Helios\ - then double check again ! - and of course, always use my last export files. If you are using a system with more than two monitors, - check the FAQ on the site. There is a bug on Helios that can asign a incorrect monitor to all bindings on the profile. There you got a solution for that. If everything looks correct with the export files and still no joy, - run a mision, and exit DCS, - then check the dcs.log in savedgames/dcs/logs and look for errors in the export.lua . If something wrong happens in the export.lua the log tell you where to look at. If you are using other tools with Helios, like: Simpleradio,Tackview DCS-bios etc, you can try to change the order of the lines in the export.lua. Those ones do not give problems, but some tools can, so give it a try. In the SECOND case: The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work. Ok, this is important to know, Helios do not export the viewports, is DCS who do that. Some DCS modules are ready to export some of his viewport, but not all of them. That's the reason we need to change some .luas to make that module ready to export the viewports. In the F18 case, and at this date ( 29/Aug/2018 ), only the 2 DDIs and the AMPCD are ready to export. The IFEI, RWR and UFC are not, so we need to overwrite those .luas with other ones ready to export viewport. Usually, in my profile packages you got everything you need to do that operation in a folder called monitor configuration. So... - Check if you installed the files in the correct place. I recomend to you use JSGME or OVGME to do the job, because in every DCS update those files are rewriten again - Then edit the MonitorSetup file to adjust the viewports to your monitor configuration. (2_monitors-FA18C.lua ) - In DCS options, put your max resolution ( this is the total of your monitor resolutions in horizontal and vertical, for example two monitors 1920x1080 placed in horizontal layout, the total resolution is 3840x1080 ) - In DCS options, uncheck full screen option - In DCS options, select the monitorsetup file to use (the one your just edited) IMPROVING THE LINES QUALITY IN THE EXPORTED VIEWPORTS use this information to improve the lines visuals... https://forums.eagle.ru/showpost.php...&postcount=117 from my discord channel, by Kudox: "Hi all this is what i discovered on MDG export . The wire solution looks terrible. set the MDI_init.lua for default . the file you what to modify is C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua . The draw is used for 3d cockpit and exported MDG . modify as a balance between the two . Here are my defaults that work for me stroke_thickness = 0.5 stroke_fuzziness = 0.25 -- Currently is used for DMC generated fonts black outline DMC_outline_thickness = stroke_thickness * 3 DMC_outline_fuzziness = stroke_fuzziness * 1.1 DMC_stroke_thickness = 0.5 DMC_stroke_fuzziness = 0.25 looks great now. Id ditch the wire draw. I ll look into the RWR and UFC UFC use the brightness control in cockpit works fine, RWR C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\indicator\RWR_ALR67_init.lua Modify shaderLineDefaultThickness = 3 see if that helps " ..

DCS bios export the digits of the UFC too.

you need to use a module controller, like JSGME, if not you can become frustrated!

you dont need helios to export the radar of he F5e. You can export the radar directly frm the options menu on DCS. chosse a monitor configuration with the MFCD right, and select the resolution using the size of the total your two monitors in horizontal. fro the vertica, use you bigest monitor resolution.

I use helios and dcs-bios without problems. try to put the Helios line, first in the export.lua, then the DCS-bios line.

Thanks a lot Imp! That was the part that I did not know how to do!

i just tested tonight, all viewport looks correct on my system.

i just downloaded the profile from the Mega site and no problems at all.