Jump to content

Bunny's Apache Helios Touchscreen Profile


Recommended Posts

I'll be updating mine with Helios display patching at some point. I'd like ED to at least fix TEDAC export ghosting first, but I might just implement it anyway and then manually comment out the TEDAC export. 

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

I am thinking about getting back in to helios. I used it for the A-10 a long time ago now I would like to use it for the Apache. Can you tell me where I can find or make a KU panel that has a widow for the KU text to show through? Thank you

AMD Ryzen 5 2600 Six-Core Processor 3.4 GHz

32 Gb RAM, Nvidea GTX 1050 TI

Water Cooled, Windows 10 64 bit

Link to comment
Share on other sites

11 minutes ago, 16th Widowmakr said:

Can you tell me where I can find or make a KU panel that has a widow for the KU text to show through? Thank you

Like the one bottom center in my profile? You can just download my profile from here and use it. 

Link to comment
Share on other sites

13 minutes ago, Bunny Clark said:

Like the one bottom center in my profile? You can just download my profile from here and use it. 

I did that butt can't seem to find it. I put the file folders in Documents/Helios folder. Can I copy and paste the panel in to the profile editor?

AMD Ryzen 5 2600 Six-Core Processor 3.4 GHz

32 Gb RAM, Nvidea GTX 1050 TI

Water Cooled, Windows 10 64 bit

Link to comment
Share on other sites

  • 1 month later...
  • 3 months later...

Also how to incorporate this fix ---> 

   into mine monitor config.lua which is:

 

_  = function(p) return p end
name = _('H_AH64D_Multiseat_SwitchPit2')
description = 'Generated from Helios Profile AH64D_Multiseat_SwitchPit2'
AH64_CMWS = { x = 3310, y = 864, width = 144, height = 72 }
--AH64_CPG_EUFD = { x = 3280, y = 640, width = 400, height = 196 }
AH64_CPG_KU = { x = 2640, y = 640, width = 480, height = 60 }
--AH64_LEFT_CPG_MFD = { x = 2000, y = 80, width = 480, height = 480 }
AH64_LEFT_PLT_MFD = { x = 2000, y = 80, width = 480, height = 480 }
AH64_PLT_EUFD = { x = 2635, y = 20, width = 455, height = 300 }
AH64_PLT_KU = { x = 2640, y = 617, width = 480, height = 60 }
--AH64_RIGHT_CPG_MFD = { x = 3280, y = 80, width = 480, height = 480 }
AH64_RIGHT_PLT_MFD = { x = 3280, y = 80, width = 480, height = 480 }
AH64_TEDAC = { x = 2640, y = 80, width = 480, height = 480 }
Viewports = {
  Center = {
    x = 0,
    y = 0,
    width = 1920,
    height = 1080,
    aspect = 1.77777777777778,
    dx = 0,
    dy = 0
  }
}
UI = { x = 0, y = 0, width = 1920, height = 1080 }
UIMainView = UI
GU_MAIN_VIEWPORT = Viewports.Center

 

 

And how to use this fix which is listed in December 21, 2022 update ?

  • Fixed: Exported TEDAC creates a double image on the TEDAC in the cockpit.

[sIGPIC][/sIGPIC]

Pilot from Croatia

Link to comment
Share on other sites

  • 3 weeks later...

Hi All, 

Reaching out for advice and assistance - please.

