Open Source Helios

Is Helios ever going to be updated to include more gauges and inputs from other aircraft? I'd like to build a panel for every aircraft

Unless there is a way to grab information from DCS other than using the aircraft listed in the drop-down.

I will definitely want to be able to build a panel once my F-14 gets here

Hi CBoB, The team is VERY small in size, we have day jobs, and we'd like to fly the fine aircraft in DCS. Unfortunately, this means that what we're able to accomplish is limited. We have delivered a generic interface which should help Capt Zeen (and possibly others) with creating profiles without bespoke aircraft interfaces but using it requires a lot of skill.

1.4.2019.0317 (https://www.digitalcombatsimulator.com/en/files/3302014/) has shipped a complete IFEI and UFC for the Hornet which is demoed here

I cannot foresee a situation where there is an interface for every aircraft in the DCS world. At least 75% of the team has bought the Tomcat - read into that what you will - but whether there is any interface and gauge support in Helios is still being investigated.

Cheers, Neil

Hi BluFinBima,

could you please share you export LUA (HeliosCore.lua & HeliosExport.lua) ? Because I can't use Helios on Hornet even if I fellow the demo video on youtube step by step, add a Hornet interface and add UFC pannel on the screen. The Helio is updated to date. there is neither send nor recv between UFC and DCS world.

I'm sure there is something wrong in the export lua becaues if I add A-10C interface and export A-10C UFC, everything works perfect.

Attach is my export lua

HeliosCore.zip

Hi RglsPhoto,

The attachment you added is Capt Zeen's exports. This does not support the Helios FA-18C interface. It does support the Helios A-10C interface. To get the Helios Hornet UFC working you need to install Helios's exports.lua from the "DCS F/A-18C" interface tab in the Helios profile editor. Pressing the button "Setup DCS F/A-18C" button at the bottom right side of the screen will write the correct export.lua file into the saved games scripts directory. If this works correctly, you will see a pop-up box saying "DCS F/A-18C has been configured".

It is important to note that even though it is called "HeliosCore.zip", it is NOT part of Helios.

The process I describe above will not touch your existing HeliosCore.lua, however the code in that file will no longer be executed. Captain Zeen's export.lua file will be overwritten by this process.

Please note that currently Helios gets a little confused by multiple installations of DCS, and might not write the export.lua to the scripts directory for the DCS installation that you wanted. If you have multiple versions of DCS installed, then have a look in the scripts directories for each DCS installation.

If you have done all of this correctly, then the most probable reason for it not working is a problem with the export.lua script. Have a look in the dcs.log file and see if it is reporting an error with the export.lua script.

If there is an error reported in the dcs.log, please let me know what it is, and I can send you a fix for it.

Please let me know how you get on.

Hi RglsPhoto,

 

The attachment you added is Capt Zeen's exports. This does not support the Helios FA-18C interface. It does support the Helios A-10C interface. To get the Helios Hornet UFC working you need to install Helios's exports.lua from the "DCS F/A-18C" interface tab in the Helios profile editor. Pressing the button "Setup DCS F/A-18C" button at the bottom right side of the screen will write the correct export.lua file into the saved games scripts directory. If this works correctly, you will see a pop-up box saying "DCS F/A-18C has been configured".

 

It is important to note that even though it is called "HeliosCore.zip", it is NOT part of Helios.

The process I describe above will not touch your existing HeliosCore.lua, however the code in that file will no longer be executed. Captain Zeen's export.lua file will be overwritten by this process.

 

Please note that currently Helios gets a little confused by multiple installations of DCS, and might not write the export.lua to the scripts directory for the DCS installation that you wanted. If you have multiple versions of DCS installed, then have a look in the scripts directories for each DCS installation.

 

If you have done all of this correctly, then the most probable reason for it not working is a problem with the export.lua script. Have a look in the dcs.log file and see if it is reporting an error with the export.lua script.

 

If there is an error reported in the dcs.log, please let me know what it is, and I can send you a fix for it.

 

Please let me know how you get on.

Hi BluFinBima,

Thank you so much,

Problem resolved:thumbup:

There is still one issue, some symbols are not displayed correctly, a screenshot and the lua file is attached

export_hornet.lua

Hi RglsPhoto, what locale are you in? I'm wondering if there is some conversion being done on the font on your machine. I'm not an expert in this area... maybe given your forum role description, you might be in a better position than me to work out what might be going on.

As an example, the option cues should be ascii 200 and get mapped to È.

Attached is the font mapping that I'm expecting.

Hornet UFC Mapping.PDF

Hi there - many thanks for your assistance with this excellent add on.

I did this after following Capt Zeens video after an unsuccessful first test:

To get the Helios Hornet UFC working you need to install Helios's exports.lua from the "DCS F/A-18C" interface tab in the Helios profile editor. Pressing the button "Setup DCS F/A-18C" button at the bottom right side of the screen will write the correct export.lua file into the saved games scripts directory. If this works correctly, you will see a pop-up box saying "DCS F/A-18C has been configured".

Now if I try to run the profile in the Helios Control Centre (with either DCS running or not running), then the Helios Control Centre crashes instantly. This didn’t happen prior to following the above quoted section - though DCS was not connecting to Helios either - but at least it didn’t crash and the pretty panels showed up! :)

