Helios 1.6 - Official Thread

[PSYKOnz]

I need to better understand how to carve out space to show a radar screen from the Skyhawk in Helios

 

I’m not sure if you have all ready figured this out or not but here’s how I did it.

 

Make a copy of the background file, gots ya have ya backups!

 

open paint3d... yes paint 3D, it worked for me.

 

set the background (canvas) to transparent

 

then open up the copy of the background (you can also just open it up and the. Change the canvas to transparent)

 

remove the area you want to make transparent (select and cut or erase or what ever)

 

save the file, make sure your saving it as a file type that handles transparency, png, or what ever

 

Over in the profile area go to the background file and save change it to the new file.

 

done.

 

ofcorse, of your really clever you can use a real editing program And mess around with alpha layers and fades etc

 

I am not this clever, and never will be so I used paint.

 

here's a screenshot of it running on my desktop after doing the procedure above,

 

[derammo]

Bit of a weird question

 

is it possible to make a generic cockpit up that will work with any aircraft? So that I can have all the custom ones but when I’m flying one that dose not have a custom pit I can still have the basics? Ie, altitude, speed, bearing, rwr, mfcds etc?

 

Here are some links to study:

 

https://github.com/HeliosVirtualCockpit/Helios/wiki/Change-Log#all-dcs-interfaces-using-helios-driver-now-provide-basic-telemetry

NOTE: doesn’t work in Multi Player if the server is blocking the use of the LoGet... functions

 

https://github.com/HeliosVirtualCockpit/Helios/wiki/Simulator-Viewport

(There are generic Simulator Viewport objects for the generic names for MFDs etc. that exist in many aircraft)

 

So you will get SOME stuff for SOME aircraft, depending on the whims of the different DCS aircraft developers and MP server settings. Have fun.

 

[PSYKOnz]

 

Here are some links to study:

 

https://github.com/HeliosVirtualCockpit/Helios/wiki/Change-Log#all-dcs-interfaces-using-helios-driver-now-provide-basic-telemetry

NOTE: doesn’t work in Multi Player if the server is blocking the use of the LoGet... functions

 

ok, I'm a bit confused, so helios is already doing the basic gauges? it's not working in single or mp, does anyone have a howto? seeing it in the changelog is good but doesn't help me, I'm all good with the viewports, that bit I have done, it's getting the gauges to work that I need some help with

 

please forgive my ignorance

 

 

[derammo]

I know people have complained about this a while ago. Is there any fix to make the exported viewports brighter?

 

Please file a lot of bugs against DCS aircraft about this :). It is DCS that renders the viewports and we (Helios) have basically no control over it. I did some Lua hacking for the F/A-18C to bump up the brightness (these changes of mine are already automatically applied when you configure Helios 1.6.) But it is not generally possible for me to fix that for the other planes. So please file bugs/enhancement requests against all the planes where it doesn't work well. It requires code changes by the plane developers.

[linknet]

If I add a Falcon BMS 4.34 viewport to Helios 1.6 the viewport properties has a "Patch Required" checkbox.

 

What exactly is this? Is this a patch for Falcon BMS or a patch for Helios?

 

Any help would be appreciated.

[derammo]

If I add a Falcon BMS 4.34 viewport to Helios 1.6 the viewport properties has a "Patch Required" checkbox.

 

What exactly is this? Is this a patch for Falcon BMS or a patch for Helios?

 

Any help would be appreciated.

 

Unfortunately, those viewports are only for DCS

https://github.com/HeliosVirtualCockpit/Helios/wiki/Simulator-Viewport

[MAXsenna]

If I add a Falcon BMS 4.34 viewport to Helios 1.6 the viewport properties has a "Patch Required" checkbox.

 

What exactly is this? Is this a patch for Falcon BMS or a patch for Helios?

 

Any help would be appreciated.

I believe BMS has easier solutions.

Cheers!

 

Sent from my ANE-LX1 using Tapatalk

 

 

[linknet]

Unfortunately, those viewports are only for DCS

https://github.com/HeliosVirtualCockpit/Helios/wiki/Simulator-Viewport

 

Thanks for the information, that explains why I couldn't get them to work!!

 

 

[Cop23rd]

Hello,

 

I am trying to control a virtual joystick (vjoy) using Helios.