I have a 4 monitor set up, 1 x 15.6 touchscreen (recently purchased - bit by mistake - don't ask!) - so attempting to use with Helios, 2 x 27 curved main screens, and one 11.6 monitor for MFD exports.

The 2 x 27 are idented 1 and 2, the touchscreen 3 and the 11.6 as 4.  However, the rub is that in order for the touchscreen to work properly and detect touches on its screen - it needs to be selected as the main screen - so the monitors are set up in order 3, 1, 2, 4, to account for DCS being pedantic about taking x/y as 0/0 from the main screen.

I set the main viewport up so that the display HUD central point was about 2 thirds across screen 1 by adding a value to the x (1080) - so in effect the viewport starts 2/3 across screen 3 (leftmost), and extending across screen 1 and 2, The above alignment was OK, but I cannot find anyway to blank the background of the touchscreen in this configuration so that the only display is the helios overlay. If I do a background fill the viewports do not display data, and if I do not I get the 3d world running behind (and visible) in the viewports.

Hopefully the above makes sense - but am at a bit of a loss. The only workaround I can come up with is by moving the touchscreen above the 1st main screen so both x values are the same, then dropping the main viewport y value down to align with the main screens. Ideally I want them all in a line to assist in mouse pointer transition between screens.

Any guidance and assistance well received.

 

AMD Ryzen 5 5600X; ASUS ROG Strix X570-F, Corsair Vengeance 64 GB (2x 32GB) 3600MHz; Seagate FireCuda 510 500GB M.2-2280 (OS); Samsung 860 EVO 2TB M.2-2280 (DCS); MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU. TM Warthog Hotas; T.Flight Pedals; DelanClip/Trackhat.

Link to comment
Share on other sites

Why do you say the touchscreen has to be monitor 1? There is a utility in Windows that you go through and touch the screens that are touchable and skip over the ones that aren't.  Does this method not work for yours?

I run a configuration that looks like this, where monitor 1 is my main display at 3440 x 1440 non-touch, and the two smaller screens are 1024 x 600 and are touch-enabled for Helios.

image.png

 

  • Like 1
Link to comment
Share on other sites

Hi @Floyd1212 - many thanks for the response - as that would be so much easier, but for some reason it will only calibrate/setup if I unplug/replug it back in with a USB lead to carry the touch commands. I can then select screen 1 as main and screen 3 as a touch, but if I reboot the PC screen 3 loses its abilities to maintain the touch capabilities and they show up on the main screen.

 

image.png

AMD Ryzen 5 5600X; ASUS ROG Strix X570-F, Corsair Vengeance 64 GB (2x 32GB) 3600MHz; Seagate FireCuda 510 500GB M.2-2280 (OS); Samsung 860 EVO 2TB M.2-2280 (DCS); MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU. TM Warthog Hotas; T.Flight Pedals; DelanClip/Trackhat.

Link to comment
Share on other sites

On 4/11/2023 at 5:50 PM, Floyd1212 said:

Yeah, mine occasionally act up, too, and when I touch them I get phantom presses on the main screen.  I run the utility again, which takes a few seconds, to sort it out again. 

The problem I have is that the utility is not available unless I unplug/replug the screen, and the settings do not save - which makes it a bit cumbersome having to reset it every time I restart the PC.


Edited by Leg2ion

AMD Ryzen 5 5600X; ASUS ROG Strix X570-F, Corsair Vengeance 64 GB (2x 32GB) 3600MHz; Seagate FireCuda 510 500GB M.2-2280 (OS); Samsung 860 EVO 2TB M.2-2280 (DCS); MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU. TM Warthog Hotas; T.Flight Pedals; DelanClip/Trackhat.

Link to comment
Share on other sites

  • 11 months later...
On 7/3/2022 at 4:35 AM, Bunny Clark said:

Now that Helios has native support for the Apache module, I figured I'd make a thread for this by itself. 

This new version of my Helios profile does not require a custom Interface. Simply copy the Profile and Images into your folder and it'll work. 

Requires Helios version 1.6.5305.0.

Download here: https://www.digitalcombatsimulator.com/en/files/3322990/

Includes a Pilot and CPG pit with MFDs, EUFD, KU, Master Armament Panel, Master Caution Panel, Lighting Panel, Video Panel, Tailwheel Panel, and a toggleable Comms Panel. I've also included bonus panels for the Engine Control Panel, Windshield Wiper Panel, Fire Warning Panel, and CMWS which are hidden and unused by default but fully mapped and functional if you'd like to unhide them and place them.

Thank you soooo much, your profile was the only one I could get working! It's really a beautiful thing. And did I say thanks?  🙂

 

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...