I’m a super newb at this, would appreciate your recommendation.

More info:

Running Win 10 64

Tried deleting HeliosSettings.xml as per another thread - no joy. Saw something about enabling "Aero" but not sure this is a Win 10 thing - and, it did run the profile originally...

Cheers.

Joe

Some more info - I have uninstalled and reinstalled Helios - no joy - Helios Control Centre continues to now crash whenever I try to run the profile.

Also, if I try to "add interface" in Helios Profile Editor, there is no longer an option for FA18C.

Hi Joe,

the only reason I know of for the Control Center to crash at startup is due to an image that was missed out of the distribution. I'm pretty sure that Helios 1.4.2019.0317 shipped the missing file. What precise release of Helios did you install? (this was an image related to Aero).

If there is no longer an option to add the F/A-18C interface, then it probably means that it is either already installed in the profile you've opened, or you're using an older version of Helios.

If you still see the problem with Helios 1.4.2019.0317, then start control center from the command line with options "-l debug" and attach the ControlCenter.log file created (in the %userprofile%\Documents\Helios directory).

Cheers, BlueFinBima

Some more info - I have uninstalled and reinstalled Helios - no joy - Helios Control Centre continues to now crash whenever I try to run the profile.

Also, if I try to "add interface" in Helios Profile Editor, there is no longer an option for FA18C.

Thanks to both BlueFinBima and Capt Zeen for getting back to me - I'll continue my explorations of Helios in this thread in case it helps other in the future, it's easier to find under the "Open Source Helios" sticky.

I'll respond to BlueFinBima initially:

I have only just dipped my toe into Helios and have only ever installed 1.4.2019.317.

Here's the ControlCenter.log contents:

14/05/2019 1:38:06 PM - All - Helios Version 1.4.2019.317

14/05/2019 1:38:07 PM - Debug - Loading Modules

14/05/2019 1:38:07 PM - Debug - Converter found AreaConverter

14/05/2019 1:38:07 PM - Debug - Converter found DistanceConverter

14/05/2019 1:38:07 PM - Debug - Converter found MassConverter

14/05/2019 1:38:07 PM - Debug - Converter found MassFlowConverter

14/05/2019 1:38:07 PM - Debug - Converter found PressureConverter

14/05/2019 1:38:07 PM - Debug - Converter found RadianToDegreesConverter

14/05/2019 1:38:07 PM - Debug - Converter found SpeedConverter

14/05/2019 1:38:07 PM - Debug - Converter found TimeConverter

14/05/2019 1:38:07 PM - Debug - Interface found ProfileInterface

14/05/2019 1:38:07 PM - Debug - Interface found KeyboardInterface

14/05/2019 1:38:07 PM - Debug - Interface found FalconInterface

14/05/2019 1:38:07 PM - Debug - Control found RWR

14/05/2019 1:38:07 PM - Debug - Control found DED

14/05/2019 1:38:07 PM - Debug - Control found HUD

14/05/2019 1:38:07 PM - Debug - Control found LeftMFD

14/05/2019 1:38:07 PM - Debug - Control found PFL

14/05/2019 1:38:07 PM - Debug - Control found RightMFD

14/05/2019 1:38:07 PM - Debug - Control found RWR

14/05/2019 1:38:07 PM - Debug - Interface found EosDirectSerial

14/05/2019 1:38:07 PM - Debug - Interface found DTSCardInterface

14/05/2019 1:38:07 PM - Debug - Interface found DirectXControllerInterface

14/05/2019 1:38:07 PM - Debug - Interface found MiG21Interface

14/05/2019 1:38:07 PM - Debug - Interface found Mi8SimpleInterface

14/05/2019 1:38:07 PM - Debug - Interface found GenericInterface

14/05/2019 1:38:07 PM - Debug - Interface found FC2Interface

