Capt Zeen F/A-18C Beta Helios Profile ! ! !

[RookFett]

The main monitor is an Asus RoG Swift 34" curved (3440X1440) and the touch screen is a Dell P2418HT 23.8" (192X1080).

 

 

 

I have them configured to have the swift as the primary, on the left, and the other as the secondary on the right. So it increases my horz.

 

 

 

then I just move the dell to be below the screen. Easier to setup in helios and other programs I found.

 

 

 

 

I am using Track IR 5 - with the deadzone in the middle set so I can glance down on the second panel without messing up the view to much. Still playing with it to get it just right.

[Fakum]

ah,,, ok,, I was wondering about the height of the primary monitor,, one of the reasons why I have not gone beyond my 30". I want to keep the height at 1600. Thanks for the reply.

[Tomcat]

İ hate updates

damn i cant do it again.

İ can only get the mfds

the rest are missing.

whaterver i do,never worked

[Capt Zeen]

you need to use a module controller, like JSGME, if not you can become frustrated!

[Tomcat]

you need to use a module controller, like JSGME, if not you can become frustrated!

 

 

Thank you but i dont know how to use it with your profile.

Search and could not find any.

???

[mhe]

You just put stuff like the scripts that modify the aircraft instruments into mod packages (works with JSGME or OVGME). When a DCS update comes, you don't update but hit "Later" instead.

Stop DCS, open your preferred mod package manager, disable all mods, run DCS updater and let it do its job and once it's done, you re-enable the mods again with that mod manager. It is really not that hard but saves you a lot of time.

 

Also, I got the bug with the super thick lines again on the AMPCDs and the MFDs. This seems to only happen with 4k resolutions for the main screen.

Edited October 24, 2018 by mhe

[gargue]

UPDATE 2

 

Fixed the beheviors of some switches:

 

Launch bar Switch

Hook Bypass Switch

ALR-67 Power Button

And deleted the AMPCD config files, we don't need it anymore

 

UPDATE 1

 

Fixed the change of device numbers on the ED update.

 

--------------------------------------------------------------------------------------------------------------

 

 

 

Hello all !

 

Here we come, with another Helios profile! This time for the F/A-18C Hornet.

I made the profile using the A10C interface in Helios. With that, we dont need to prepare different versions for differents countries, we dont need the default.lua to define all the keyboard commads, because i redirect directly to DCS from helios, so we dont need to worry abous future changes. And of course, for the final user, (you), is a more easy installation ! So here you got a fully input/output F/A-18C profile. Hope you like it !

 

- Beta version:

 

Important notice !!

As everyones knows, i publish the F/A18C profile while the DCS F/A-18C module is still in Early Access state.

Thats mean the module is still not finished and we foresee more changes in it, so the Helios profile will need some changes on the near future. In this version I implemented all the switches, lamp, instruments and levers that actually work on the module. I publish the profile in beta version, with the purpose of test it, and of course, everyone can enjoy it before the module will be finish.

 

For this profile i exported all the instruments, lamps, selectors, switches and levers in the F/A-18C cockpit.

Of course i added the navigation panel from others profiles, so you can check airport charts, tactical maps, ndbs, etc

 

Main panel

 

Right panel

 

Left panel 1

 

Left panel 2

 

Bottom panel and Brakers panel

 

 

 

 

- Profile files:

 

F18_beta.hpf .....................16:10 monitor resolutions

F18_b_beta.hpf .....................16:9 monitor resolutions

 

 

- Export.lua:

 

Another important notice !!

Included in the Scripts folder, you can find the export.lua, ready to export data A10C, KA50, FC3, F-15C, P-51D, UH-1H, A10C radio fix, MI-8 v1.5, SA342, Mig21bis, L39ZA and the F/A-18C Hornet profile.

