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

[Snacko]

Can anyone shed some light on or point me in the correct direction, as I can not seem to get the side panels to work on the F18 beta 2 profile.

 

Have you clicked on the little green buttons near the center of the profile? And the panels do not appear? Which version of Helios are you using?

[rossi_69]

Thanks Snacko sometimes you cant see the woods for the trees (or I am just stupid)

been trying all round the edges and did not see those right there. :)

[Snacko]

Thanks Snacko sometimes you cant see the woods for the trees (or I am just stupid)

been trying all round the edges and did not see those right there. :)

No Problem. Using the Editor, I moved them to the left side and made them bigger. I am using the _b profile and it has about 1.5 inches of blank space on each side.

[Fakum]

This profile works just fine for me, however, I already have a "MonitorSetup" config file that allows alot of other different modules to use 1 single file for Helios, I just want to ADD the F-18 to it, but I did that and its not working. Can someone post up their Monitor Config.lua if you have the F-18 and other modules in the same file. I will then likely see what I am doing wrong.Thanks

[flx54]

+1 here

 

I am Using an 2k as main Monitor and just got a 22" Ilyama touch monitor especially for Helios. I got the profile for F18 but i only see the Main Panel on the 22" without any "interaction" and the main DCS view on my large 32" 2k monitor. (Instruction where to put the profile files was googled, as i didnt find it in Capt. Zeens instructions )

 

I went through the installation guide, substituted the export.lua file into the right place but no success. Anyone here with a "Helios Guide for Dummies"?

 

I believe, it is an outstanding piece of software if i get it to work right and will donate as soon as i get it working as i expect it to do... :thumbup:

 

Many thanks!

[Snacko]

This profile works just fine for me, however, I already have a "MonitorSetup" config file that allows alot of other different modules to use 1 single file for Helios, I just want to ADD the F-18 to it, but I did that and its not working. Can someone post up their Monitor Config.lua if you have the F-18 and other modules in the same file. I will then likely see what I am doing wrong.Thanks

 

What works, what doesn't? Every other aircraft works, but none of the FA18 viewports don't show up?

 

The only problem would probably be if any of the viewport names were duplicated. Each one has to be unique. For example, you cannot have RIGHT_MFCD defined twice. Other than that, it should work.

[Snacko]

+1 here

 

I am Using an 2k as main Monitor and just got a 22" Ilyama touch monitor especially for Helios. I got the profile for F18 but i only see the Main Panel on the 22" without any "interaction" and the main DCS view on my large 32" 2k monitor. (Instruction where to put the profile files was googled, as i didnt find it in Capt. Zeens instructions )

 

I went through the installation guide, substituted the export.lua file into the right place but no success. Anyone here with a "Helios Guide for Dummies"?

 

I believe, it is an outstanding piece of software if i get it to work right and will donate as soon as i get it working as i expect it to do... :thumbup:

 

Many thanks!

Here is a 54 page guide. It's 4 years old and uses a different profile for the A10c. But the basics of the setup have not changed, so it should have some answers. The only difference is some profiles may have a mod to install to create additional Viewports if DCS does not have all of them. Some profiles may have a mod and some may not need one.

 

You are welcome to PM me if you would like more help.

Edited January 9, 2019 by Snacko

[Fakum]

What works, what doesn't? Every other aircraft works, but none of the FA18 viewports don't show up?

 

The only problem would probably be if any of the viewport names were duplicated. Each one has to be unique. For example, you cannot have RIGHT_MFCD defined twice. Other than that, it should work.

 

 

When I run the CaptZeen Monitor config file that he includes in his Profile, it works just fine. I have not used Helios in about 1 year, but when I did, I had a monitor config file that incorporated many modules, I have not run any of those in about a year so I honestly dont know if they work because I uninstalled the older version of Helios a couple of weeks ago to install the latest version of Helios. All I was trying to do is copy over the data from CaptZeens F18 Monitor Config file to my older one, but there are Lines in the old Monitor Config fille that IDENTIFY each Specific Aircraft. I tried to figure out what that line should state, but without looking at someone elses file, Im not sure. Thats all I need to see, is someone elses file that has the F18 and at least one other module.

[Snacko]

Sorry, I have a file like that, but haven't used it in about a year also.

 

If you are still using that function reconfigure_for_unit(unit_type), it doesn't work anymore AFAIK.

 

You may have just left out a comma or something like that. I've done that before and it took a long time to find.

 

Here is my old one that doesn't use that function(). It works with a few aircraft that do not duplicate viewports. I hesitate to share it because it relies on viewport mods that others may not have, so they wouldn't work. It's just something I slapped together a long time ago. It worked when I was using it back then. Sorry I cannot help more.

Helios Viewports by Snacko NO FUNCTION.lua

[Fakum]

Thanks Snacko, the unit comment made me realize I was using the obsolete file, I found the last version that IO used a year ago and pasted the F18 info into it from Capt Loz and it exported fine it seems at this time. I am posting it up in case anyone else is having difficulty. Thanks

 

 

 