14/05/2019 1:38:07 PM - Debug - Interface found BlackSharkInterface

14/05/2019 1:38:07 PM - Debug - Interface found FA18CInterface

14/05/2019 1:38:07 PM - Debug - Interface found AV8BInterface

14/05/2019 1:38:07 PM - Debug - Interface found A10CInterface

14/05/2019 1:38:07 PM - Debug - Control found Accelerometer

14/05/2019 1:38:07 PM - Debug - Control found IAS

14/05/2019 1:38:07 PM - Debug - Control found TAS

14/05/2019 1:38:07 PM - Debug - Control found FuelGauge

14/05/2019 1:38:07 PM - Debug - Control found AOA

14/05/2019 1:38:07 PM - Debug - Control found DA200

14/05/2019 1:38:07 PM - Debug - Control found KPP

14/05/2019 1:38:07 PM - Debug - Control found NPP

14/05/2019 1:38:07 PM - Debug - Control found EngExhaustTempGauge

14/05/2019 1:38:07 PM - Debug - Control found EngingeRpm

14/05/2019 1:38:07 PM - Debug - Control found RadioAltimeter

14/05/2019 1:38:07 PM - Debug - Control found ARU3VM

14/05/2019 1:38:07 PM - Debug - Control found BarometricAltimeter

14/05/2019 1:38:07 PM - Debug - Control found Nosecone

14/05/2019 1:38:07 PM - Debug - Control found HydroPressure

14/05/2019 1:38:07 PM - Debug - Control found Voltmeter

14/05/2019 1:38:07 PM - Debug - Control found RSBNDistance

14/05/2019 1:38:07 PM - Debug - Control found OilPressure

14/05/2019 1:38:07 PM - Debug - Control found O2Level

14/05/2019 1:38:07 PM - Debug - Control found EngineO2

14/05/2019 1:38:07 PM - Debug - Control found O2Pressure

14/05/2019 1:38:07 PM - Debug - Control found ChannelDisplay

14/05/2019 1:38:07 PM - Debug - Control found BatteryCapacity

14/05/2019 1:38:07 PM - Debug - Control found ADI

14/05/2019 1:38:07 PM - Debug - Control found VVI

14/05/2019 1:38:07 PM - Debug - Control found PitchTrim

14/05/2019 1:38:07 PM - Debug - Control found RollTrim

14/05/2019 1:38:07 PM - Debug - Control found RPM

14/05/2019 1:38:07 PM - Debug - Control found OilPressure

14/05/2019 1:38:07 PM - Debug - Control found Nozzle

14/05/2019 1:38:07 PM - Debug - Control found HSI

14/05/2019 1:38:07 PM - Debug - Control found FuelFlow

14/05/2019 1:38:07 PM - Debug - Control found FTIT

14/05/2019 1:38:07 PM - Debug - Control found AOA

14/05/2019 1:38:07 PM - Debug - Control found Altimeter

14/05/2019 1:38:07 PM - Debug - Control found Airspeed

14/05/2019 1:38:07 PM - Debug - Control found ADI

14/05/2019 1:38:07 PM - Debug - Control found VVI

14/05/2019 1:38:07 PM - Debug - Control found Tachometer

14/05/2019 1:38:07 PM - Debug - Control found RotorRPM

14/05/2019 1:38:07 PM - Debug - Control found RadarAltimeter

14/05/2019 1:38:07 PM - Debug - Control found IAS

14/05/2019 1:38:07 PM - Debug - Control found HSI

14/05/2019 1:38:07 PM - Debug - Control found FuelGauge

14/05/2019 1:38:07 PM - Debug - Control found Clock

14/05/2019 1:38:07 PM - Debug - Control found BladeAngle

14/05/2019 1:38:07 PM - Debug - Control found BarometricAltimeter

14/05/2019 1:38:07 PM - Debug - Control found ADI

14/05/2019 1:38:07 PM - Debug - Control found Accelerometer

14/05/2019 1:38:07 PM - Debug - Control found EGT

14/05/2019 1:38:07 PM - Debug - Control found VVI

14/05/2019 1:38:07 PM - Debug - Control found TISLCodeWheel

14/05/2019 1:38:07 PM - Debug - Control found TACANChannel

14/05/2019 1:38:07 PM - Debug - Control found OxygenPressure

14/05/2019 1:38:07 PM - Debug - Control found OilPressure

14/05/2019 1:38:07 PM - Debug - Control found LiquidOxygen

14/05/2019 1:38:07 PM - Debug - Control found ILSFrequency