This file is a modified version of the Loophole Updated version from 09/11/2014, ( http://forums.eagle.ru/showthread.php?t=97222 )

 

- Monitor aspect resolutions:

 

I made two different profiles, v1.0 for 16:10 monitors and v1.0b for 16:9 monitors. Use the one better fit width you monitor resolution.

 

- Thanks:

 

I made the entire graphic art, based on screenshots of the simulator, and the textures folder of the game.

I used the airport charts from http://www.virtual-jabog32.de and the tactical chart TC-1 created by =MAF=Mongoose and the NDBs list created by Lino_Germany.

For the export.lua i used the Loophole version, compatible width KA50, A10c and FC3 as a base for all my implementations.

In the export.lua i include a couple of functions by [FSF]Ian to export the digits of the UV26 for the MI-8

I want to thanks aswell to all the people who help me, in the DCS forum, every time i reached a deadlock, somewhere!

And of course to Gadroc for creating Helios, this great software.

 

PROFILE FEATURES

 

All panels are designed independently, so you can re-arrange the design if you need it to fit your rig.

 

Main Front Panel:

- All the instruments, switches and lamps

- Empty spaces to visualize the viewport exports for IFEI, UFC, RWR, AMPCD and the two DDI

 

Auxiliar panels:

- All the instruments, switches, levers and lamps

 

Left 1 and Left 2 panel:

- The Left panel is divided in two - All the instruments, switches, levers and lamps

 

Right panel:

- All the instruments, switches, levers and lamps

 

Bottom panel:

- All the instruments, switches,levers and lamps

 

Brakers panel:

- All the switches

 

 

Navigation panel:

-Airports visual operation charts v4.04

-Airports diagramss v4.04

-TC-1 Tactical Chart

-Caucasus general area map, with airports and table width airport freqs, locations, ids, etc.

-Airport Circuit Example

-List of the NDBs

 

- About panel:

- Info about the profile and version.

 

 

 

SPECIAL ACTIONS

 

-Helios dont use right mouse buttons so i created special buttons to simulate several cockpit actions:

 

 

 

 

 

INSTALLATION

 

--Install Helios if you don't have it yet. (http://www.gadrocsworkshop.com/helios/latest)

-Copy the profile you need, for your resolution , on the profiles folder, usualy in user/my documents/helios/profiles

-Copy the folder Capt_Zeen on the images folder, usualy in user/my documents/helios/images

-Run the HeliosProfileEditor, load the profile F18 you want to use, and perform a Reset Monitors from the menu Profile.

-Save the profile

-Dont forget to use the correct export.lua i included in the package,

Copy it in C:\Users\yourusername\Saved Games\DCS\Scripts, but first make a backup copy of your actual export.lua.

-IF you use Tackview, Simpleradio, DCS-bios or another external scripts, copy the corresponding lines from your old export.lua to the new one.

 

RUNNING THE PROFILE

 

 

-Open the Helios Control Center, select the profile and start it.

 

 

CONFIGURING THE SECOND MONITOR

 

included in the package, there is a folder called "DCS Monitor Configuration" width a complete folders structure you can drop on DCS World instalation folder. This structure prepare the diferents lua scripts to export the views to the second monitor to represent the IFEI, UFC, RWR, AMPCD, left and right DDI.

You will need to change the coordinates x and y of every viewport and the width and height sizes of them in the DCS Monitor Configuration\Config\MonitorSetup\2_monitors-F18.lua

Change it before copy to the game folder, and save a copy of this structure, cause DCS world rewrite this files every update!

To calculate the correct position of each viewport, run Helios and start the profile. Take a screenshot and paste the image in any art program. Paint from Windows works well.

Put the cursor over the left-up corners of every empty spaces and write down the coordinates. Drag a box from that point to the right_down corner, and take the width and height of the rectangle.

Modify the 2_monitors-F18.lua width your correct numbers. and you can now copy the complete "DCS Monitor Configuration" folder to the DCS game folder, or use a Mods control program like JSGME to do it.

 

Also, you can use this template to calculate the position and sizes of the diferent viewports: (note how IFEI uses a bigger space to fit correctly in his place)

 

 

 

 

KNOWN ISSUES

 

- The switches of the APU power and Crank do not return automaticaly to his rest position after use them from Helios, so you need to do it manually. I hope fix this in the final versión

 

OTHER CONSIDERATIONS

 

If you use Helios and TARS or TACKVIEW you can have miss workings due to the way Helios works width the export.lua.

To prevent this, just move the lines for Tars or tackview to the very end of the export.lua in C:\Users\yourusername\Saved Games\DCS\Scripts.

 

 

 

 

As always, you can get it in the download section of my site:

http://www.captzeen.com

 

 

Hope you like it !

 

 

 

 

 

TROUBLESHOOTING:

 

 

Wen you install a Helios profile, and you got a problem, try to identify exactly what happens.

Usually two issues can show up:

 

1 - The gauges, switches, lamps, etc, don't work

 

2 - The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work.

 

 

In the FIRST case: The gauges, switches, lamps, etc, don't work

 

Helios is probably not getting the DCS info needed, and thats because the export.lua is not doing his job. So...

 

- check if the export files are you using are the correct ones

- check if the place where you installed is the correct one:

Export.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\

HelioCore.lua and HeliosExport.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\Helios\

- then double check again !

- and of course, always use my last export files.

 

If you are using a system with more than two monitors,

- check the FAQ on the site. There is a bug on Helios that can asign a incorrect monitor to all bindings on the profile. There you got a solution for that.

 

If everything looks correct with the export files and still no joy,

- run a mision, and exit DCS,

- then check the dcs.log in savedgames/dcs/logs and look for errors in the export.lua . If something wrong happens in the export.lua the log tell you where to look at.

 

If you are using other tools with Helios, like: Simpleradio,Tackview DCS-bios etc, you can try to change the order of the lines in the export.lua. Those ones do not give problems, but some tools can, so give it a try.

 

 

In the SECOND case: The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work.

 

Ok, this is important to know, Helios do not export the viewports, is DCS who do that.

 

Some DCS modules are ready to export some of his viewport, but not all of them. That's the reason we need to change some .luas to make that module ready to export the viewports.

 

In the F18 case, and at this date ( 29/Aug/2018 ), only the 2 DDIs and the AMPCD are ready to export. The IFEI, RWR and UFC are not, so we need to overwrite those .luas with other ones ready to export viewport.

 

Usually, in my profile packages you got everything you need to do that operation in a folder called monitor configuration. So...

 

- Check if you installed the files in the correct place. I recomend to you use JSGME or OVGME to do the job, because in every DCS update those files are rewriten again

- Then edit the MonitorSetup file to adjust the viewports to your monitor configuration. (2_monitors-FA18C.lua )

- In DCS options, put your max resolution ( this is the total of your monitor resolutions in horizontal and vertical, for example two monitors 1920x1080 placed in horizontal layout, the total resolution is 3840x1080 )

- In DCS options, uncheck full screen option

- In DCS options, select the monitorsetup file to use (the one your just edited)

 

 

 

IMPROVING THE LINES QUALITY IN THE EXPORTED VIEWPORTS

 

https://forums.eagle.ru/showpost.php?p=3555460&postcount=117

 

 

 

 

 

 

if you got other problems, check the FAQ on the site

If still you don't find a solution, you can use my discord channel too: https://discord.gg/sS66aJf

 

And of course you can ask in this forum too !!

 

 

 

 

 

 

 

 

..

Hello

 

I am a newbie does Helios software work on windows 10. I can GEt the Helios editor up and running but not the run time version. Any help would be gladly appreciated

 

Gary or snowman_one

[Mule]

I used to be able to get Helios to work a long time ago and it is a fantastic tool.

 

Does anyone know where I can get a step by step guide or video on how to do it correctly?

 

I need to be told like a 4 year old on how to do this. It seems I am not the only one. If there is something like this in a document I will gladly make a video to help others out if that's the case.

 

Cheers!

[MackM2]

Thought it was just me but a updated video would be great.

[dureiken]

Hi there

 

 

thanks for your awesome work capt !

 

 

Could some users post their setup default view ? I don't know how to setup my main view ?

 

 

Thanks

[mhe]

Ok, so I have it running ALMOST perfectly now. However, the AMPCD still gives me a headache. I tweaked the MDG_strokesDefs.lua with the values recommended in https://forums.eagle.ru/showpost.php?p=3555460&postcount=117 and that works great for the DDIs.

 

However, to affect the thickness of the AMPCD fonts, I have to tweak other values in the same file:

 

-- Currently is used for DMC generated fonts black outline
DMC_outline_thickness = stroke_thickness * 3
DMC_outline_fuzziness = stroke_fuzziness * 0.5
DMC_stroke_thickness  = 0.4
DMC_stroke_fuzziness  = 0.18

 

The values themselves are not the issue here, I can get these to be ok, my big gripe is that if I optimize for values that look good on the export, they look like crap on the 3D cockpit view and vice versa. Is there a way to have a nicely readable AMPCD both on the touchscreen and in the 3D cockpit at the same time?

 

Running a 4K main screen and a 1080p touch underneath it.

[dureiken]

Hi Capt,

 

 

is that normal that when I put your script folder in Saved Games, I loose 15 fps on my DCS ?

I tried on both computers, one with helios (but it's the same without) and another one, a laptop with just DCS

 

 

THanks

[Animal451]

YEAHAAAA

it worked mate

thanx

 

Sorry, hadn't checked back in a while but I'm glad it worked . . .

[Tomcat]

Sorry, hadn't checked back in a while but I'm glad it worked . . .

 

Sorry but after one update it sucks again.And never did it .

[Animal451]

Sorry but after one update it sucks again.And never did it .

 

Unfortunately I have the same issue. I'm unable to get the IFEI, UFC, or RWR to work anymore . . .

 

If I do get it to work I'll let you know what I did!

[aarenas52]

Please help me

 

Can someone help me? I did the install correctly but the instruments do not work./ The left and right MFD are exported properly so are the IFEI and UFC are also exported properly. The gauges do not work and neither does the jettison select buttons to the left oof the IFEI.

 

am using a touch screen (planar PXL 2230MW) and the screen works well in normal use but when i run helios i cannot use the buttons or knobs on it. It is properly calibrated and i already used the touch screen configuration in the Helios manual.

 

I linked my DCS log maybe someone can help me out? This is my first time trying to set up dual monitors especially with a touch screen support. I already went though captain's trouble shooting and i triple checked the folder locations. No luck. I don't know how to read .lua files if not i would try to make it work.

 

 

 

https://drive.google.com/open?id=1vLvF17o4YnfVgRhdNf8ljo3pk3jXABYk

 

thanks in advance!

[Capt Zeen]

TROUBLESHOOTING:

 

 

Wen you install a Helios profile, and you got a problem, try to identify exactly what happens.

Usually two issues can show up:

 

1 - The gauges, switches, lamps, etc, don't work

 

2 - The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work.

 

 

In the FIRST case: The gauges, switches, lamps, etc, don't work

 

Helios is probably not getting the DCS info needed, and thats because the export.lua is not doing his job. So...

 

- check if the export files are you using are the correct ones

- check if the place where you installed is the correct one:

Export.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\

HelioCore.lua and HeliosExport.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\Helios\

- then double check again !

- and of course, always use my last export files.

 

If you are using a system with more than two monitors,

- check the FAQ on the site. There is a bug on Helios that can asign a incorrect monitor to all bindings on the profile. There you got a solution for that.

 

If everything looks correct with the export files and still no joy,

- run a mision, and exit DCS,

- then check the dcs.log in savedgames/dcs/logs and look for errors in the export.lua . If something wrong happens in the export.lua the log tell you where to look at.

 

If you are using other tools with Helios, like: Simpleradio,Tackview DCS-bios etc, you can try to change the order of the lines in the export.lua. Those ones do not give problems, but some tools can, so give it a try.

 

 

In the SECOND case: The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work.

 

Ok, this is important to know, Helios do not export the viewports, is DCS who do that.

 

Some DCS modules are ready to export some of his viewport, but not all of them. That's the reason we need to change some .luas to make that module ready to export the viewports.

 

In the F18 case, and at this date ( 29/Aug/2018 ), only the 2 DDIs and the AMPCD are ready to export. The IFEI, RWR and UFC are not, so we need to overwrite those .luas with other ones ready to export viewport.

 

Usually, in my profile packages you got everything you need to do that operation in a folder called monitor configuration. So...

 

- Check if you installed the files in the correct place. I recomend to you use JSGME or OVGME to do the job, because in every DCS update those files are rewriten again

- Then edit the MonitorSetup file to adjust the viewports to your monitor configuration. (2_monitors-FA18C.lua )

- In DCS options, put your max resolution ( this is the total of your monitor resolutions in horizontal and vertical, for example two monitors 1920x1080 placed in horizontal layout, the total resolution is 3840x1080 )

- In DCS options, uncheck full screen option

- In DCS options, select the monitorsetup file to use (the one your just edited)

 

 

 

IMPROVING THE LINES QUALITY IN THE EXPORTED VIEWPORTS

use this information to improve the lines visuals...

 

https://forums.eagle.ru/showpost.php...&postcount=117

 

from my discord channel, by Kudox:

 

"Hi all this is what i discovered on MDG export . The wire solution looks terrible. set the MDI_init.lua for default . the file you what to modify is

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua . The draw is used for 3d cockpit and exported MDG . modify as a balance between the two . Here are my defaults that work for me

stroke_thickness = 0.5

stroke_fuzziness = 0.25

 

-- Currently is used for DMC generated fonts black outline

DMC_outline_thickness = stroke_thickness * 3

DMC_outline_fuzziness = stroke_fuzziness * 1.1

DMC_stroke_thickness = 0.5

DMC_stroke_fuzziness = 0.25

looks great now. Id ditch the wire draw.

I ll look into the RWR and UFC

UFC use the brightness control in cockpit works fine, RWR

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\indicator\RWR_ALR67_init.lua Modify shaderLineDefaultThickness = 3 see if that helps "

 

 

..

Edited November 23, 2018 by Capt Zeen

[Oraton]

A couple of quick questions,

 

Is there much of a performance hit when using helios?

Presumably it works with a touchscreen, are there any recommendations? I was considering the Magedok 15,6 Inch touch screen.

[aarenas52]

TROUBLESHOOTING:

 

 

Wen you install a Helios profile, and you got a problem, try to identify exactly what happens.

Usually two issues can show up:

 

1 - The gauges, switches, lamps, etc, don't work

 

2 - The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work.

 

 

In the FIRST case: The gauges, switches, lamps, etc, don't work

 

Helios is probably not getting the DCS info needed, and thats because the export.lua is not doing his job. So...

 

- check if the export files are you using are the correct ones

- check if the place where you installed is the correct one:

Export.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\

HelioCore.lua and HeliosExport.lua inside the folder \Users\yourusername\Saved Games\DCS.openbeta\Scripts\Helios\

- then double check again !

- and of course, always use my last export files.

 

If you are using a system with more than two monitors,

- check the FAQ on the site. There is a bug on Helios that can asign a incorrect monitor to all bindings on the profile. There you got a solution for that.

 

If everything looks correct with the export files and still no joy,

- run a mision, and exit DCS,

- then check the dcs.log in savedgames/dcs/logs and look for errors in the export.lua . If something wrong happens in the export.lua the log tell you where to look at.

 

If you are using other tools with Helios, like: Simpleradio,Tackview DCS-bios etc, you can try to change the order of the lines in the export.lua. Those ones do not give problems, but some tools can, so give it a try.

 

 

In the SECOND case: The diferent viewports from DCS, like DDIs IFEI, RWR, etc, do not work.

 

Ok, this is important to know, Helios do not export the viewports, is DCS who do that.

 

Some DCS modules are ready to export some of his viewport, but not all of them. That's the reason we need to change some .luas to make that module ready to export the viewports.

 

In the F18 case, and at this date ( 29/Aug/2018 ), only the 2 DDIs and the AMPCD are ready to export. The IFEI, RWR and UFC are not, so we need to overwrite those .luas with other ones ready to export viewport.

 

Usually, in my profile packages you got everything you need to do that operation in a folder called monitor configuration. So...

 

- Check if you installed the files in the correct place. I recomend to you use JSGME or OVGME to do the job, because in every DCS update those files are rewriten again

- Then edit the MonitorSetup file to adjust the viewports to your monitor configuration. (2_monitors-FA18C.lua )

- In DCS options, put your max resolution ( this is the total of your monitor resolutions in horizontal and vertical, for example two monitors 1920x1080 placed in horizontal layout, the total resolution is 3840x1080 )

- In DCS options, uncheck full screen option

- In DCS options, select the monitorsetup file to use (the one your just edited)

 

 

 

IMPROVING THE LINES QUALITY IN THE EXPORTED VIEWPORTS

use this information to improve the lines visuals...

 

https://forums.eagle.ru/showpost.php...&postcount=117

 

from my discord channel, by Kudox:

 

"Hi all this is what i discovered on MDG export . The wire solution looks terrible. set the MDI_init.lua for default . the file you what to modify is

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua . The draw is used for 3d cockpit and exported MDG . modify as a balance between the two . Here are my defaults that work for me

stroke_thickness = 0.5

stroke_fuzziness = 0.25

 

-- Currently is used for DMC generated fonts black outline

DMC_outline_thickness = stroke_thickness * 3

DMC_outline_fuzziness = stroke_fuzziness * 1.1

DMC_stroke_thickness = 0.5

DMC_stroke_fuzziness = 0.25

looks great now. Id ditch the wire draw.

I ll look into the RWR and UFC

UFC use the brightness control in cockpit works fine, RWR

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\indicator\RWR_ALR67_init.lua Modify shaderLineDefaultThickness = 3 see if that helps "

 

 

..

 

DCS. Log file: https://drive.google.com/file/d/1vLvF17o4YnfVgRhdNf8ljo3pk3jXABYk/view?usp=drivesdk

 

Thanks Capt. I already followed those instructions. But still nothing. I attached my DCS log above, do you think you can take a look ay it for me? I don't know how to read it or what exactly i am looking for.

 

Also does Helios evem work with DCS 2.5 beta? Or should i definitely be using the normal one? I wonder if that is an issue.

Edited November 23, 2018 by aarenas52
Adding link file.

[Capt Zeen]

Your dcs.log dont show any problem with the export.lua, so the problem can be on the profile . Send me your profile, after doit the reset monitors.

[aarenas52]

I am not sure if you mean the .lua or the helios profile so i attached both. Helios file is in the google drive link. I threw in the DCS log as well because I changed monitors but i already followed your trouble shooting tips and nothing :/ dont know if this time around i got a new error.

 

So i did make a few changes. I installed table DCS world and uninstalled helios.

 

First thing i did was download your profile and download helios according to your instructions.

 

I followed it to the foot of the letter with the new DCS world install. So helios is fresh as well. I also completely deleted DCS beta to be safe.

 

My new monitor setup is 3840 x 3600 (3840x2560 tv and a 2560x1440 screen under it!)

 

 

https://drive.google.com/open?id=1jEGP3rTK84EqOlNruwt8faUvTSvNF-W1

 

 

 

UPDATE/EDIT: Ok so i was messing around and before i do anything else, where do i install the export.lua file? I put it in D:\DCS World\Scripts. I did back up the original. Anyway i was looking at DerekM write up for helios with a touch screen monitor (which I got rid of) but he puts the export file under C:\Users\[username]\Saved Games\DCS\Scripts

 

is that were I put mine as well? and leave the original in D:\DCS World\Scripts? Or do I place it in both?

 

I am an idiot if this is the issue lol.

 

UPDATE/EDIT #2: So I tried following DerekM write up and it did not work either. So i placed the export.lua under C:\Users\[username]\Saved Games\DCS\Scripts and deleted it over in D:\DCS World\Scripts but that didnt work. I tried the script only in D:\DCS World\Scripts and deleted from C:\Users\[username]\Saved Games\DCS\Scripts but that didn't work either. Lastly I tried having the same export.lua in both C:\Users\[username]\Saved Games\DCS\Scripts and D:\DCS World\Scripts but that did not work either. I'm out of ideas Capt. the export.lua I tired was the one DerekM generated via helios. I still; have yours and i guess i can copy it to C:\Users\[username]\Saved Games\DCS\Scripts and see if being there helps. but i doubt it.

2A monitors-FA18C 1440p.lua

Edited November 23, 2018 by aarenas52

[RightStuff]

Is there much of a performance hit when using helios?

Presumably it works with a touchscreen, are there any recommendations? I was considering the Magedok 15,6 Inch touch screen.

 

Performace hit: Depends on your rig, but all over all it‘s not that big that it will be showstopper.

 

Touchscreen: Look for at least 20“-22“.

The DDI / UFC buttons are even on my 20“ screen a little bit too tiny.

But that‘s only my very personal look and feel.

[Oraton]

Touchscreen: Look for at least 20“-22“.

The DDI / UFC buttons are even on my 20“ screen a little bit too tiny.

But that‘s only my very personal look and feel.

 

OK, that changes things! I was going to have the touchscreen at arms length so I guess I'll need a much bigger display.

Thanks, RightStuff.

[oldracoon]

Is there a way to make exported DDIs and other indicators always be bright at their max and not be affected by cockpit controls?

[Padonis]

After switching on the JHMCS - HMD, its lines are very poorly visible, can anyone correct it already? I tried to change the values ​​in the "HMD_init" file

shaderLineDefaultThickness = 1.8 , shaderLineDefaultFuzziness = 1.5 , but it does not work.

I know that it does not really match HELIOS, but I have no idea where to ask.

Edited December 6, 2018 by padonis