_ = function(p) return p; end;

name = _('Fakums All Helios 2');

Description = 'Export ALL Viewports in one LUA file.'

 

 

Viewports =

{

Center =

{

x = 0;

y = 0;

width = 2560;

height = 1600;

viewDx = 0;

viewDy = 0;

aspect = 1.6;

}

}

 

 

-- ┌─────────────────────────────────────┐

-- │ A 1 0 C - Loz A10c profile. │

-- └─────────────────────────────────────┘

ED_A10C_LEFT_MFCD = --

{

x = 2627;

y = 120;

width = 445;

height = 445;

}

 

ED_A10C_RIGHT_MFCD = --

{

x = 3968;

y = 120;

width = 445;

height = 445;

}

 

ED_A10C_CLOCK = --

{

x = 3037;

y = 826;

width = 125;

height = 125;

}

 

ED_A10C_RWR = --

{

x = 3160;

y = 161;

width = 175;

height = 175;

}

 

ED_A10C_CMSC = --

{

x = 3421;

y = 140;

width = 216;

height = 48;

}

 

ED_A10C_UHF_REPEATER = --

{

x = 3205;

y = 695;

width = 125;

height = 30;

}

 

ED_A10C_CMSP = --

{

x = 3637;

y = 192;

width = 267;

height = 62;

}

 

ED_A10C_UHF_PRESET_CHANNEL = --

{

x = 3304;

y = 476;

width = 33;

height = 33;

}

 

ED_A10C_UHF_FREQUENCY_STATUS = --

{

x = 3190;

y = 562;

width = 135;

height = 35;

}

 

 

KNEEBOARD =

{

x = 1920;

y = 0;

width = 526;

height = 789;

}

 

 

-- ┌─────────────────────────────────────────┐

-- │ K A - 5 0 for Capt. Zeen's profile.

-- └─────────────────────────────────────────┘

--SHKIVAL

ED_KA50_Shkval =

{

x = 2572;

y = 7;

width = 801;

height = 646;

}

 

--ABRIS

ED_KA50_ABRIS =

{

x = 3897;

y = 0;

width = 584;

height = 845;

}

 

-- PVI800

ED_KA50_PVI =

{

x = 2599;

y = 670;

width = 209;

height = 118;

}

 

--EKRAN

ED_KA50_Ekran =

{

x = 3721;

y = 961;

width = 158;

height = 112;

}

 

--UV26

ED_KA50_UV26 =

{

x = 3451;

y = 542;

width = 190;

height = 67;

}

 

--CAUTION LIGHTS

ED_KA50_CautionLights =

{

x = 1920;

y = 0;

width = 700;

height = 700;

}

 

--

-- KNEEBOARD =

-- {

-- x = 1920;

-- y = 0;

-- width = 526;

-- height = 789;

-- }

 

 

 

 

 

-- ┌─────────────────────────────────────────┐

-- │ F-15

-- └─────────────────────────────────────────┘

 

 

 

-- Radar F-15C

RIGHT_MFCD = {

x = 2830;

y = 0;

width = 381;

height = 381;

}

 

-- ┌─────────────────────────────────────────┐

-- │ Harrier

-- └─────────────────────────────────────────┘

 

 

 

LEFT_MFCD =

{

x = 2732;

y = 425;

width = 388;

height = 383;

}

 

RIGHT_MFCD =

{

x = 3893;

y = 441;

width = 388;

height = 374;

}

 

ODU_base =

{

x = 2775;

y = 137;

width = 287;

height = 150;

}

 

UFC_base =

{

x = 3281;

y = 38;

width = 455;

height = 375;

}

 

UVHF_base =

{

x = 3167;

y = 725;

width = 450;

height = 355;

}

 

-- ┌─────────────────────────────────────────┐

-- │ F18

-- └─────────────────────────────────────────┘

 

--LEFT

LEFT_MFCD =

{

x = 2840;

y = 200;

width = 394;

height = 377;

}

 

--RIGHT

RIGHT_MFCD =

{

x = 3822;

y = 200;

width = 394;

height = 377;

}

 

 

-- RWR

F18_RWR =

{

x = 4051;

y = 730;

width = 184;

height = 184;

}

 

 

 

--AMPCD

CENTER_MFCD =

{

x = 3330;

y = 690;

width = 377;

height = 360;

}

 

--IFEI

F18_IFEI =

{

x = 2716;

y = 753;

width = 521;

height = 205;

}

 

 

--UFC

F18_UFC =

{

x = 3299;

y = 32;

width = 461;

height = 260;

}

 

 

UIMainView = Viewports.Center

 

Edited January 9, 2019 by Fakum

[Snacko]

You've got the LEFT_MFCD and RIGHT_MFCD in there several times. DCS will probably only use the first one or the last one every time. The others won't work. That's why we used that function before they broke it.

 