14/05/2019 1:38:07 PM - Debug - Control found IAS

14/05/2019 1:38:07 PM - Debug - Control found Hydraulic

14/05/2019 1:38:07 PM - Debug - Control found HSI

14/05/2019 1:38:07 PM - Debug - Property editor found HSIBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Control found HARSSync

14/05/2019 1:38:07 PM - Debug - Control found FuelGauge

14/05/2019 1:38:07 PM - Debug - Control found FuelFlow

14/05/2019 1:38:07 PM - Debug - Control found Flaps

14/05/2019 1:38:07 PM - Debug - Control found FanRPM

14/05/2019 1:38:07 PM - Debug - Control found EngineRPM

14/05/2019 1:38:07 PM - Debug - Control found EngineTemp

14/05/2019 1:38:07 PM - Debug - Control found CabinPressure

14/05/2019 1:38:07 PM - Debug - Control found ApuRPM

14/05/2019 1:38:07 PM - Debug - Control found ApuEGT

14/05/2019 1:38:07 PM - Debug - Control found ADI

14/05/2019 1:38:07 PM - Debug - Control found BackupADI

14/05/2019 1:38:07 PM - Debug - Control found Altimeter

14/05/2019 1:38:07 PM - Debug - Control found AOA

14/05/2019 1:38:07 PM - Debug - Control found Battery

14/05/2019 1:38:07 PM - Debug - Control found BrakePressure

14/05/2019 1:38:07 PM - Debug - Control found cabinPressure

14/05/2019 1:38:07 PM - Debug - Control found IAS

14/05/2019 1:38:07 PM - Debug - Control found IFEI_Gauges

14/05/2019 1:38:07 PM - Debug - Control found UFC_FA18C

14/05/2019 1:38:07 PM - Debug - Control found IFEI_FA18C

14/05/2019 1:38:07 PM - Debug - Control found VVI

14/05/2019 1:38:07 PM - Debug - Control found Hydraulic

14/05/2019 1:38:07 PM - Debug - Control found BAltimeter

14/05/2019 1:38:07 PM - Debug - Control found RAltimeter

14/05/2019 1:38:07 PM - Debug - Control found O2Gauge

14/05/2019 1:38:07 PM - Debug - Control found ADI

14/05/2019 1:38:07 PM - Debug - Control found fuel

14/05/2019 1:38:07 PM - Debug - Control found advisoryPanel

14/05/2019 1:38:07 PM - Debug - Control found ODU_AV8B

14/05/2019 1:38:07 PM - Debug - Control found UFC_AV8B

14/05/2019 1:38:07 PM - Debug - Control found Altimeter

14/05/2019 1:38:07 PM - Debug - Control found cabinPressure

14/05/2019 1:38:07 PM - Debug - Control found edp

14/05/2019 1:38:07 PM - Debug - Control found fuzeDisplay

14/05/2019 1:38:07 PM - Debug - Control found smcModeDisplay

14/05/2019 1:38:07 PM - Debug - Control found SMC_AV8B

14/05/2019 1:38:07 PM - Debug - Control found stabilizerDisplay

14/05/2019 1:38:07 PM - Debug - Control found OneDigitDisplay

14/05/2019 1:38:07 PM - Debug - Control found AOA

14/05/2019 1:38:07 PM - Debug - Control found trimPositionRudder

14/05/2019 1:38:07 PM - Debug - Control found trimPositionAileron

14/05/2019 1:38:07 PM - Debug - Control found Battery

14/05/2019 1:38:07 PM - Debug - Control found edpNoz

14/05/2019 1:38:07 PM - Debug - Control found FiveDigitDisplay

14/05/2019 1:38:07 PM - Debug - Control found ThreeDigitDisplay

14/05/2019 1:38:07 PM - Debug - Control found IAS

14/05/2019 1:38:07 PM - Debug - Control found FourDigitDisplay

14/05/2019 1:38:07 PM - Debug - Control found TwoDigitDisplay

14/05/2019 1:38:07 PM - Debug - Control found VVI

14/05/2019 1:38:07 PM - Debug - Control found Accumulator

14/05/2019 1:38:07 PM - Debug - Control found BackupADI

14/05/2019 1:38:07 PM - Debug - Control found SlipTurn

14/05/2019 1:38:07 PM - Debug - Property editor found GuardedThreeWayAppearancePropertyEditor

14/05/2019 1:38:07 PM - Debug - Property editor found GuardedThreeWayBehaviorPropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found GuardedThreeWayToggle

