Helios help

[AstroEma]

HI all,

 

I have been trying to configure helios to work with DCS but I need some help please.

 

Installed Helios latest built and Capt.Loz 2.1 profile. (I am running 3 27" 1920x1080 screen and another screen to the right 24" 1920x1200)

 

I have pointed Helios to the DCS10C installed directory. This did not create an export.lua file apparently. So I found the correct export.lua file and copied it over the original one in the DCSOpenBeta/Scprits (should I leave it there??)

 

Helios does not read any of the A10C gauges, nor is it exporting the Digital Clock (testing only this one for now).

 

I also replaced the MonitorConfig file with a new one which should export the Viewports. But it does not. I tried changing the names of the ViewPort (i.e DIGIT_CLOCK to DIGIT_CLK) but made no difference.

 

Probably something stupidly easy that I am not doing but its driving me crazy.

 

Thank you very much.

 

Cheers,

e

Edited March 6, 2016 by AstroEma

[Rickety]

HI all,

 

I have been trying to configure helios to work with DCS but I need some help please.

 

Installed Helios latest built and Capt.Loz 2.1 profile. (I am running 3 27" 1920x1080 screen and another screen to the right 24" 1920x1200)

 

I have pointed Helios to the DCS10C installed directory. This did not create an export.lua file apparently. So I found the correct export.lua file and copied it over the original one in the DCSOpenBeta/Scprits (should I leave it there??)

 

Helios does not read any of the A10C gauges, nor is it exporting the Digital Clock (testing only this one for now).

 

I also replaced the MonitorConfig file with a new one which should export the Viewports. But it does not. I tried changing the names of the ViewPort (i.e DIGIT_CLOCK to DIGIT_CLK) but made no difference.

 

Probably something stupidly easy that I am not doing but its driving me crazy.

 

Thank you very much.

 

Cheers,

e

 

The export.lua file should be placed in C:\Users\USERNAME\Saved Games\DCS\Scripts. I'm not sure if you have the beta or alpha installed(I have both). Mine looks like this for the alpha: C:\Users\Rob\Saved Games\DCS.openalpha\Scripts. I created a "scripts" folder for both alpha and beta and placed the "export.lua" there and it works for both.

 

If you don't have a "scripts" folder in your "Saved Games/DCS" folder, create one and place the export.lua there. VERY IMPORTANT

 

Also check this page(but don't worry about the TARS stuff). http://forums.eagle.ru/showthread.php?t=102034

 

It states: The change introduced with DCS World 1.2.3.9871 is that the file "C:\Program Files\Eagle Dynamics\DCS World\Config\Export\Export.lua" and config.lua in the same directory is ignored by DCS, but used by both TARS and HELIOS. Instead DCS now looks for "C:\Users\USERNAME\Saved Games\DCS\Scripts\Export.lua".

 

You can also try to use the "export.lua" file that came with Capt.Loz 2.1 profile and place that in the "scripts" folder you created/have in the saved games folder. This worked for me.

 

Try to run the game without starting the Helios profile you created if you haven't tried this already. This will show the all of the viewports on your other monitor. The "digital clock" may be hidden behind Helios and not in the correct spot?

 

My Digital Clock looks like this from my monitor.lua:

 

 

}

DIGIT_CLOCK =

{

x = 2284;

y = 667;

width = 80;

height = 85;

}

 

 

Hope this helps.

Edited March 6, 2016 by Rickety

[AstroEma]

Thanks Rickety,

 

I was actually missing the export.lua file in the Scripts folder inside SavedGames etc. Appreciate very much your help.

 

It seems though that the gauges move at a very low frame rate. Like 1-2 FPS maximum. Any help on that?

 

Thanks!

[Rickety]

Thanks Rickety,

 

I was actually missing the export.lua file in the Scripts folder inside SavedGames etc. Appreciate very much your help.

 

It seems though that the gauges move at a very low frame rate. Like 1-2 FPS maximum. Any help on that?

 

Thanks!

 

You're welcome.

 

Sorry, can't help with the gauges. I have the same issue myself.

[AstroEma]

No worries. Thanks Rickety!

[AstroEma]

anyone else?

[AstroEma]

Well, digging into it I found out what the problem is:

If I view the aircraft from outside using F3 and No ground is visible in the monitors view, then the gauges and instruments in helios update in real-time

If the ground comes into view, they start lagging badly.

The peculiar fact is that I get 45-50 fps average in cockpit.

 

Any idea for a fix?

[BravoYankee4]

