Capt Zeen

I am going to check that when i arrive at home this afternoon.

C:\Users\you user name\Documents\Helios\Images\Capt_Zeen

Yes, change the final directory on the installation proccess for that.

there is a new version of Helios: https://www.digitalcombatsimulator.com/en/files/3302014/ Try that one !

New Helios 1.4 Beta 3 version on the skys !!!!!! Oficial post: https://forums.eagle.ru/showthread.php?t=221100 download link: https://www.digitalcombatsimulator.com/en/files/3302014/ Thanks to BlueFinBima and all the collaborators ! ..

Amazing good job! From here i ask everyone uses my profiles, to test it in this new version. Soon wi'll be another version and we need as much feedback as posible, before release it. Right now i am working on a new complete Mi-8 2.0 profile, using the new features and the new General interface we included in the next Helios beta4 release. With this new multipurpose interface we are able to create profiles for airplanes that already do not have a specific interface in Helios. My plan is convert the UH1H profile to this new system aswell, as soon as possible, and at last forget about the keyboard files and problems! Thanks to BlueFinBima and all the collaborators!

send me the profile you saved, i can take a look on it.

Hello Shotgun Dexter. You need to load the f18 profile in the helios profile editor, first. Then do a reset monitor to configure the profile to your system, then save it with another name. that one is the profile you need to load with the helios control center.

send me your profile and i can take a look on it.

you need to configure your touch screen behevior in windows. i do not have a touch screen, so not sure what you need to do, but other people with that problem solved in windows

Open the profile in the helios profile editor and look for the layers called crystal, and delete them, or make ir smallers.

i am going to take a look on that Thanks!

Yes, i notice that several weeks ago. Looks like some values on the F18 dcsbios file are outside range. Perhaps AndrewW need to take a look on that. i am going to revise my aditions to the file to see if something comes from my changes ..

This afternoon i am going to look at home, i think i got it in my HD

check here, https://github.com/DCSFlightpanels/dcs-bios/releases some started a f5 dcsbios already ..

When Andrews made the F18 dcsbios file, the device number were correct. After that, ED changed the device number from the 38 and up, moving the device 38 content ( hotas) to the device 10. So all the device numbers from 38 need to be substract by 1. I made the corrections on my advanced F18 DCSbios file you can find in the DCS Flightpanels github download section. You can donwload from here: https://github.com/DCSFlightpanels/dcs-bios/releases ..

Hello BluFinBima. I was stating a Harrier profile for Helios, https://forums.eagle.ru/showthread.php?t=216139&page=2 I was looing for references and i just discovered this post. I never see it before. You did a great job adding a interface to Helios. This is something i was thinking to do some time ago, but the dificulty of create a new version, distribute it, and the possible malfunction of some systems, makes me go for another way. The thing is, i dont want to interfere with your work, and if you want to publish your profile, i can go for another airplane. Anyway, you can PM me if you like it, and see what we can do for the comunity. ..

Good guide, thanks for sharing! Just a coment: In one of the latest updates, ED added the lines to export the AMPCD, so my lines are not needed anymore on that .lua And the ED name for that viewport is now "CENTER_MFCD"

Hello BlackLibrary. As far as i know, geebeer2 is doing a F5E dcsbios too. Talk with him, just in case you two are doing the same work!

Well, this look easy to do, you only need to modify your monitor configuration file and make bigger viewports. Then move the button to the correct place, remove the background on the profile, and thats all.

Well. looks like the next one is the Harrier ! Lets start working on it! ..