14/05/2019 1:38:07 PM - Debug - Control found GuardedToggleSwitch

14/05/2019 1:38:07 PM - Debug - Property editor found GuardedToggleSwitchAppearancePropertyEditor

14/05/2019 1:38:07 PM - Debug - Property editor found GuardedToggleSwitchBehaviorPropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found GuardedSwitch

14/05/2019 1:38:07 PM - Debug - Property editor found GuardedSwitchAppearancePropertyEditor

14/05/2019 1:38:07 PM - Debug - Property editor found GuardedSwitchBehaviorPropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found HatSwitch

14/05/2019 1:38:07 PM - Debug - Property editor found HatSwitchAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Control found HeliosPanel

14/05/2019 1:38:07 PM - Debug - Property editor found HeliosPanelAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Control found ImageDecoration

14/05/2019 1:38:07 PM - Debug - Property editor found ImageDecorationAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found IndicatorAppearancePropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found TextDisplay

14/05/2019 1:38:07 PM - Debug - Control found Indicator

14/05/2019 1:38:07 PM - Debug - Property editor found TextDisplayAppearancePropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found IndicatorPushButton

14/05/2019 1:38:07 PM - Debug - Property editor found IndicatorPushButtonAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Control found LineDecoration

14/05/2019 1:38:07 PM - Debug - Property editor found LineDecorationAppearancePropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found AMPCD_FA18C

14/05/2019 1:38:07 PM - Debug - Control found MPCD_FA18C

14/05/2019 1:38:07 PM - Debug - Control found MPCD_AV8B

14/05/2019 1:38:07 PM - Debug - Control found MFD_A10

14/05/2019 1:38:07 PM - Debug - Control found MFD_F16

14/05/2019 1:38:07 PM - Debug - Control found Potentiometer

14/05/2019 1:38:07 PM - Debug - Property editor found PotentiometerAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found PotentiometerBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Control found PushButton

14/05/2019 1:38:07 PM - Debug - Property editor found PushButtonAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found PushButtonBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Property editor found PushButtonBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Control found RectangleDeocration

14/05/2019 1:38:07 PM - Debug - Property editor found RectangleDecorationAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Control found RotaryEncoderPushable

14/05/2019 1:38:07 PM - Debug - Control found RotaryEncoder

14/05/2019 1:38:07 PM - Debug - Property editor found RotaryEncoderAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found RotaryEncoderBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Control found RotarySwitch

14/05/2019 1:38:07 PM - Debug - Property editor found RotarySwitchAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found RotarySwitchBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Control found ScreenReplicator

14/05/2019 1:38:07 PM - Debug - Property editor found ScreenReplicatorBehaviorPropertyEditor

14/05/2019 1:38:07 PM - Debug - Control found TextDecoration

14/05/2019 1:38:07 PM - Debug - Property editor found TextDecorationAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Control found ThreeWayToggleSwitch

14/05/2019 1:38:07 PM - Debug - Property editor found ThreeWayToggleSwitchAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found ThreeWayToggleSwitchBehaviorEditor

14/05/2019 1:38:07 PM - Debug - Control found ToggleSwitch

14/05/2019 1:38:07 PM - Debug - Property editor found ToggleSwitchAppearanceEditor

14/05/2019 1:38:07 PM - Debug - Property editor found ToggleSwitchBehaviorEditor

14/05/2019 1:38:07 PM - Info - Initializing Main Window

14/05/2019 1:38:15 PM - Info - Profile starting. (Name="FA-18C_b_beta")

14/05/2019 1:38:15 PM - Debug - UDP interface starting. (Interface="DCS A10C")

14/05/2019 1:38:15 PM - Debug - UDP interface waiting for socket data. (Interface="DCS A10C")

14/05/2019 1:38:15 PM - Debug - UDP interface starting. (Interface="DCS F/A-18C")

Note - program then crashes (shuts down and closes) with no error messages.

Perhaps something funny going on with loading both A10 and F18 interface??

From Capt Zeen

Hello Joe.

 

First of all, we need to know what profile do you want to install, or if you are creating a new one.

 

If you want to use one of my already made profiles, you dont need to do nothing on the the interface tab, just install the profile in your helios folder and use my latest export files from my site.

Actually, if you do the interface tab "Setup DCS F/A-18C" or any other, you'll broke my exports, so is not a good idea!

 

If you are creating a completly new F18C profile, then probably you need to do the "Setup DCS F/A-18C", because you'll need the new export.lua for that.

Thanks for getting back to me, Capt Zeen.