A button pressed via touch in Helios should e.g. simulate the virtual DX button 1 in the virtual joystick.

 

Is that possible?

[PSYKOnz]

Will the a10c2 be supported as an option for cockpits and will the capt zeen a10c profile work for it?

[derammo]

Hello,

 

I am trying to control a virtual joystick (vjoy) using Helios.

A button pressed via touch in Helios should e.g. simulate the virtual DX button 1 in the virtual joystick.

 

Is that possible?

 

It is not. I decided supporting anything involving vJoy was not worth it. I don't want to deal with a kernel driver signed by a random person being installed on people's computers.

For DCS applications, we have always been able to do everything we want by just sending cockpit interaction (via Helios' DCS interfaces) and keyboard bindings (via Helios' Keyboard interface.)

 

That said, there is nothing stopping anyone from writing a Helios plugin interface to talk to vJoy if they want. I just did not want to be the one who has to maintain or support that :).

 

 

[derammo]

Will the a10c2 be supported as an option for cockpits and will the capt zeen a10c profile work for it?

 

Didn't you already discuss that on the Discord?

[PSYKOnz]

Nope. Not on discord lol, what was discussed?

Edited November 18, 2020 by PSYKOnz
spellchecker changed discussed to fist, don't know how but it did

[weijas]

Hi

 

After installing the Capt Zeen A-10C Warthog v3.0 Helios profile.

 

All seems well, but gauges and button don't work when activated.

 

Eg, the right and left MFD don't respond to the button pressed(though it is animated on the screen).

 

Any solution to the problem or have I miss out some steps.

 

Any advise is greatly appreciated.

 

Thanks

 

Can this work with A10C II?

[sharkfin61]

Am 26.12.2020 um 13:58 schrieb weijas:

....

 

Can this work with A10C II?

The latest version of Helios 1.6 has support for the A-10 C II. But be aware you might have conflicts with your "normal" A-10C" profile. (At least, I had).

[PSYKOnz]

So how did you get around that? Double up the profile and rename it?

[sharkfin61]

Was busy with my CDU project, will try it tomorrrow.

Gesendet von meinem SM-T820 mit Tapatalk

[NotCallMeHacker]

I cant figure out why Helios Keypress Reciever is not working, I tried pretty much everything but the biggest problem is, that there are no online Resources for this.

PC 1 (Running DCS):

PC2 (not running DCS):

Thanks in advance

[GPatricks]

New to Helios and DCS from the BMS/YAME64 world. I can't seem to get the gauges to communicate with the gauges or MFDs displayed when placing them from the "F-16" images. There is no "F-16 Interface" listed to install. Failing that I installed Capt. Zeens' F-16 profile and removed all the gauges as it seemed to install a "DCS Generic impersonating F-16C_50" Interface Put the gauge images from the F-16 folder in place, still nothing. Added the "Additional Viewports" Interface and the placed the RMFD.RMFD, and EHSI from the "F-16 Simulator Viewports" folder in place, made sure all tabs (DCS MonitorSetup/Interface/etc.) had no errors and hopped in DCS World. The MFDs and EHSI worked perfectly (actually they work without invoking the profile at all) but still no input into the other gauges. I'm missing a step (or 2 or 10),please advise!

 

This is where i'm at now...

 

 

[GPatricks]

On 11/9/2020 at 1:06 PM, linknet said:

If I add a Falcon BMS 4.34 viewport to Helios 1.6 the viewport properties has a "Patch Required" checkbox.

 

What exactly is this? Is this a patch for Falcon BMS or a patch for Helios?

 

Any help would be appreciated.

 

For BMS Falcon 4.35 (which moved to DX11) you currently need to use the included RTT extraction tool for MFDs, but can combine it with the easy to use YAME64 1.21 for other gauges. I believe once the U1 patch comes out you may be able to use YAME64 for everything again (as it was in 4.34)..

Been a while since I was here, but now with Helios 1.6 and the new profiles available Helios does it all, no need for RTT at all on a strong system!

 

Edited March 27, 2022 by =LD=Icer
Update

[GPatricks]

