Helios 1.4 - Taking to the Skys Once Again

[Super Sloth Six]

Ok, I am completely clueless here. I am new to all of this including DCS. I have downloaded the latest Helios, watched the youtube videos, read the forum, and readme files. I cannot find a profile for the A-10 that I can download. The file for CapLoz on Gadroc is broken, which I found out why on that. So I went to Capt Zeen can"t find the A-10 profile there. Can someone please post this file or a working link to download this profile. I am completely lost.

 

 

 

Thanks in advance

 

SS6

[jander]

I found a way around on gardoc site that works for me anyways. If u look at the download link it takes u too that gives you error page, at the end of the long url is the actual url to the file. It worked for me anyways grabbing some stuff to just delete everything but that ending part to the url. At work at moment but once I get home tonight i will put all that i have up on my one drive and perm share here.

 

Sent from my SM-G955U using Tapatalk

[Snacko]

Ok, I am completely clueless here. I am new to all of this including DCS. I have downloaded the latest Helios, watched the youtube videos, read the forum, and readme files. I cannot find a profile for the A-10 that I can download. The file for CapLoz on Gadroc is broken, which I found out why on that. So I went to Capt Zeen can"t find the A-10 profile there. Can someone please post this file or a working link to download this profile. I am completely lost.

 

Thanks in advance

 

SS6

 

Attached is Loz A10c profile. I had to break it into 2 uploads because the DCS forums have a 9.77mb limit per file. Just combine these two zip files and you have the entire profile. :thumbup:

 

Snack

Loz SM v2.1 - Part 1.rar

Loz SM v2.1 - Part 2 (more images).rar

[Super Sloth Six]

Attached is Loz A10c profile. I had to break it into 2 uploads because the DCS forums have a 9.77mb limit per file. Just combine these two zip files and you have the entire profile. :thumbup:

 

Snack

 

 

Thank you! Now just to resize every thing to 1920x1080. do you have any idea how to move the MFD screen to Secondary monitor, My main monitor is 2560x1080 and I cant get the MFD to show on my 1920x1080. I have moved them all around and no luck.

 

 

SS6

[AKJAW]

I did the update this week 01-16-2019 on DCS 2.5.4.26368 and the Helios 1.4 Now all my MFCD's map looks like squares dots.

hope someone might have a fix for this my flying buddy has the same on his MFCD's

[ron533]

Hi,

 

I'm trying to bind FLAPS to Helios A-10C Profile by LOZ , butt does not succeed.

In his original profile he had no bind for Flaps.

Trying to bind "trigger value" I get a warning that 'Action value cannot be convert from trigger value'.

Can anyone support please? I have no clue what to do...just playing with it and failing...

Thanks!

[Fakum]

The only thing I can do to help you is to send you my profile to dissect or use. I have not used it in a couple of years and its the original version of Helios.

 

 

Fakums A-10C Rev 8.zip

[ron533]

The only thing I can do to help you is to send you my profile to dissect or use. I have not used it in a couple of years and its the original version of Helios.

 

 

[ATTACH]204889[/ATTACH]

Thank you Fakum!

I see the flaps are not configured in your profile as well, and has the same warning I get.

Still can't resolve this myself.

[Fakum]

hmmm........ I havnt used it in so long

[Nagilem]

First let me say thank you to the devs for putting this out there. I am excited to see this work! As someone who works in IT, I wanted to share some thoughts on my experience and what did and didn't work. This isn't to be critical, but rather to provide some feedback. Hopefully it makes sense and helps. This is one of by first posts here, so please bare with me.

 

I've been trying this for over a week now and cannot get the F/A-18 Capt Zeen profile to work. The issue for me is that none of the gauges, switches, or views work. Even the Freq, About, and Nav panels never pop up. I was able to get the viewports working perfectly, so I can see the right and left MFD, UFC, IFEI, RWR and AMPCD.

 

After lots of reading :book:, hitting Youtube, and and a few late nights, I figured out generally how things work in Helios. I tried multiple configurations of export.lua files and have never gotten the data exchange between Helios and DCS to work in 1.4 for the F18.

 

I finally decided (after reading post after post here about export.lua problems) to verify the rest of my configuration. I downloaded the previous version of Gadrocs Helios 1.3 from Capt Zeen's site. I verified the export.lua files were the latest versions from Capt Zeens site. I fired it up and EVERYTHING worked AS EXPECTED.

 