I am trying to install your profile for the FA18C. I did misread an earlier post from BlueFinBima and thought I had to setup the FA18C profile from within Helios Profile Editor. I did that because I believed I'd followed your instructions from your video to the letter and I was still not displaying any output from DCS (this was prior to setting up the MFDs) during the "testing DCS" phase.

I realise I have made this difficult for you both to assist me as I've probably ended up with a mishmash of an install that is only half correct. I'm considering trying to completely un-install all Helios related stuff - including Helios directory in Documents and the Script folders in "Saved Games" - and then try a reinstall. My aim is to use Capt Zeen's profile as my starting point - so just trying to get that running at this stage. Before I leap into all of that though, I'll await your response and recommendations. Again, I really appreciate the help.

Cheers,

Joe

Hi Joe,

While it is not intuitive, Capt Zeen's Hornet profile does not use Helios's DCS F/A-18C interface. That interface did not exist when he wrote his profile.

The problem you see is a result of Helios attempting to open the same UDP port twice for the two different aircraft profiles and then falling over. I suggest that you get Capt Zeen's profile working first by following his instructions only. Do not install the DCS F/A-18C interface. Currently Helios does not support installing two Aircraft interfaces. The "invisible" failure is not graceful, and I will raise an issue to make the failure more explicit.

https://github.com/BlueFinBima/Helios/issues/140

Regards, BlueFInBima

Will attempt to get back to square one and start again!

Thanks for the advice - I'll report back...

With much thanks to Capt Zeen and BlueFinBima I have had success with Helios and Capt Zeen's FA18C profile. A complete uninstall, including manually deleting any Helios related folders in Documents and Saved Games allowed Helios to be reinstalled and run successfully. My previous issue with DCS not talking to Helios was fixed when I realised I had two folders in Saved Games (DCS and DCS Open Beta) evidently my working DCS (which is actually the Open Beta version) is NOT in the Open Beta folder) - anyway, with the scripts in both, the initial test worked fine. So, working now and whilst I have some additional queries to tweak it to be even better, I'll ask those in the appropriate existing thread for Capt Zeen's FA18C Profile.

This really is an awesome setup - thanks to the developers.

Hello! I'm trying to get my setup working but coming back to DCS after many years away and I'm totally lost. I've installed Helios 1.4.2019.0317, I've added Capt Zeen's Hornet profile, got it set up, but now I'm stuck trying to configure my .lua file to work.

As you can see above, this is my setup. #1 is my main monitor which is 3x 1920x1080 monitors on Surround with a bezel-corrected resolution of 5896x1080. Since this is the main monitor, I expect the upper-left corner (red arrow) to be 0, 0 and this seems to be the case most of the time.

#2 is my main touchscreen which is directly under the center-top monitor and #3 is my secondary touchscreen which is located to the left of #2 and under the left-top monitor. The setup looks like so:

I am working from Capt Zeen's original .lua file

_  = function(p) return p; end;
name = _('2_monitors_FA18C');
Description = 'Right, Left, RWR, IFEI, UFC, and AMPCD in right monitor'

--TOTAL DEL VIEWPORT
Viewports =
{
    Center =
    {
         x = 0;
         y = 0;
         width  = 1920;
         height = 1080;
         viewDx = 0;
         viewDy = 0;
         aspect = 16/9;
    }
}


--LEFT
LEFT_MFCD =
{
    x = 2078;
    y = 165;
    width = 330;
    height = 311;
}

--RIGHT
RIGHT_MFCD =
{
    x = 2890;
    y = 165;
    width = 330;
    height = 311;
}


-- RWR
F18_RWR =
{
    x = 3086;
    y = 600;
    width = 150;
    height = 150;
}



--AMPCD
CENTER_MFCD =
{
    x = 2482;
    y = 572;
    width = 315;
    height = 300;
}

--IFEI
F18_IFEI =
{
    x = 1972;
    y = 630;
    width = 430;
    height = 167;
}


--UFC
F18_UFC =
{
    x = 2458;
    y = 25;
    width = 380;
    height = 216;
}



UIMainView = Viewports.Center

My intention is to only use #1 and #2 for DCS, leaving #3 for other stuff like TeamSpeak and monitoring programs. When I set the Center width to be 5896 in the .lua file and set in-game resolution to 5896x1080, DCS displays the game in monitor #1 as would be normal. When I set the in-game resolution to 7816x1080, instead of keeping the red arrow as 0,0 and just bump the picture by 1920 pixels to the left or right, the game instead bumps the whole thing 3840 pixels to the left and now, the blue arrow becomes 0,0. The game now fills monitors #3, #2, and 2/3rds of #1 leaving the rightmost monitor showing the desktop.

