BluFinBima

A hybrid approach would work well here, the artwork from CZ's profile is very good, and using composite components from Helios (such as the IFEI and UFC) should give a good result. Thanks for sharing the photo.

My profiles generally are not compatible with profiles from CaptZeen because of the export.lua structure used in these profiles. We're looking into harmonizing the export.lua, but it is not there yet. Currently Helios does not manage multiple export.lua files very well. Sorry. Cheers, Blue

Apologies for the slow reply. I've been moving house. The latest AV-8B profile is at https://github.com/BlueFinBima/DCS-AV-8B-NA-Profile. This one requires the latest version of Helios and is not backwards compatible with the previous profile. It also does not have feature parity, although it removes the need to create viewports for some of the instruments which should save some cycles. Cheers Blue

Oops I didn't realise that the changes made broke the older profile so catastrophically. Sorry about that.:music_whistling: https://github.com/BlueFinBima/DCS-AV-8B-NA-Profile/blob/master/Profiles/AV-8B.hpf is the best I can do with the older profile. I've quickly cobbled together a new style profile which is here https://github.com/BlueFinBima/DCS-AV-8B-NA-Profile/blob/master/Profiles/AV8BNAv3.hpf You MUST take the following actions!!!!!!!!! Notes: you must have 1.4.2019.1005 for the latter profile, and the positions of the MFD's have moved a little. No other viewport exports are necessary with AV8BNAv3.hpf. Finally, you will also have to press the "Setup DCS AV-8B" which is on the AV-8B Interface tab in "Profile Editor". Once again, sorry for causing grief, but it is all in the name of "progress".

1.4.2019.0930 Released Just uploaded 1.4.2019.0930 which is mostly AV-8B and M2000C focused. Cheers,

Updates to the AV-8B Artefacts in 1.4.2019.0930 A few more breaking changes in the latest release of Helios (sorry), but all of the updates should be autobinding which means that as long as the AV-8B interface has be loaded in Profile Editor, the new parts of the AV-8B should automatically hook into the interface. There is also a Front Cockpit device which is much of the cockpit in a single chunk. Interested in any feedback Harrier drivers might care to provide. Cheers, BlueFinBima

Firstly Helios 1.4.2019.0908 includes some changes to AV-8B artefacts, and all of the changes autobind to the interface which means that if you add the interface, when you drag a component eg UFC into the Profile Editor monitor, it should bind everything that is needed to the interface. If you're missing images in your AV-8B profile, then this is likley because I have moved them into Helios resources. So if you have images that are in the form {Helios}/Images/AV-8B/xxx.png then the images should be able to be found in {AV-8B}/Images/xxx.png. This release also removes the need to have viewports defined for the ODU and UFC. Cheers, BlueFinBima

Hi Red Dog, the Helios native interface gives you the UFC and the IFEI without the need for exporting viewports.

Hi Bones, several ways of doing this, but I'd usually take a Panels->Generic Bezel, and change the background image and remove the border. Then set the layout size and width to that of the png.

Looking stunning CZ. Can't wait to give this a go!

Thanks for the feedback. I'm glad we got there in the end! These changes will be in the next level of Helios to be made public.

Hi ohc, forget this request, I think I see what you mean by "mess".

Hi ohc, I've emailed you with a possible fix for this problem. Let me know how you get on. It worked for me when I went Japanese :-) Cheers,

OHC, thanks for the offer to help. The problem is my mis-use of characters with codes >127, and the way they get mapped to the default character encoding on your machine. I took a few short-cuts in development that appeared to work for me, but clearly they are problematic for you. I guess that if you were to set up your machine purely as English, then it might work for you, but that is a bad answer and I do not recommend that you do this. I'll certainly come back to you once I have worked out a potential fix because I want to make sure that the character encoding and glyph selection work for you without you needing to make any changes to your machine. Cheers, Neil

I'm not sure what you can do apart from waiting for me to understand what needs done here and get it fixed. I don't want to require people to change the language to English, I'd rather it just worked.

Hi ohc, you're absolutely correct. This is very similar to https://github.com/BlueFinBima/Helios/issues/138 . The coordinates might be something slightly different. What region was Windows in originally? Cheers,