.. In case you want/need to control the Garmin NS430 across DCS-Bios, i created the lines you need to add to your DCS-bios airplane file. Using those lines in the MI-8 DCS-bios file, i managed to implement the Garmin controls using DCSFlightpanels. How to add the lines: As always, first, make a backup copy of your files, just in case! Look for the airplane file you want to add the Garmin controls in: Saved Games\DCS.openbeta\scripts\DCS-BIOS\lib Copy those lines at the end of the DCS-bios airplane file, but just before the line: BIOS.protocol.endModule() This one need to be the last one! Save the file and run DCS, and start a mision. The Json file is created automatically. Now you can acces to the new NS430 commands in your favorite tool. the lines: --NS430 added by Capt Zeen------------------------------------------------------------------------------ definePushButton("NS430_PWR-VOL_PUSH-SQ_POW", 257, 3001, 1, "NS430", "PWR-VOL_PUSH-SQ COM Power") defineRotary("NS430_PWR-VOL_PUSH-SQ_VOL", 257, 3002, 0, "NS430", "PWR-VOL_PUSH-SQ COM Volume") definePushButton("NS430_VOL_PUSH-ID_PUSH", 257, 3004, 3, "NS430", "VOL_PUSH-ID VLOC Push") defineRotary("NS430_VOL_PUSH-ID_VOL", 257, 3005, 2, "NS430", "VOL_PUSH-ID VLOC volume") defineRotary("NS430_BIG_LEFT_BTN", 257, 3007, 4, "NS430", "NS430_BIG_LEFT_BTN") definePushButton("NS430_SMALL_LEFT_BTN_PUSH", 257, 3009, 5, "NS430", "SMALL_LEFT_BTN Push") defineRotary("NS430_SMALL_LEFT_BTN_ROT", 257, 3010, 6, "NS430", "SMALL_LEFT_BTN rotate") definePushButton("NS430_COM_FLIP_FLOP", 257, 3012, 7, "NS430", "COM flip-flop") definePushButton("NS430_VLOC_FLIP_FLOP", 257, 3013, 8, "NS430", "VLOC flip-flop") definePushButton("NS430_CDI", 257, 3014, 9, "NS430", "CDI") definePushButton("NS430_OBS", 257, 3015, 10, "NS430", "OBS") definePushButton("NS430_MSG", 257, 3016, 11, "NS430", "MSG") definePushButton("NS430_FPL", 257, 3017, 12, "NS430", "FPL") definePushButton("NS430_PROC", 257, 3018, 13, "NS430", "PROC") definePushButton("NS430_RNG-UP", 257, 3019, 14, "NS430", "RNG-UP") definePushButton("NS430_RNG-DOWN", 257, 3020, 14, "NS430", "RNG-DOWN") definePushButton("NS430_DIRECT-TO", 257, 3021, 15, "NS430", "DIRECT-TO") definePushButton("NS430_MENU", 257, 3022, 16, "NS430", "MENU") definePushButton("NS430_CLR", 257, 3023, 17, "NS430", "CLR") definePushButton("NS430_ENT", 257, 3024, 18, "NS430", "ENT") defineRotary("NS430_BIG_RIGHT_BTN", 257, 3025, 19, "NS430", "BIG_RIGHT_BTN") definePushButton("NS430_SMALL_RIGHT_BTN_PUSH", 257, 3027, 20, "NS430", "SMALL_RIGHT_BTN Push") defineRotary("NS430_SMALL_RIGHT_BTN_ROT", 257, 3028, 21, "NS430", "SMALL_RIGHT_BTN rotate") definePushButton("NS430_PWR-VOL_PUSH-SQ_POW_STOP_ACTION", 257, 3030, 1, "NS430", "PWR-VOL_PUSH-SQ COM Power stop action command") definePushButton("NS430_VOL_PUSH-ID_PUSH_STOP_ACTION", 257, 3031, 3, "NS430", "VOL_PUSH-ID VLOC Push stop action command") definePushButton("NS430_SMALL_LEFT_BTN_PUSH_STOP_ACTION", 257, 3032, 5, "NS430", "SMALL_LEFT_BTN Push stop action command") definePushButton("NS430_COM_FLIP_FLOP_STOP_ACTION", 257, 3033, 7, "NS430", "COM flip-flop stop action command") definePushButton("NS430_VLOC_FLIP_FLOP_STOP_ACTION", 257, 3034, 8, "NS430", "VLOC flip-flop stop action command") definePushButton("NS430_CDI_STOP_ACTION", 257, 3035, 9, "NS430", "CDI stop action command") definePushButton("NS430_OBS_STOP_ACTION", 257, 3036, 10, "NS430", "OBS stop action command") definePushButton("NS430_MSG_STOP_ACTION", 257, 3037, 11, "NS430", "MSG stop action command") definePushButton("NS430_FPL_STOP_ACTION", 257, 3038, 12, "NS430", "FPL stop action command") definePushButton("NS430_PROC_STOP_ACTION", 257, 3039, 13, "NS430", "PROC stop action command") definePushButton("NS430_RNG-UP_STOP_ACTION", 257, 3040, 14, "NS430", "RNG-UP stop action command") definePushButton("NS430_RNG-DOWN_STOP_ACTION", 257, 3041, 14, "NS430", "RNG-DOWN stop action command") definePushButton("NS430_DIRECT-TO_STOP_ACTION", 257, 3042, 15, "NS430", "DIRECT-TO stop action command") definePushButton("NS430_MENU_STOP_ACTION", 257, 3043, 16, "NS430", "MENU stop action command") definePushButton("NS430_CLR_STOP_ACTION", 257, 3044, 17, "NS430", "CLR stop action command") definePushButton("NS430_ENT_STOP_ACTION", 257, 3045, 18, "NS430", "ENT stop action command") definePushButton("NS430_SMALL_RIGHT_BTN_PUSH_STOP_ACTION", 257, 3046, 20, "NS430", "SMALL_RIGHT_BTN Push stop action command") -- end of NS430 added by Capt Zeen---------------------------------------------------------------------- Hope you like it, and let me know how it goes ! ..

ED changed the AMPCD_init.lua and now it contains the proper lines to export the viewport. Also asigned the name "CENTER_MFCD" to that viewport. So probably you need to change the that name on your monitor config file.

I actuallized the UPDATE 2 with the new changes on the config files, for the AMPCD, So the web package is up to date with all changes and improvements. Do not overwrite your monitor config file! use yours, simple change the name of the "F18_AMPCD" to "CENTER_MFCD"

OK... ED added ( 08/29/2018 ) the lines to export the AMPCD in his code, so we don't need anymore my extra lines. And they asigned the name "CENTER_MFCD" for that viewport. Soooo.....You can use the actual ED code instead my code for the AMPCD ( we still need it for the IFEI, RWR and UFC ) If you use JSGME or other mod manager, delete the folder "Multipurpose_Display_Group" from Monitor configuration\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group in your mod manager files and activate it again. And change the name of the viewport in your configuration file! replace "F18_AMPCD" by "CENTER_MFCD" ..