What is the FPS level when this happens? - Just realized you provided that info already.

Seems that the data feed is affected when the system is to busy rendering the scenario...

I think there is a value for the poll frequency (or something like that) that can be altered.

Edited March 11, 2016 by BravoYankee4
Added comment

[AstroEma]

Thanks for your feedback BravoYankee.

 

I changed the gExportInterval to 0.0067 without success.

 

I also tried to disable the cockpit but still gives me the same problem.

[AstroEma]

bump! Still hoping someone has a solution. Otherwise I will have to ditch Helios.

[BravoYankee4]

bump! Still hoping someone has a solution. Otherwise I will have to ditch Helios.

Try with HawgTouch or Ikarus and see if you have the same problem there. Then you can sort out in what end you have the issue.

[Mick F]

What's your system spec?

[AstroEma]

Thanks guys. Any links to Hawgtouch or Ikarus? EDIT: Found them.

 

My specs are: Intel Skylake 4.5ghz, 8gb Ram, 250gb SSD M2, 1Tb HDD, GTX970G1

Edited March 14, 2016 by AstroEma

[AstroEma]

Quick update:

I installed HawgTouch and it works, in realtime.

That means that there's something wrong in the configuration of the export scripts or export lua in Helios.

 

Still looking for a solution. While Hawgtouch is nice, it is certainly not as advanced as Helios is.

Edited March 17, 2016 by AstroEma
spelling

[Mick F]

Makes sense. My system is lower specs than yours and works fine. I do find Helios can be a little slow to response at busy airbases but is fine after takeoff so I suspect system limitations on my side.

[BravoYankee4]

Quick update:

I installed HawgTouch and it works, in realtime.

That means that there's something wrong in the configuration of the export scripts or export lua in Helios.

 

Still looking for a solution. While Hawgtouch is nice, it is certainly that advanced as Helios is.

 

What are you referring to as more advanced in Helios?

[AstroEma]

The interface and controls of instruments/gauges seems to me, just from using it half an hour or so, not that intuitive compared to Helios which has a nice GUI.

Might be because I have not explored Hawgtouch deeply.

 

I was playing around a bit more with it and now the gauges are not moving at all. I have checked the export.lua and the settings are correct (port and interface)

 

Also I was reading in another thread that we should not touch the enable/disable button in the control panel? Mine says disabled now and how to I enable export??

[BravoYankee4]

The interface and controls of instruments/gauges seems to me, just from using it half an hour or so, not that intuitive compared to Helios which has a nice GUI.

Might be because I have not explored Hawgtouch deeply.

 

I was playing around a bit more with it and now the gauges are not moving at all. I have checked the export.lua and the settings are correct (port and interface)

 

Also I was reading in another thread that we should not touch the enable/disable button in the control panel? Mine says disabled now and how to I enable export??

 

Yes, then I understand. The successor, Ikarus, that will be released shortly is a lot better in that aspect.

 

Regarding that enable/disable function I think I had to replace the export files again to get it working...

[AstroEma]

Will try replacing the file and give it another go!

Will report back.

[Capt Zeen]

Hello AstroEma

 

Try Helios again using my export.lua and let us know if the problem persist.

You can find it in www.captzeen.com in the download section

[AstroEma]

Hello Capt. Zeen,

 

Yep I already tried it and nothing changed unfortunately.

I am starting to think that it might be a problem related to having only 8Gb oF ram?

[Rickety]

Hello Capt. Zeen,

 

Yep I already tried it and nothing changed unfortunately.

I am starting to think that it might be a problem related to having only 8Gb oF ram?

 

Hi AstroEma. It might not be the ram. I had 8Gb in mine and the gauges were slow. I recently upgraded my rig to 32Gb and it is still the same.

 

In older versions of DCS the gauges in the A-10C were flawless for me but not so well with the newer versions of DCS. For my experience with Helios and the gauges not working at all, it always came down to something wrong with the export.lua file.

[AstroEma]

Hello again,

 

I finally figured out what the problem is: MSAA setting in DCS.

Even at 2X brakes the real-time update in Helios.

I am now using the ExportScript lua file from Hawgtouch though.

 

In any case MSAA is the problem.

[Hollywood_315]

Same problem here - occasional (very) low gauge refresh rates in HELIOS with DCS 1.5/2.0oa while it used to work well before. My rig is completely op to spec so no bottlenecks there.

 

If it's MSAA that's causing it then switching it off seems like too much of a sacrifice to fix it.

[kadda]

hello everybody, is it possible to do the same thing with the L-39c/za ???