Viewports =
{
    Center =
    {
         x = 1920;
         y = 0;
         width  = 5896;
         height = 1080;
         viewDx = 0;
         viewDy = 0;
         aspect = 737/135;
    }
}

With the .lua file set up as above, it still starts 0,0 at the blue arrow and just bumps the picture by 1 monitor to the right.

Viewports =
{
    Center =
    {
         x = 3840;
         y = 0;
         width  = 5896;
         height = 1080;
         viewDx = 0;
         viewDy = 0;
         aspect = 737/135;
    }
}

With the above setup and changing the in-game resolution to 9736x1080, it bumps the UI by 2 monitors so the UI is now displayed in monitor #1 but obviously the game has also taken over the two touchscreens.

Any suggestions appreciated!

Sorry Ice, I find the monitor setup inconsistent and confusing myself. I've not had much luck with negative viewport placement, however I'm sure that it can be beaten into submission if you're determined enough. I always start with the DCS monitor starting at 0,0, and then I place secondary displays to the right (irrespective of where they are physically located.

Have you taken a look at https://forums.eagle.ru/showthread.php?t=60815 ?

Right-side orientation would work without a hitch, I would assume, as I had that configuration before flying BMS. However, with BMS, this would be very messy since the UI screen forces a screen resolution change to the main screen and any screen(s) to the right. Because of this, multi-monitor BMS users prefer a left-side orientation as the resolution change won't affect anything to the left of 0,0 coordinates.

I guess nobody in DCS uses a left-side orientation?

What I would like to do is to set up 0,0 to either stay at the red arrow or be at the upper-left of monitor #2, but the game seems to only select either the red arrow or the blue arrow. It also seems to prefer either just using 5896x1080 resolution (just the main Surround screen) to display the game or use the 9736x1080 resolution (all three screens).

However, with BMS, this would be very messy since the UI screen forces a screen resolution change to the main screen and any screen(s) to the right.

You can force the BMS UI to start windowed without affecting the other screens.

Concerning your inital problem to have other screens left of 0,0 I spent several hours on this problem and did not find a solution. Maybe others are more skilled on this...

You can force the BMS UI to start windowed without affecting the other screens.

That is correct but old habits die hard :) Currently running some tests to see if there's any adverse effects of running windowed mode.

Concerning your inital problem to have other screens left of 0,0 I spent several hours on this problem and did not find a solution. Maybe others are more skilled on this...

So not just me. Good to know. :smartass:

-ICE

I am glad to see that you are still involved in flight sims. I never could figure out what happened to you and BMS. I had used your BMS profile for many years. Is there any chance of seeing a 4.34 BMS profile from you?

As to your issues, I have only 3 comments. Some at BMS indicate that the latest version of Helios is not BMS friendly so I have retained the original Helios to use with BMS when someone produces a 4.34 profile.

Second, I run 3 monitors and found that Helios had trouble when monitor 3 used an HDMI plug as that seemed to confuse/control the helios monitor reset feature. My solution was to only use 2 monitors and unplug the 3rd monitor when using the Helios monitor reset feature. I then plugged back the 3rd monitor and use it for Teamspeak, etc with no issues.

Lastly, perhaps I am misunderstanding your issues, but why not just tell Helios that everything is to the right of your main monitor(s) and then physically set them up the way you want to. Helios is not looking over your shoulder to see if you are cheating on your physical setup.

Good to see you back.

Hey sobe! Thanks for the kind words!

I have a 4.34 BMS profile now with all the new 4.34 stuff but it is not ready to be shared and even if it were, I do not know what would be the best way to do it. BlueFinBima has kindly offered to help me get the 4.34 profile compatible with Helios 1.4 so that's in the works now as well.

If your 3rd screen-HDMI issue persists whether using Helios 1.3 + BMS and also with Helios 1.4 + DCS, then maybe these kind folk can help you.

As for screen setup, I had everything to the right of the 0,0 monitor back when I was flying DCS but in the early days of BMS 4.32, there were some issues and IIRC, windowed mode didn't work well or had much lower framerates or something so I **HAD** to use fullscreen mode and I **HAD** to put everything to the left of the 0,0 monitor. I guess I just kept it that way since then. Just finished my testing with BMS different settings so if the numbers are good, I just might go back to right-side orientation.

Grateful for any help with BlueFinBima profile

