Capt Zeen

If you are using one of my export.lua, check the solution in this thread, reply n15.

for that you need to use the files modified that comes with the package you donwloaded of the A10C profile. And of course you need to configure the monitor configuration to indicate the position of the viewports on the screen.

Ok. if you are using one of my export.lua, look for this line: os.setlocale("ISO-8559-1", "numeric") and comment it like this: -- os.setlocale("ISO-8559-1", "numeric") That fix the problem. now i need to go out with my wife, when i come back home, i am going to revise why this line dont work. Thanks a lot to alpha7-bravo4, he discover the problem a couple of days ago! ..

I am updating my beta to 1.5.5 to test the problem.

Gracias Silver_Dragon. Cualquier dia de estos me pongo a hacer modelos ! Le tengo ganas.

OK, here you got your fixed KA50 profie. The problems was the 4th in the list. using 3 or more monitors, Helios dont do the reset monitors very well, and dont move the bindings to the correct monitor. To solve the problem just follow the intructions. Anyway, here you got the file already fixed: https://drive.google.com/open?id=0B5mdZ8jTY3lqUEx0MlNnOWRNV2s The A10C profile you send me has lost all the bindings on one of the procces you did. So start again from a original profile, and check, at the end, using notepad++ if the bindings are in the correct monitor. (The bindings are in the last half part of the code) ..

Send me your profile and i can take a look.

hello all! Back to work... WIP on left and right panels: left panel WIP right panel WIP ..

Good job ! Really interesting script to improve missions.

Great, great news! BST, thanks for your effort !

Hello all I added a new section on my site with the usually asked questions about Helios and my profiles. I am going to collect those questions here too, to try help people find solutions faster. if you want to contribute, post your question and/or solution, here, and i'll update the main post, time to time. Here you got the first list: Frequently asked questions : -- Helios projecting cockpit dashboard on the wrong monitor You have to reset monitors in your Helios profile. Use the Helios Profile Editor and do a "reset monitors", make the monitor numbers match the Windows monitor numbers. -- Helios dashboard dont fit completly my monitor There are a lot of monitor aspect ratios and resolutions. You must use the profile that best fit with your resolution. If the aspect ratio of your monitor is not the same as the profile, you can see an empty space on the right, or on the bottom. -- After reset monitors, my profile miss some labels, letters or numbers When Helios scale the profile to fit with your monitor configuration, he scale the font sizes of all the existing labels on the profile (letters and numbers). Sometimes, the scale of the font dont fit well with the scale of the label-box itself, and that cause the text disapear. to fix it, just click on the label-box and make it a bit bigger, till the text appears again. Then save again your profile. -- After reset monitors, my profile dont work at all, any gauge or switches moves when they do on the cockpit (Usually configurations with 3 or more monitors) sometimes, converting to systems with 3 or more monitors, Helios move the graphics to the correct monitor, but not the bindings. They stay in monitor 2, even if you move everything to monitor 3, or other. To solve this problem, look the number where you put it the profile inside and open the profile in notepad++ and using the tool replace, replace all the "monitor 2" by your correct number. For example "monitor 3" -- I can see red squares with a big black X inside, on my profile Helios can't find the images in the correct place. Revise and be sure you put all the images of the profile in the correct folder, usually in my documents/Helios/images -- No gauges working at all. probably you got a problem in the export.lua of DCS check if you are using the correct export.lua for your profile, and check if you put it in the correct place, usually in "my saved games/DCS/scripts" -- In Windows 10, DCS dont receive the switches actions from Helios, but Helios receive the cockpit switches actions from DCS If everything is installed in the correct place, and the problem persist, try runnig Helios in Administrator mode. If you are using windows10, the UAC can block the outputs from Helios to DCS. To be sure, everything is correctly installed, open helios in administrator mode, then open notepad with an empty document, and mantain focus on it. When you click on the buttons or switches, you can see some letters appears on the notepad document. Thats mean Helios is sending the keyboard command correctly. If DCS dont get the keyboards from Helios, probably is because the UAC, try to low a level of security and try again. -- Helios is working good, but i can't see the MFCs or the Abris, Skhival, etc To see the different viewports from the game you need to be sure you are using the correct monitor configuration files, and the airplane related .luas. Each installation package, have all the files you need to prepare the game to export the viewports to the other monitor. So read the instruction and install using JSGM the correct ones. --Helios do not recognize the correct size for UHD 4K monitor resolutions In Windows 10, right-click on desktop --> Display Settings For the UHD (4K)-display move the slider "Change the size of text, apps and other items" to the left (100%). Helios will now recognize the screen resolutions correctly. --From DCS 1.5.5 export.lua dont work anymore if you are using one of my export.lua, look for this line: os.setlocale("ISO-8559-1", "numeric") and comment it like this: -- os.setlocale("ISO-8559-1", "numeric") That fix the problem. Or use the latest export.lua from the web site. to be continued.... ..