Saw a video where someone copied the gauges from a working profile and pasted them in a 2nd Helios Editor window with his new profile in it. As my "working" profile is a bastardized Cat. Zeen's "F16C_v1.1b" profile and all that works are the LMFD/RMFD/EHSI gauge Viewports I figured give it a shot. Copied the Engine RPM% gauge over, resized it. Copied the Nozzle Position gauge over, resized it. Copied the Fuel Flow over but all that copied was the 4 number window and no bezel, and it won't resize so it's too small. Reset everything so no errors and fired DCS up, everything worked perfectly! 

 

I'll keep plugging away but I still need a full size Fuel Flow, a Fuel gauge (to take Nozzle Positions place), a VVI, and an AoA gauge to finish up.... Here is where she is today.

 

Edited January 12, 2021 by GaryR

[sharkfin61]

Maybe the missing bezels are part of the background.

For the gauges, I did the similar thing (copy out of a working profile) with the A-10C profile to fit it into my main console. Worked almost out of the box.

What I missed was to press the shift key when trying to resize them.

[GPatricks]

Thanks man, that worked! Now I need to figure out what I screwed up to have the main screen extend down into my two MFDS... The Helios.lua seems to be correct but the main screen is running in 2560x2240 instead of 2560x1440 so it's the background in my MFDs.. now lol. This is how the Profile Editor sets the Monitor Setup, tried " height = 1440" but it throws an error and resets it.. If I set it at 1440 and don't run a profile I get the viewports (MFDs and EHSI) and all is well..

 

 Helios.lua -

 

_  = function(p) return p end
name = _('Helios')
description = 'Generated from compatible Helios Profiles'
F_16C_EHSI = { x = 1968, y = 2049, width = 188, height = 184 }
F_16C_LEFT_MFCD = { x = 0, y = 1440, width = 550, height = 550 }
F_16C_RIGHT_MFCD = { x = 1968, y = 1440, width = 548, height = 549 }
Viewports = {
  Center = {
    x = 0,
    y = 0,
    width = 2560,
    height = 2240,
    aspect = 1.14285714285714,
    dx = 0,
    dy = 0
  }
}
UI = { x = 0, y = 0, width = 2560, height = 1440 }
UIMainView = UI
GU_MAIN_VIEWPORT = Viewports.Center

Edited January 12, 2021 by GaryR

[sharkfin61]

vor 1 Stunde schrieb GaryR:

... tried " height = 1440" but it throws an error and resets it.. If I set it at 1440 and don't run a profile I get the viewports (MFDs and EHSI) and all is well..

 

...

 

I guess if you set the red height to something else than 2240 and don't the aspect ratio it won't fit (should be 1,777777777777778 in that  case)

ALso you have an extra line in your helios.lua: UI = { x = 0, y = 0, width = 2560, height = 1440 }

 

Here's my .lua to compare (I extracted the viewport for th A-10C CDU, positioned in nvidia setup right of my main screen):

 

_  = function(p) return p end
name = _('Helios')
description = 'Generated from compatible Helios Profiles'
A_10C_CDU_SCREEN = { x = 1945, y = 0, width = 773, height = 595 }
Viewports = {
  Center = {
    x = 0,
    y = 0,
    width = 1920,
    height = 1080,
    aspect = 1.77777777777778,
    dx = 0,
    dy = 0
  }
}
UIMainView = Viewports.Center
GU_MAIN_VIEWPORT = Viewports.Center

 

[GPatricks]

You can see above and below what I get if I let Helios "Reset Monitor" to clear the errors in the Profile Editor. The DCS main screen uses the whole area (of 2560x2240) to display which puts parts of it on my Lilliputs..

The red lines on the bottom are added (the lines on the bottom were like yours before)/ and height is changed from 1440 to 2240...

 

===============================================

_  = function(p) return p end
name = _('Helios')
description = 'Generated from compatible Helios Profiles'
F_16C_EHSI = { x = 1968, y = 2049, width = 188, height = 184 }
F_16C_LEFT_MFCD = { x = 0, y = 1440, width = 550, height = 550 }
F_16C_RIGHT_MFCD = { x = 1968, y = 1440, width = 548, height = 549 }
Viewports = {
  Center = {
    x = 0,
    y = 0,
    width = 2560,
    height = 2240,
    aspect = 1.14285714285714,
    dx = 0,
    dy = 0
  }
}
UI = { x = 0, y = 0, width = 2560, height = 1440 }
UIMainView = UI
GU_MAIN_VIEWPORT = Viewports.Center

==========================================

Edited January 12, 2021 by GaryR