I've been struggling to get BlueFinBima's excellent AV-8B Helios profile to work on my set up for the past week. Any counsel would be appreciated. Here's my arrangement: I'm using two Samsung monitors side by side; my main monitor on the left is a 27 inch at 3840x2160 resolution; on the right is a 22 inch at 1680x1050. So my combined resolution is 5520x2160. I'm running both monitors at 150 percent text magnification, which is recommended by Windows for the main monitor. The two monitors are properly aligned in my Windows monitors set up. So far, so good.

In the Helios editor, I reset the monitors so that BlueFinBima's profile comes up and is saved on my second (righthand) monitor. I copy the export.lua to my Saved Games folder.

I run Helios and BlueFinBima's profile comes up perfectly on my second monitor. So then I start DCS, and two problems are immediate: My cockpit extends across both monitors instead of just my main; and nothing comes up in the AV-8B panel windows on the second, righthand monitor except my extended cockpit in the background. I'm not competent in .lua editing and can't figure out what in the AV-8B config program to adjust:

_ = function(p) return p; end;

name = _('AV-8B Config');

Description = 'AV-8B MFCD, ODU, UFC etc. GUI Config'

-- x = displays[1].width + displays[2].width + 0;

if displays and #displays >2 then

primary =

{

x = displays[1].x - screen.x;

y = displays[1].y - screen.y;

width = displays[1].width;

height = displays[1].height;

aspect = displays[1].width/displays[1].height;

viewDx = 0;

viewDy = 0;

}

GUI=

{

x = displays[2].x - screen.x;

y = displays[2].y - screen.y;

width = displays[2].width;

height = displays[2].height;

aspect = displays[2].width/displays[2].height;

}

UIMainView = primary

xo = displays[2].width;

-- xo = 0;

LEFT_MFCD =

{

x = displays[1].width + xo + 0;

y = 0;

width = 334;

height = 312;

}

RIGHT_MFCD =

{

x = displays[1].width + xo + 340;

y = 0;

width = 334;

height = 312;

}

UFC_base =

{

x = displays[1].width + xo + 0;

y = 320;

width = 453;

height = 385;

}

ODU_base =

{

x = displays[1].width + xo + 680;

y = 0;

width = 283;

height = 140;

}

UVHF_base =

{

x = displays[1].width + xo + 460;

y = 320;

width = 210;

height = 210;

}

Viewports = {primary}

else

primary =

{

x = 0;

y = 0;

width = screen.width;

height = screen.height;

viewDx = 0;

viewDy = 0;

aspect = screen.aspect;

}

UIMainView = primary

Viewports = {primary}

end

Any ideas?

Ok, made some progress; still need some counsel

Per my post above, I successfully edited BlueFinBima's monitor .lua, but I'm still not getting communication between the game and Helios. What am I not doing or doing wrong. See attached.

AV-8B FX.lua

Hi Franx, I see a few problems with your lua, but it would help me to know what the dimensions of the two displays are before I comment further.

Cheers, Neil

Thanks for the reply. My left (main) monitor is 3840x2160; my right (secondary) monitor is 1650x1080. Both are set at 150 percent magnification, which is recommended for the main monitor. Both are Samsungs -- 27 inch and 22 inch respectively, I think.

1680x1050. sorry.

Not an expert in this area, and I have not tested this (and the positions will not be precise) but I think this should get you started. In your game options, I would expect that your DCS options should have a resolution of 5520x2160.

_  = function(p) return p; end;
name = _('AV-8B FX');
Description = 'AV-8B MFCD, ODU, UFC etc.  GUI Config'
   Center = 
   {
       x 		= 0;
       y 		= 0;
       width   = 3840;
       height  = 2160;
       aspect  = 1.77777778;
       viewDx  = 0;
       viewDy  = 0;
   }
   GUI=
   {
       x 		= 0;
       y 		= 0;
       width   = 3840;
       height  = 2160;
   } 

   LEFT_MFCD = 
   {
       x = Center.width + 20;
       y = 680;
       width = 334;
       height = 312;
   }

   RIGHT_MFCD = 
   {
       x = Center.width + 1326;
       y = 680;
       width = 334;
       height = 312;
   }

   UFC_base = 
   {
       x = Center.width + 610;
       y = 320;
       width = 453;
       height = 385;
   }

   ODU_base =
   {
       x = Center.width + 20;
       y = 40;
       width = 283;
       height = 140;
   }

   UVHF_base =
   {
       x = Center.width + 460;
       y = 320;
       width = 210;
       height = 210;
   }

   UIMainView = Center
   Viewports = {Center}

Hope this gets you going.