BluFinBima

Hi PSYKOnz, until we revise the release numbering system again, you will have to manually remove the previous Helios via "Add or Remove Programs" before installing the new one.

It has been a little time since we released a version of Helios for Windows 32 bit, however with 1.4.2020.0530 you have the opportunity once again to run Helios on lower function machines. There is also the usual 64 bit version. For this release, most of the functionality is actually focused on Falcon BMS but there are also some bug fixes. The team also wanted to make a single download site for distributions of Helios, and that sire is Github where Helios is developed. This means that the file while is downloaded from the DCS "user files" site is simply a link to the actual file on Github. Finally, for those who are running a modern release of Helios which contains new release checking, you might see a pop-up offering you the ability to download the latest version directly. Some browsers will throw up a warning about the file, and it is obviously your choice as to whether you proceed, however if the file is downloaded from our Github releases, then I believe this should be the genuine article, and there are checksums on the site for you to validate an unaltered zip file.

@j9murphy, probably better to use an arduino pro micro or other board with an atmega32u4. Plenty examples of using this as a standard game controller and you'd be able to use x and y axis for the knob travel and I even found this https://www.youtube.com/watch?v=RYMYF_zXgu4. I agree with derammo that the interaction style would be nice to have in Helios.

@PSYKOnz, I'm only aware of the items produced by the good Captain Z.

Resizing F-14 Profile Hi @PSYKOnz, Thanks for your positive comments. The answer to your high level question is yes, it is possible to make panels within a profile smaller / bigger. If you group the items and hold the shift key while resizing, you should be able to retain the correct aspect ratio. Particular gauges / controls can be deleted with the delete key. However.... resizing the background image is probably best done outside of Helios, and certain controls are likely to be on panels or sub panels, some of the controls you'll want and some you won't, which will also possibly require some careful attention. So care will be required. I would suggest that you practise on a profile which is less complex than Captain Zeen's F14 profile. Cheers BlueFin

@sobe you may have clicked the exe.... There was a problem with the tags on GitHub (now fixed) which would have resulted in something similar to what you described.

Hi Sobe, if you installed via the "Helios Setup.exe" program, the Visual C++ runtime should have been installed. Did this not happen?

@jayyang - https://github.com/BlueFinBima/Helios/issues/185 opened for this

Issues with the AV8BV3 @daddio007 apologies for not spotting this post until now. I have not used the Harrier profile for some time, but I'm glad that you're liking it, and that you were able to solve the problems you encountered. For bindings that are duplicated, this is likely to be a bug that I have seen on occasion and I'm hoping that we'll have a fix coming out in the next level of Helios.

Les, hope you have a great holiday!

Problem opening CZ profiles in 1.4.2019.1005 Not that I am aware of. Do you see the problem opening a CZ profile which you've just downloaded from his site (without changes)? If so, which one?

I actually use my own exports scripts (not Helios or from another source) but I'm pretty sure the ODU and UFC codes are correct. Chances are that if nothing is flowing over the socket, then my first guess would be that an error was thrown and the exports stopped.