For kicks I also went back to 1.4 and tried to just do some basics (remove Capt Zeen profile and setup one with some basic gauges and such). I started with a fresh Helios profile, setup new interfaces (using the included F18 interface) to what is included in Helios 1.4, updated the export.lua from Helios 1.4, and used the toolbox components inside Helios for the F-18. I re-verified everything! After some tinkering, I found *I could* get buttons and switches working (master arm on touch screen would switch, in game MA would switch, AND DCS would register the MA state change), but the export.lua would NOT exchange data with DCS for any of the flight instruments such as ADI, Altimeter, etc.

 

So - to recap

- Used 1.4 with Capt Zeen FA18 profile - viewports work, but no gauges, switches, or panel

views work with touch or mouse

- Used 1.3 with same configuration - Everything works as expected

- Tried creating new profile with all 1.4 generated interfaces and export.lua - no data exchange

using 1.4 F18 export.lua.

 

I have:

See below for Specs on computer

3440x1440 Primary Monitor

1920x1080 Secondary Monitor - touch screen

Windows 10 Home

Latest software from Gighub and Capt Zeen website for Helios and F18 pit.

VIACOM Pro - disabled for testing

 

If you are a new user trying this, I would try 1.3 FIRST. You can download it from Capt Zeen's site.

Edited February 23, 2019 by Nagilem

[sobe]

Nagilem

 

 

I have been using Helios and Capt Z's profiles for several years with the original Helios. When problems occurred, it was generally user error. When the F18 profile came out with the new Helios, I went with that and have no issues with either the 1.4 helios or the F18 profile. I have a system somewhat similar to yours so I am wondering why you had so much trouble.

 

While your primary monitor is larger than mine, all else is about the same. One thing you might consider is changing how windows views your screens. In my case, while I have my primary monitor on top and my touch screen on the bottom, for windows purposes, they are treated as side by side with the touchscreen on the right.

 

Another issue that I had is that windows numbering of the monitors does not appear to be the same as the internal numbering of the monitors based on what graphics ports are being used. However, since you got everything to work in 1.3, I have no understanding of why it is not working in 1.4.

 

Keep us posted.

[Nagilem]

Hi Sobe - Thanks.

 

I went back and checked everything again. Right now I have the setup you described (second monitor low). I tried the touchscreen on the right at first, but now that I have a simpit, I have them vertically with no issues on 1.3. All buttons, gauges and other panel views working flawlessly.

 

I made sure when I started that my big monitor was always seen as number 1. I also did all of the touch screen calibration, so no issues there.

 

What I find interesting is with 1.4, I never was able to even get the panel views to work using the export.lua AS IS from the Captain. So if I fired up control center, start the profile, I got the requisite front panel view on my second monitor -:thumbup:. Then if I tried to access any other panel (about, freq, nav, aux, etc.), the button would get the green line under it showing that panel should be active, but no panel appeared.

 

It works as advertised when I use 1.3.

 

Some other points -

I tried running the control center as Administrator - no change

I also removed any other software from the export.lua - I have ViacommPro

I can see all of the panels in Profile Editor, and I can also see the A10 inputs and outputs on bindings

 

As I said before, I could not get a clean singular profile with the default F18 interface and export.lua to exchange data with DCS for any instruments I tried. Switches - yes. Instruments - no joy.

 

I do have my documents on another drive than C:\users. My docs is on D: with Saved games on C: Again no issue with 1.3.

This is a new box for me so Windows 10 hasn't been activated yet. I can't imagine this would cause this issue, but will test sometime later this week.

 

Glad it works for you. I'll keep digging around after the next update. This is new for me so I want to spend more time flying and less time configuring :smilewink:

Edited February 23, 2019 by Nagilem

[sobe]

My export file just to double check:

 

 

local lfs=require('lfs');

dofile(lfs.writedir()..'Scripts\\Helios\\HeliosExport.lua')

 

local dcsSr=require('lfs');

dofile(dcsSr.writedir()..[[scripts\DCS-SimpleRadioStandalone.lua]])

 

 

-- VAICOM PRO server-side script

-- Export.lua (append)

-- version 2.5.3

-- do not edit next line:

-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

 

local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]])

local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

[Nagilem]

@Sobe - Thanks for that. Mine looks identical for the lines setting up helios and for Viacom pro.

 

I have yet to setup a tacview or SRS, though they are coming once I get my HOTAS working the way I want. That looks to be a few more hours of messing with code :doh:.

 

Ah well, its only time... and I guess I am learning *something*… :megalol:

[_Lion_]

Hi guys,

I have a question, I downloaded BLUEFINS Harrier profile and there is a IRIS Folder; I don’t know where I have to put it.

Thanks in advance

Lion

[BluFinBima]

Helios 1.4.2019.0317 is now up on https://www.digitalcombatsimulator.com/en/files/3302014/ .

