Capt Zeen

This afternon i was installing the multipanel and the switch panel. In my frst attemp to setup, everything works bad, gear lights change colors at ramdon, the values on the displays go crazy, etc. Then i realized that i was using the pre.release verison of DCSfligtpanel, so i download the release version and then everything start to work correct ! I just want to thanks all the work done on the tool, really impressive And now a more complicated question: for the VVI on the KA50 i am using this formula: ((VARIO_SPEED/65536)*30)-15 But the problem with that is the values are not correct because those values have different scales in diferent parts of the instrument. In my helios profiles i have a function to do that, but dont know how to doit in DCSFP Any of you has the correct way to do it? Thanks a lot in advance

Nice videos. Waiting for more! Thanks a lot.

Try using direct numbers instead of variables. With 2 similar resolutions monitor is easy to calculate, and you don't change your monitors everyday so... _ = function(p) return p; end; name = _('2_monitors_KA50'); Description = 'configuracion para dos monitores' --MAIN GAME VIEWPORT TOTAL SIZE AN ASPECT Viewports = { Center = { x = 1921; y = 0; width = 1920; height = 1080; viewDx = 0; viewDy = 0; aspect = 16/9; } } --SHKIVAL LEFT_MFCD = { x = 1; y = 0; width = 960; height = 700; } --ABRIS RIGHT_MFCD = { x = 961; y = 0; width = 960; height = 1080; } UIMainView = Viewports.Center Thats code if for the KA50. For A10C create a new one and change the width and height of the 2 MFCDs, for a square size, for example width=960 and height = 960 And don't forget to set your monitor resolution to 3840x1080 in the options panel in DCS ..

Ouch! I remenber now ! Some versions ago,ED change the name of that folder and removed the "s". Olders profiles still with that name on the package. Sorry....

Don't forget this: "-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 Abris, Skhval, PVI digits, Ekran and UV26 digits." If you don't copy this files in your game folder no aditional viewport export can be done.

Rest in peace Gospadin. My condolences to his wife and family.

First, check if you got the config file in the correct place. An then ,check in windows monitor configuration, how your monitors are ordered, take in cosideration that coordinates 0,0 are in the most left monitor, upper-left corner.

:smilewink: Nice work Marques !

yes. no problems at all.

Slowhand, how many time they take for send you the new serial? I want to make the change too, and i dont want to be much time without flying the ka550

I am using Helios with 2.5 and no problems at all. So you probably miss something, perhaps the correct export.lua

Thanks a lot, ED !

Hello again ! 1) I never use sounds in Helios, and i really dont know if you can doit. Take in consideration that when you use Helios with DCS, is DCS who made the sounds. 2) For the buttons indicators, you got a especial one in Helios. This button need 4 states: ON normal, ON pushed, OFF normal and OFF pushed. This buttons have 2 inputs: the state of the button (pressed or not) and the value of the indicator it self (Light ON or OFF) 3) Do not look too much to the AP buttons on the SU25T profile. That a very special case because FC3 do no have any way to know how the buttons are, pressed or not. So i made a very complicated way to determine the state of the buttons taking in consideration the keys pressed. In the F18 module, you are not going to have this problem, becase you can know whats the state of every button, so everything is going to be easy. 4) LALT is Left Alt, RALT is right Alt. The & symbol probably an error, you can delete it. 5) You can put actions when push or release buttons. Where to put it, only depend of the functionality you want or the exact moment you need the action to be performed. ..

Even in that case it is posible to add new buttons to the module. You need to edit the default.lua file from your module keyboard folder. Of course you need to know the device and button id you neeed to add, this information can be get it from the clickable.lua file. Anyway, is not a easy thing to do unless you dit it a couple of times, hehe.

Download the latest default.lua for the UH1H from my site! Don't use the ones that comes with the UH1H profile package.