How embarrassing... I did write the code for the Harrier. I completely forgot. But I didn't publish the exports. This is the ProcessLowImportance function from the exports: function ProcessLowImportance(mainPanelDevice) --local ii --for ii = 1,16,1 do -- li = parse_indication(ii) -- if li ~= nil then -- Helios.log.write(thisScript,string.format("%s %1.0f ", "Dump ", ii) .. Heliosdump(li)) -- end --end li = parse_indication(5) if li then if scriptDebug > 0 then Helios.log.write(thisScript,string.format("UFC Dump " .. Heliosdump(li))) Helios.log.write(thisScript,string.format("UFC Comm 1: " .. check(li.ufc_chnl_1_m) .. check(li.ufc_chnl_1_v))) end SendData("2092", string.format("%2s",check(li.ufc_left_position))) SendData("2094", string.format("%7s",check(li.ufc_right_position))) SendData("2095", string.format("%2s",check(li.ufc_chnl_1_m) .. check(li.ufc_chnl_1_v))) SendData("2096", string.format("%2s",check(li.ufc_chnl_2_m) .. check(li.ufc_chnl_2_v))) --[ufc_left_position] string: "ON" --[ufc_right_position] = string: "16" end local li = parse_indication(6) if li then if scriptDebug > 0 then Helios.log.write(thisScript,string.format("ODU Dump " .. Heliosdump(li))) Helios.log.write(thisScript,string.format("ODU 5 Text: " .. check(li.ODU_Option_5_Text))) end SendData("2082", string.format("%4s",check(li.ODU_Option_1_Text))) SendData("2083", string.format("%4s",check(li.ODU_Option_2_Text))) SendData("2084", string.format("%4s",check(li.ODU_Option_3_Text))) SendData("2085", string.format("%4s",check(li.ODU_Option_4_Text))) SendData("2086", string.format("%4s",check(li.ODU_Option_5_Text))) SendData("2087", string.format("%1s",check(li.ODU_Option_1_Slc)):gsub(":","!")) -- ":" is reserved SendData("2088", string.format("%1s",check(li.ODU_Option_2_Slc)):gsub(":","!")) -- ":" is reserved SendData("2089", string.format("%1s",check(li.ODU_Option_3_Slc)):gsub(":","!")) -- ":" is reserved SendData("2090", string.format("%1s",check(li.ODU_Option_4_Slc)):gsub(":","!")) -- ":" is reserved SendData("2091", string.format("%1s",check(li.ODU_Option_5_Slc)):gsub(":","!")) -- ":" is reserved -- -- test command 00000000*2096=20:2095=13:2087=!:2088=!:2089=!:2090=!:2091=!:2082=BLUE:2083=FIN :2084=BIMA:2085=2019:2086=test:2094=123.567:2092=~0:2093=-:326=1:336=1:197=1:365=1:196=1: end local li = parse_indication(7) --V/UHF Radio and ACNIP if li then if scriptDebug > 0 then Helios.log.write(thisScript,string.format("V/UHF Radio and ACNIP " .. Heliosdump(li))) end --[uVHF_DISPLAY] = string: "" --[uvhf_channel] = string: "01" --[uvhf_freq_left] = string: "177.000" --[acnip_1_label_mode] = string: "MODE" --[acnip_1_mode] = string: "PLN" --[acnip_1_label_code] = string: "CODE" --[acnip_1_code] = string: "00" --[acnip_2_label_mode] = string: "MODE" --[acnip_2_mode] = string: "CY" --[acnip_2_label_code] = string: "CODE" --[acnip_2_code] = string: "03" SendData("2100", string.format("%2s",check(li.uvhf_channel))) SendData("2101", string.format("%7s",check(li.uvhf_freq_left))) SendData("2102", string.format("%s",check(li.acnip_1_label_mode))) SendData("2103", string.format("%s",check(li.acnip_1_mode))) SendData("2104", string.format("%s",check(li.acnip_1_label_code))) SendData("2105", string.format("%s",check(li.acnip_1_code))) SendData("2106", string.format("%s",check(li.acnip_2_label_mode))) SendData("2107", string.format("%s",check(li.acnip_2_mode))) SendData("2108", string.format("%s",check(li.acnip_2_label_code))) SendData("2109", string.format("%s",check(li.acnip_2_code))) end SendData(2001, string.format("%.0f",mainPanelDevice:get_argument_value(253) * 1000+mainPanelDevice:get_argument_value(254) * 100+mainPanelDevice:get_argument_value(255) * 10)) -- Engine Duct SendData(2002, string.format("%.0f",mainPanelDevice:get_argument_value(256) * 10000+mainPanelDevice:get_argument_value(257) * 1000+mainPanelDevice:get_argument_value(258) * 100+mainPanelDevice:get_argument_value(259) * 10)) -- Engine RPM SendData(2003, string.format("%.0f",mainPanelDevice:get_argument_value(260) * 1000+mainPanelDevice:get_argument_value(261) * 100+mainPanelDevice:get_argument_value(262) * 10)) -- Engine FF SendData(2004, string.format("%.0f",mainPanelDevice:get_argument_value(263) * 1000+mainPanelDevice:get_argument_value(264) * 100+mainPanelDevice:get_argument_value(265) * 10)) -- Engine JPT SendData(2005, string.format("%.0f",mainPanelDevice:get_argument_value(267) * 100+mainPanelDevice:get_argument_value(268) * 10)) -- Engine Stab SendData(2006, string.format("%.0f",mainPanelDevice:get_argument_value(269) * 100+mainPanelDevice:get_argument_value(270) * 10)) -- Engine H2O SendData(2019, string.format("%.4f",mainPanelDevice:get_argument_value(386) * 100+mainPanelDevice:get_argument_value(387) * 10)) -- SMC Fuze SendData(2020, string.format("%.0f",mainPanelDevice:get_argument_value(392) * 1000+mainPanelDevice:get_argument_value(393) * 100+mainPanelDevice:get_argument_value(394) * 10)) -- SMC Interval SendData(2022, string.format("%.0f",mainPanelDevice:get_argument_value(389) * 100+mainPanelDevice:get_argument_value(390) * 10)) -- SMC Quantity SendData(2021, string.format("%.0f",mainPanelDevice:get_argument_value(391) * 10)) -- SMC Mult SendData(2010, string.format("%.0f",mainPanelDevice:get_argument_value(367) * 10000+mainPanelDevice:get_argument_value(368) * 1000+mainPanelDevice:get_argument_value(369) * 100+mainPanelDevice:get_argument_value(370) * 10)) -- Fuel Total SendData(2011, string.format("%.0f",mainPanelDevice:get_argument_value(371) * 10000+mainPanelDevice:get_argument_value(372) * 1000+mainPanelDevice:get_argument_value(373) * 100+mainPanelDevice:get_argument_value(374) * 10)) -- Fuel Left Tank SendData(2012, string.format("%.0f",mainPanelDevice:get_argument_value(375) * 10000+mainPanelDevice:get_argument_value(376) * 1000+mainPanelDevice:get_argument_value(377) * 100+mainPanelDevice:get_argument_value(378) * 10)) -- Fuel Right Tank SendData(2013, string.format("%.0f",mainPanelDevice:get_argument_value(381) * 10000+mainPanelDevice:get_argument_value(382) * 1000+mainPanelDevice:get_argument_value(383) * 100+mainPanelDevice:get_argument_value(384) * 10)) -- Fuel Bingo SendData(2014, string.format("%.0f",mainPanelDevice:get_argument_value(455) * 100+mainPanelDevice:get_argument_value(456) * 10)) -- Flap Position SendData(2015, string.format("%.0f",mainPanelDevice:get_argument_value(550) * 1000+mainPanelDevice:get_argument_value(551) * 100+mainPanelDevice:get_argument_value(552) * 10)) -- Pressure Brake SendData(2016, string.format("%.0f",mainPanelDevice:get_argument_value(553) * 1000+mainPanelDevice:get_argument_value(554) * 100+mainPanelDevice:get_argument_value(555) * 10)) -- Pressure Hyd 1 SendData(2017, string.format("%.0f",mainPanelDevice:get_argument_value(556) * 1000+mainPanelDevice:get_argument_value(557) * 100+mainPanelDevice:get_argument_value(558) * 10)) -- Pressure Hyd 2 end