It contains few external changes but there are internal changes that have allowed things like the Hornet IFEI and UFC to become available.

[BluFinBima]

About Helios Exports.lua

 

Having read through some of the posts here, I thought that I would make a general comment on the subject of Exports.lua.

 

Firstly, it has to be said that this whole area is a bit of a mess, and it does not look likely that this will change (possibly ever). The problem is that Exports.lua is really the only way to get data into and out of DCS so lots of people try to use it. This is possible, however the world as it currently exists, is a free for all, and there is no architected way for multiple exports.lua to play nicely with each other. This is not a criticism of anyone's approach, just a statement of reality as I see it.

 

Helios is no better than anyone else in this regard. It's interface design presumed that it could be king of the exports.lua heap, and this causes certain problems. The good CaptZeen had to work around limitations in the Helios code and he did this in part by pushing lots of extra code into the Exports.lua and also pushing code into the profile itself. His profiles are fantastic given all of the many limitations that he had to find solutions for. Sometimes Exports.lua creators created large exports to cope with many different aircraft, and again, there are some awesome results out there.

 

Meanwhile, Helios remained solidly in the camp of 1 exports.lua for each Helios interface, and if you have two profiles which use different interfaces, then the Helios way of doing it is to change the whole exports.lua.

 

This situation desperately needs to improve, however any change in this area *will* certainly break things that are currently working. I have a preferred solution, but this only works for me because I have relatively simple needs.

 

When you throw into the mix that (as an example) two different implementations of a Hornet profile can have subtly different command codes and values, then the complications increase still further.

 

So all this is a long way of saying that I understand a lot of the reasons why people have so many problems with the exports.lua, but this area is unlikely to improve significantly in the near future. For the time being, if you want to use a Helios interface, then the best starting point is to deploy the Exports.lua for that interface from within Profile Explorer. and then if a particular profile has extra needs from the exports.lua, read the instructions for that profile and change the exports.lua as directed.

[sobe]

Problem. When I go to install your 2019 version over my 2018 version (the last one), I get an error message: Unable to install because a newer version of this product is already installed. This is not true. Why is the computer lying to me???? I also tried to install it in a different folder, but got the same error message.

Edited March 18, 2019 by sobe

[BluFinBima]

Hi Sobe. You are correct. If you read the welcome text in the installer, it explains that because we've changed the format of the installer, (hopefully) for this time only, you will have to go to Add/Remove programs and perform an uninstall.

Cheers, Neil

[sobe]

OK. Uninstalled and reinstalled and all is fine.

 

 

 

Could someone please expand on the following highlighted language found in the new change log:

* Hornet UFC updated to remove the need for a viewport

* Hornet IFEI updated to remove the need for a viewport

* Auto-binding for some devices to their intended interface

[BluFinBima]

Hi Sobe,

This describes these items

 

With a full (well almost) featured IFEI and UFC, there is no need to do the expensive exporting of the IFEI and UFC images.

 

* Hornet UFC updated to remove the need for a viewport

* Hornet IFEI updated to remove the need for a viewport

* Auto-binding for some devices to their intended interface

Edited March 19, 2019 by BluFinBima

[ShadowVonChadwick]

Hi

 

I'm new to Helios and encountered a "Control Center has stopped working" (App crash CLR20r3) apon trying to start the Control Center.

 

Editor seems to work without any apparent problem, and I have created a simple profile with it.

 

Is there any known issues with a clean Win 7 (SP1 only)

 

 

Thanks

[BluFinBima]

Hi

 

I'm new to Helios and encountered a "Control Center has stopped working" (App crash CLR20r3) apon trying to start the Control Center.

 

Editor seems to work without any apparent problem, and I have created a simple profile with it.

 

Is there any known issues with a clean Win 7 (SP1 only)

 

 

Thanks

Hi ShadowVonChadwick,

 

Short answer is no. CLR20r3 is a very generic error saying that it crashed. Try running helios as follows:

 

from a windows command prompt, type:

cd %programfiles%

cd "Gadrocs Workshop\Helios"

"Control Center.exe" -l debug

 

Then see if there are any errors documented in %userprofile%\documents\helios\ControlCenter.log

[ShadowVonChadwick]

I couldn't see any errors

 

 

And Event Viewer is not helpful either.

[BluFinBima]

I couldn't see any errors

 

 

And Event Viewer is not helpful either.

I dug out a Windows 7 machine and I'm seeing a CLR20R3 Sig 9 is System.Windows.Markup.XamlParse. Unfortunately I do not have the ability to debug on that machine.

My initial suggestion is to install latest .net framework from Microsoft and see if that changes the symptoms. Please let me know how you get on.