It can be done, but is not a matter of symple change images. In the KA50 profile i used the VVI gauges that comes with Helios, and those can`t be modified. But is possible to recreate a completly new VVI using a new image and a potenciometer used as the needle of the instrument. I f there are a really interest in his i can prepare the new gauge for you.

Hello Sobe. Been the F18 one of my most loved airctafts, it is going to be my next Helios proyect. My plan is to prepare first the main frontal panel and publish it as soon as posible when the module comes out. Then... with more time, finish the rest of the panels,left and right sides of the cockpit. Now asking your questions... Implement the a10c interface to use with the f18 is not a easy thing. You need to program in the export.lua all the conections between the two modules. The imputs and the outputs devices need to be linked. I am going to make a video during the process od creating the f18 profile and publish it too in my youtube channel so everyone with the interest can learn to do it in future modules. ..

Hello all ! Here you got a new night version of the Gazelle profile for Helios by Chardly38. Thanks a lot to Chardly38 for his contribution, he make a great work converting all the panels and switches to night version. -This version need some art from the original Capt Zeen day version, so you need to have installed the original version of the profile, to have all the graphics. -Use the latest export.lua from the download section You can find it in the Download section, hope you like it ! ..

:doh:

Hello Danzer. YOu really don't need to use this export.lua This fix is only for people using the CapLoz Helios profile.

:doh:

Well, Looks like DCS is on top of Helios. make sure you dont got "full screen" checked on DCS options. need to be in windows mode to work. And uncheck the disable aero interface The code you send is not the export.lua It is the monitor configuration, so you can arrange the diferent viewo¡port on the screens. Anyway looks correct. I recomend you to rescale the helips profile for your monitor, too. You are not using the complete resolution for it, so everythig looks smaller. To do that use the option "reset monitors" on the helios profile editor. For the export.lua you can use the latest export i got on my web page. It works with several airplanes and helos. Bye!

Thanks Ed, for the letter, and a big big thanks for all those years making happy to the fly combat simulator fans. Still remember the day i bought my first Lock on. And from that day, i never stop flying with your aircrafts and helos. Comming from the videogame devellopment industry, i know the difficulty of focus in this small area of products, so i really apreciate your efforts. Thanks a lot , again.

Capt Zeen L-39ZA Forward Cockpit Helios Profile !! English and Russian cockpit ! 16/9 and 16/10 aspect resolutions ! Hello all ! I just published the brand new L-39ZA Forward Cockpit Helios Profile! You can follow the official post here: https://forums.eagle.ru/showthread.php?p=3301208#post3301208 And of course you can download it from my web site, download section: www.captzeen.com Hope you like it ! ..

Capt Zeen L-39ZA Forward Cockpit Helios Profile !! English and Russian cockpit ! 16/9 and 16/10 aspect resolutions ! Here we come, with another Helios profile! This time for the L-39ZA Forward cockpit. I made the profile using the A10C interface in Helios. With that, we dont need to prepare different versions for differents countries, we dont need the default.lua to define all the keyboard commads, because i redirect directly to DCS from helios, so we dont need to worry abous future changes. And of course, for the final user, (you), is a more easy installation ! So here you got a fully input/output L-39ZA profile. Hope you like it ! For this profile i exported all the instruments, lamps, selectors, switches and levers in the Forward cockpit. Soon the future i'll preprare a Rear cockpit one too. Of course i added the navigation panel from others profiles, so you can check airport charts, tactical maps, ndbs, etc The profile can be changed from English Cockpit to Russian cockpit, replacing the graphics from the ones in the required folder. By default, the profile is english configured. - Profile files: L39ZA_v1.0.hpf .....................16:10 monitor resolutions L39ZA_v1.0b.hpf .....................16:9 monitor resolutions - Graphics files: The profile can be changed from English Cockpit to Russian cockpit, replacing the graphics from the ones in the required folder. By default, the profile is in english. The folder names inside images/L39 are, "english cockpit" and "russian cockpit". Just copy all the files inside the folder you want and paste to images/L39 replacing the actual ones - Export.lua: Important notice !! Included in the Scripts folder, you can find the export.lua, ready to export data A10C, KA50, FC3, F-15C, P-51D, UH-1H, A10C radio and TACAN fix, MI-8 v1.5, SA342, Mig21bis and L39ZA 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 deadend, somewhere! And of course to Gadroc for creating Helios, this great software. PROFILE FEATURES - Pilot forward Dashboard: - All the instruments, switches and lamps - Left and Left-back panel: - All the instruments, switches and lamps - Right and Right-back panel: - All the instruments, switches and lamps - Bottom panel: - All the instruments, switches and lamps - Brakers panel: - All the switches - 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 -Freq panel: -list of the airport frequencys - 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 L39ZA 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 This profile do not need any special actions for the second monitor. KNOWN ISSUES -Everyting looks correct right now, so no Known issues at the moment 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. Right back panel Right front panel Bottom panel Left front panel Left back panel Breakers panel And of course, you can put the cockpit in Russian labels too !! Hope you like it ! ! ! As always you can download from my web site, download section. www.captzeen.com ...