Hi Les, Apart from the MFD's (which are usually already defined), the other viewports need to be defined. for the A-10C , this is in file Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\indicator\AN_ALR69V.lua. If you look in Capt Zeens profile rar, the required file is in "Monitor Configuration\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\indicator" Hope this helps.

AV8B UFC / ODU Text Hi @ShadowDragonCZ, The text for the AV-8B UFC and ODU does not come via Helios. Viewports need to be created for these devices and the exported screens need to sit beneath the Helios profile. See https://github.com/BlueFinBima/DCS-AV-8B-NA-Profile/blob/master/Config/MonitorSetup/AV-8B%20Config.lua and https://github.com/BlueFinBima/DCS-AV-8B-NA-Profile/tree/master/Mods/Aircraft/AV8BNA/Cockpit . The advice provided by @Derammo would be appropriate if the ODU and UFC worked like the Hornet, but I have not yet released versions of that code for the AV-8B. Hope this helps.

Hi Les, that is it precisely.

Hi Les, @JG14_Smil states the situation correctly. The "contents" of the RWR have to be a viewport (ie nothing to do with Helios). Typically when DCS exports a viewport, there is no bezel, so Helios offers the bezel and a transparent area for the exported viewport to be seen through. Is the area inside the bezel transparent? Have you placed the exported viewport correctly underneath the transparent bezel? Typically what I do is take a screen shot with DCS running, but without Helios Control Center to see if the viewport is displayed in the correct position. Hope this helps, BFB

Hi @snacko, I have not seen evidence that DCS exports data that might infer where the SOI is. If the DCS A-10C cockpit does not expose this, then I wouldn't know how to make this available to a Helios profile. If you know of an implementation that has managed to determine the SOI, then I'm happy to explore further. Cheers,

Hi Phil, the opening and closing of the panels is done without the network / export.lua being involved. Contact me on Discord and I'll try to work out what is going on.

Phil, Are you running with the export.lua created by the AV-8B interface in Helios?

Phil, it is possible that the reset monitors is causing the bindings to get lost. https://github.com/BlueFinBima/Helios/issues/117#issuecomment-467985655 might hold a possible circumvention if this is the problem. Obviously the starting point will need to be a profile which still has all of the bindings.

@Spiceman, Currently Helios delivers the lua for every interface as "export.lua". This is one of the idiosyncrasies that needs attention.

Despite the naming, those are not Helios messages. I suspect that they come from Capt Zeen's export.lua. This said, I don't see any errors reported, which is a good thing. There is a problem where reset monitors can lose the bindings in the profile https://github.com/BlueFinBima/Helios/issues/117 and this might have the same symptoms. If you look in the profile's .hpf file, you should see a large number of <binding> tags, so if they are missing, that bug is a possible culprit. Cheers, Blue

@Spiceman, The message probably hints at your problem although it harks back to the days when the Helios export.lua went into the DCS folder rather than the "%userprofile%\Saved Games\DCS Openbeta\Scripts" where it lives today. You'd have to check with CZ to be sure, but I suspect that his F-14B profile does not need the export.lua from the Generic Interface to work *IF* you are using the the Good Captain's export.lua from his website.

@Ron533, I agree with all of your comments. Helios Profile Editor currently uses AvalonDock for it's UI. Nobody in the project has any knowledge of this package, and no time to learn it. It might have the capability to do what you ask already, but if it does not, then we're unlikely to replace the UI layer. Annoying though it is, I think we're all stuck with these usability annoyances, at least in the medium term. Sorry, Blue