You're correct, it is certainly a mapping problem. Below is the code from the hornet's export.lua which does the mapping and I suspect that it has been deleted or altered somehow. -- getting the UFC data local li = parse_indication(6) -- 6 for UFC if li then --SendData("2098", string.format("%s",li)) local function UFCSendData(UFCcode, UFCvalue) -- This is a 16 segment display so we need to map numerals to a single charcter in the Hornet UFC.ttf font -- the dash has already been catered for and the alphabetic characters should map without change -- Also need to special case 12 because sending ascii 172 is problematic in the Helios code local UFCnum = tonumber(UFCvalue) if UFCnum ~= nil then if UFCnum >= 0 and UFCnum <= 20 then if UFCnum == 12 then UFCvalue = string.char(125) else UFCvalue = string.char(161+UFCnum) end else -- Number Out of Bounds Error end end SendData(UFCcode,string.format("%1s",UFCvalue)) end SendData("2080", string.format("%s",check(li.UFC_MainDummy))) SendData("2081", string.format("%s",check(li.UFC_mask))) SendData("2082", string.format("%s",check(li.UFC_OptionDisplay1))) -- These may need special treatment for Hornet_UFC_Unified.ttf if there are special chars or numbers in the data SendData("2083", string.format("%s",check(li.UFC_OptionDisplay2))) -- These may need special treatment for Hornet_UFC_Unified.ttf if there are special chars or numbers in the data SendData("2084", string.format("%s",check(li.UFC_OptionDisplay3))) -- These may need special treatment for Hornet_UFC_Unified.ttf if there are special chars or numbers in the data SendData("2085", string.format("%s",check(li.UFC_OptionDisplay4))) -- These may need special treatment for Hornet_UFC_Unified.ttf if there are special chars or numbers in the data SendData("2086", string.format("%s",check(li.UFC_OptionDisplay5))) -- These may need special treatment for Hornet_UFC_Unified.ttf if there are special chars or numbers in the data SendData("2087", string.format("%1s",check(li.UFC_OptionCueing1)):gsub(":",string.char(200))) -- 16 Segment two-dot colon in Hornet_UFC_Unified.ttf SendData("2088", string.format("%1s",check(li.UFC_OptionCueing2)):gsub(":",string.char(200))) -- 16 Segment two-dot colon in Hornet_UFC_Unified.ttf SendData("2089", string.format("%1s",check(li.UFC_OptionCueing3)):gsub(":",string.char(200))) -- 16 Segment two-dot colon in Hornet_UFC_Unified.ttf SendData("2090", string.format("%1s",check(li.UFC_OptionCueing4)):gsub(":",string.char(200))) -- 16 Segment two-dot colon in Hornet_UFC_Unified.ttf SendData("2091", string.format("%1s",check(li.UFC_OptionCueing5)):gsub(":",string.char(200))) -- 16 Segment two-dot colon in Hornet_UFC_Unified.ttf UFCSendData("2092", string.format("%2s",check(li.UFC_ScratchPadString1Display)):gsub("_",string.char(201)):gsub("`","1"):gsub("~","2"):gsub(" ","")) UFCSendData("2093", string.format("%2s",check(li.UFC_ScratchPadString2Display)):gsub("_",string.char(201)):gsub("`","1"):gsub("~","2"):gsub(" ","")) SendData("2094", string.format("%7s",check(li.UFC_ScratchPadNumberDisplay)):gsub(" ","<")) UFCSendData("2095", string.format("%2s",check(li.UFC_Comm1Display)):gsub("`","1"):gsub("~","2"):gsub(" ","")) UFCSendData("2096", string.format("%2s",check(li.UFC_Comm2Display)):gsub("`","1"):gsub("~","2"):gsub(" ","")) -- test command 00000000*2095=~:2093=É:2092=~:2096=~:2094=8888888:2082=~~~~:2083=~~~~:2084=~~~~:2085=~~~~:2086=~~~~:2087=È:2088=È:2089=È:2090=È:2091=È end

I was hoping to avoid running the options.lua, so still hoping someone will come up with a better answer, but I've temporarily gone for log.write('USERMOD',log.INFO," Loading options from - " .. lfs.writedir() .. "config\\options.lua") dofile(lfs.writedir() .. "config\\options.lua") gDCS_VR = options.VR.enable log.write('USERMOD',log.INFO," VR option = " .. tostring(options.VR.enable))

Hi, Hope someone can point me in the right direction. I've dumped _G without any obvious candidates. I'm trying to find out if VR is enabled from within DCS so that I can automatically disable my FTNoIR module. It's obviously defined in options.lua, but I don't know how to expose it. Thanks in advance.

Hi Mike, It looks like you're using Capt Zeen's profile, not the one from Helios. Try changing dofile("C:\Users\mmaxw\Saved Games\DCS\Scripts\Helios") to lfs=require('lfs');dofile(lfs.writedir()..'Scripts\\Helios\\HeliosExport.lua') Cheers

Hi Mike, yes Olaf has reached out to me, but with so little information about the actual problem, it is difficult to offer assistance. The first question is which exports.lua are you trying to run... the one deployed from Helios Profile Editor, or Capt Zeen's site (or somewhere else). Whichever path you took, you will need to call the SimShaker lua code by making a change to the export.lua that you are using to talk to Helios. It would also be helpful to know what your symptoms are... ie specifically what is not working. You might also look in dcs.log to see if there are any errors in there from the export.lua. Cheere

UK HP Rep said that they won't be stocking the consumer unit - only the pro - and they have a large number of corporate orders depleting their expected stock delivery. No idea how accurate this info is, but I thought I'd share what I was told.

Hi Rightstuff, Having read the linked documentation, if I was to implement something with a Pokeys for myself, I'd use the E models, not the U and hook it directly into an extension to the export.lua and not use Helios. I do something like this for my Hornet UFC https://github.com/BlueFinBima/DCS-FA18C-UFC/raw/gh-pages/images/ufc2A.JPG except it uses wi-fi and not ethernet. Having Pokeys support in Helios might be an interesting technical challenge, but I don't have one to play with and I would not embark on something like this without the ability to test. If you're interested in giving it a go, then happy to have another contributor on the project. Cheers,

Gabgio, Even more confusingly, HP Germany does not show a picture of the Reverb against the VR1000-200nn https://store.hp.com/GermanyStore/Merch/Product.aspx?id=2CZ77EA&opt=ABB&sel=ACC I presume that the photograph is the earlier version.

1.4.2019.0616 is now available with the new Phidgets. I can't see any reason why you can't take gauge artwork from a profile using one interface and bind it against a different interface. There may be extra work if Capt Zeen has put extra Lua logic in the profile to support the gauge, but I can't see why with a bit of ingenuity, you could not achieve what you want. Cheers