Yes, i am working on it right now.

yes ! do it !

If everything is in the correct place, and the problem persist, try runnig Helios in Administrator mode. If you are using windows10, the UAC can block the outputs from Helios to DCS, too. To be sure, everything is correctly installed, open helios in administrator mode, then open notepad with an empty document, and mantain focus on it. When you click on the buttons or switches, you can see some letters appears on the notepad document. Thats mean Helios is sending the keyboard command correctly. If DCS dont get the keyboards from Helios, probably is because the UAC, try to low a level of security and try again.

Please, look on the post 41 on this thread. I remade the default.lua, compatible with lasts versions of DCS

Hola a todos ! Ya esta listo ! El nuevo y flamante perfil de Helios para el Gazelle. En esta ocasión he usado el interface del ka50 para exportarlo al helios. la conversión es mucho más difical y trabajosa que si uso el interface del FC pero de esta manera hay muchas ventajas: Ya no ha que preocuparse por los teclados internacionales, funciona siempre, pues no uso teclados para mandar los comandos, y por supuesto no hay que instalar un default.lua para las teclas, con el siguiente ahorro de problemas. espero que os guste..... podeis seguir el post oficial en https://forums.eagle.ru/showthread.php?t=175334 Y como de costumbre lo podeis encontrar en mi pagina web: http://www.captzeen.com Alli encontrareis instrucciones de como instalarlo y como configurar los viewport de pantalla. ...

Hello all. I just finished and published the Gazelle Helios profile. You can follow the main post here and you can get it on my site: http://www.captzeen.com Hope you like it ! ..

Hello all !!! Here we come, with another Helios profile! This time for the SA342 Gazelle version L, M and Mistral. For this profile i followed the recomendation of Lefuneste, and i make the profile using the KA50 interface in Helios, instead of the FC one. That was my first idea when i start to do Helios profiles, but in that time, the source code of helios was closed, so i decided to use the FC, for his easy use. The conversion was harder to do, trying to convert values from the SA342 to KA50, but at the end, i dont need to create a new keyboard table with a default.lua, and i dont need to worry about different languajes in diferent countries. And even, i dont need to worry about changes on the default.lua, that developers do time to time. And of course, for the final user, (you), is a more easy installation ! Hope you like it ! For this profile i exported all the instruments, lamps, selectors, switches and levers in the cockpit, and the collective. Of course i added the navigation panel from others profiles, so you can check airport charts, tactical maps, ndbs, etc PROFILE FILES: SA342_v1.0.hpf .....................16:10 monitor resolutions SA342_v1.0b.hpf .....................16:9 monitor resolutions main panel radio panels weapons panel EXPORT.LUA Important notice !! Included in the Scripts folder, you can find the export.lua, DCS 1.5.4 compatible, ready to export data A10C, KA50, FC3, F-15C, P-51D, UH-1H, A10C radio fix, MI-8 v1.5, and SA342 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 Thanks to Lefuneste. I started the code for the SA342 profile following his rough Helios profile for the Gazelle. You can find it here. 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. PROFILE FEATURES - Pilot Dashboard: - All the instruments, switches and lamps - TV: - All the Encoders, Switches and lamps. - A hole in the background is prepared to insert the TV viewport from the game - RWR: - All the Encoders, Switches and lamps. - A hole in the background is prepared to insert the RWR viewport from the game - Weapons panel: - You can choose between the L and M version of the weapons panels - All the Encoders, Switches and lamps. - A hole in the background is prepared to insert the WEAPONS viewport from the game - Radio panels: - panel with all the radios together: Copilot intercom, UHF, FM, AM, and ADF - All the instruments, switches, lamps and displays. - 2 holes in the background prepared to insert the RADIO UHF and FM viewports from the game - Flare dispenser panel: - All the Switches and lamps. - Collective panel: - All the Switches implemented - 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 airport freqs, locations, ids, etc. -Airport Circuit Example -List of the NDBs - About panel: - Info about the profile and version. INSTALLATION --Install Helios if you don't have it yet. (http://www.gadrocsworkshop.com/helios/latest) -Copy the profile you need, for your resolution , on the profiles folder, usualy in user/my documents/helios/profiles -Copy the folder Capt_Zeen on the images folder, usualy in user/my documents/helios/images -Run the HeliosProfileEditor, load the profile SA342 you want to use, and perform a Reset Monitors from the menu Profile. -Save the profile -Dont forget to use the correct export.lua i included in the package, Copy it in C:\Users\yourusername\Saved Games\DCS\Scripts, but first make a backup copy of your actual export.lua. -IF you use Tackview, Tarst 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 included in the package, there is a folder called "DCS Monitor Configuration" width a complete folders structure you can drop on DCS World instalation folder. This structure prepare the diferents lua scripts to export the views to the second monitor to represent the Nadir, Radio panles, RWR, TV and Weapon panel display. You will need to change the coordinates x and y of every viewport and the width and height sizes of them in the DCS Monitor Configuration\Config\MonitorSetup\2_monitors-SA342.lua Change it before copy to the game folder, and save a copy of this structure, cause DCS world rewrite this files every update! To calculate the correct position of each viewport, run Helios and start the profile. Take some screenshots with all the paneles opened, radios and weapons using print screen key on the keyboard, and paste the images in any art program. Paint from Windows works well. Put the cursor over the left-up corners of every empty spaces and write down the coordinates. Drag a box from that point to the right_down corner, and take the width and height of the rectangle. Modify the 2_monitors-SA342.lua width your correct numbers. and you can now copy the complete "DCS Monitor Configuration" folder to the DCS game folder, or use a Mods control program like JSGME to do it. Also, you can use this template to calculate the position and sizes of the diferent viewports: KNOWN ISSUES - -In the cockpit of the Gazelle, in the Stby HA, you can block the instrument moving the rotator to the upper position (thats dont happens in the main HA, so i figure is a bug, but not sure). To unblock it again, you need to pull the button, and then rotate at the same time with the mouse. In helios, you can't do two things at the same time, so if you block the stby HA by error, you need to unblock it from the cockpit. 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. As always you can get it from my site: http://www.captzeen.com ...

Hello. First of all, for the F15 you only can export the radar viewport, not the RWR. And you code need to look something like this: _ = function(p) return p; end; name = _('Export example'); Description = 'Export example'; Viewports = -- Put your values in , and delete all exports that you don't want to use ! -- You will have to determine the area for the MP/SP GUI { Center = { x = 0; y = 0; width = 1980; height = 1080; viewDx = 0; viewDy = 0; aspect = 1.3333333333; } } LEFT_MFCD = { x = 2060; -- (this is 1980 + 80) y = 80; width = 500; height = 500; } RIGHT_MFCD = { x = 2680; y = 80; width = 500; height = 500; } UIMainView = Viewports.Center ..

OK, test this one. Is fixed !! https://drive.google.com/open?id=0B2qXxbaFFjJ3dmRwOFIzSVNlU1E This is the 3er time i see this error. And always converting to system with 4 or more monitors. Helios move the graphics to the correct monitor, but not the bindings. They stay in monitor 2, even if you move everything to monitor 3. Like in this case If someone have this problem too: To solve this problem just open the profile in notepad++ and using the tool replace, replace all the "monitor 2" by your correct number. In that case "monitor 3" Let me know how it works!

send me your helios profile, please.

We have the same problem in our last two misions. In some planes after sometime, or after changing the freq in the radios, the radio menus dont work anymore, You only can see the caption of the radio menu, but not the F1, F2, etc. In both misions, we used groups of 4 units of KA50 and groups of 2 SU25.

You can use this code to do a blinking indicator: local FlipFlop = math.cos( os.clock()*10 ) * TriggerValue return string.format("%s",math.max(0,FlipFlop)) Where TriggerValue is the value you get in Helios from the export.lua. But, you need to be sure the value is sended to Helios each cycle, because Helios dont change the indicator, if the value dont change between cycles. To do that you can add something that changes everytime, for example the seconds of the clock, to the value of the switch, and then remove it in Helios before do the flipflop.

I just test it, and it seem to work correct. I need to check the aoa instrument, i dont know why is not working properly, but everything else is working fine, so...... You need to be sure you are using the correct export.lua Notice that in my site, in download section, only one of the export.lua files is compatible with su27/33. Use that one ! if you are using that one, check it again ! open the export.lua in notepad++ and look at the top of the file. The data need to be 20/Jan/2016 Well if you are sure you are using the correct one, and the profile dont work, please send it to me. I can take a look at your profile, sometimes Helios broke the profiles when you do the reset monitors, in some circunstances. Screenshot from tonight test: ..

Thats a good idea. I am going to implement this in the new gazelle monitor configuration. Thanks !