Sent from my Moto Z Play using Tapatalk

[Fakum]

I agree with you, oddly enough, when I last used this file about a year ago, those modules worked fine. Im not a coder, so I cant explain the functionality. I will have to run some tests but all I was trying to do at the moment was actually to get a common file to run the Huey and F18 for now. The others to follow at a later date. Maybe we cant do that anymore? Thanks for the advise though, I will peck at this over the weekend.

[flx54]

Here is a 54 page guide. It's 4 years old and uses a different profile for the A10c. But the basics of the setup have not changed, so it should have some answers. The only difference is some profiles may have a mod to install to create additional Viewports if DCS does not have all of them. Some profiles may have a mod and some may not need one.

 

You are welcome to PM me if you would like more help.

 

THX Snacko, will go through it!

[Fakum]

Well, a quick couple of tests proved problematic as you mentioned there Snacko. Are we stuck in the mud here where we need a separate monitor config file for modules? Later I will delete all others and try to complile for just the F18 & Huey and see how that works. I dont know what to do about the duplicate MFCD statements?

[Snacko]

I saw where you posted your original problem(combining monitorsetups) in another thread. And one reply said he had modded the game to rename some of the 'LEFT_MFCD' and 'RIGHT_MFCD' viewports for some aircraft. That is the only solution. You cannot have duplicate named viewports. Period. So, either look at his post. or combine as many as you can that dont' duplicate. And make other lua files for the rest.

 

And while your at it, go find that thread about the function that's broke, and bump it again! If that function worked it would solve this problem.

[Fakum]

Yes, I did see that, but I had no idea what he meant to be honest. Modded the game? Sounds pretty deep to me. And yes, I will try and find that thread you referred to, this is getting outside of the realm of the F18 now. Thanks Snacko

Edited January 10, 2019 by Fakum

[Fakum]

HUH! I did find that thread, but its read only?

 

 

https://forums.eagle.ru/showthread.php?t=170049

[Fakum]

Moving onto another matter, I have been unable to extract just the right & left DDI panels by themselves. I was in the midst of creating a new F18 profile that just has them, but they wont highlight by themselves to copy? I can do the UFC though? Is this because the DDIs are part of the entire front panel?

[slowmover]

I am trying to download Hellios but something is going wrong.File is broken?

[flx54]

Well, i had time to start my helios setup as described in the 50+ pages guide. Unfortunately Win10 does not match well (touch)monitor setup instructions as before. So that was a bit challenging.

Also i wanted to ask, is there a difference regarding Helios in (in all tutorials mentioned outdated) DCS 10C and DCS open beta?

 

 

For simplicity, i changed resolution of the 2k monitor to 1920x1080.(to match the touchscreen)

 

I am stuck at around page 40 So i decided to replicate everything with the A10C instead of trying to work on the F18C. Unfortunately the "Loz SM v2.1.rar" profile file is not available anymore.

 

So, because of my lacking knowledge, i am again stuck. :helpsmilie:

 

Isnt there a fully functional A10C profile around for 2 monitors? (adapted to the actual DCS Version ;) )

 

Would really appreciate just in order to eliminate one or other error produced by myself...

 

Thank you!

 

EDIT: Just worked with this tutorial and started to understand a lot concerning the monitor setup. Worth having a look for guys like me! https://www.digitalcombatsimulator.com/en/files/214771/

Now i even got it working with the F/A-18C . At this time modifying viewports but looking very very good!

Edited January 13, 2019 by flx54

[Snacko]

I'll try to answer some of these..

 

Well, i had time to start my helios setup as described in the 50+ pages guide. Unfortunately Win10 does not match well (touch)monitor setup instructions as before. So that was a bit challenging.

Also i wanted to ask, is there a difference regarding Helios in (in all tutorials mentioned outdated) DCS 10C and DCS open beta?

 

If you mean is there a difference between DCS regular stock game and DCS Open Beta for the Helios program? I have both installed. You have to put that export.lua file in the Scripts folder for each game. And if a profile has a mod to add additional viewports, you need to install that mod in each game. That's the only difference. When you run the Helios program, it sees whichever game you start automatically.

[Capt Zeen]

Hello all, i dont forget about the video tutorial, just need to assemble my new computer this week !

[flx54]

Good Luck with your new PC and many thanks for your outstanding piece of software! :thumbup:

[flx54]

I'll try to answer some of these..

 

 

 

If you mean is there a difference between DCS regular stock game and DCS Open Beta for the Helios program? I have both installed. You have to put that export.lua file in the Scripts folder for each game. And if a profile has a mod to add additional viewports, you need to install that mod in each game. That's the only difference. When you run the Helios program, it sees whichever game you start automatically.

 

Got it. Thanks!

[Tomcat]

Hello all, i dont forget about the video tutorial, just need to assemble my new computer this week !

 

İ wish for fun time for your new baby.

Hope dont get any problem to run Capt Zeen Helios Profile :megalol: