Helios -> DCS World 1.5

[OzDeaDMeaT]

I can't seem to get any of my A10C touch screen controls working since 1.5. Anyone have Helios working with 1.5 at all?

[SEDUNDERI]

I got it to work following this

http://forums.eagle.ru/showthread.php?t=125195

The colour if the countermeasure view ports is not correct but readable

[sobe]

In order to get Helios to have the gauges work properly in 1.5, don't you have to redo the setup in Helios to direct it to 1.5 and somehow redo the Export file also in 1.5? I have only managed to get the viewports working correctly in 1.5 for the Loz A10 profile but I have not yet fiddled with the gauges as I could not figure out how to keep my Helios 1.2 setup at the same time as going to a 1.5 setup. Does any of this make any sense?

[slicker55]

Helios people,

 

My world has fell apart tonight..

 

Just starting to test DCS 1.5 Beta after resetting controllers etc.

 

I have been using Helios for over 12 months and it has worked flawlessly under Windows 7 and 10 (64 bit).

 

Tonight, I had just saved some work I had been doing on a DCS profile and closed the Helios editor. I tried to open the control centre but I just get a pop-up message which says the program has stopped working

 

I tried to re-open the editor - again, it won't run - actually nothing happens - no message - just nothing.

 

So, I tried uninstalling helios and reinstalling (no joy), there's only been one windows 10 update in the last few days so I tried uninstalling that (no joy).

 

So, now wondering if this is a Windows 10 issue or has DCS 1.5 beta installed something which conflicts with Helios (thinking directX 11)..

 

reaching out for some idea's before jumping in with both feet, uninstalling DCS 1.5, then, if no joy going back to windows 7. (that will have to wait for another day - been on it too long already and need to be on the ball to tackle that minefield)...

 

 

 

 

..

Edited October 31, 2015 by slicker55

[OzDeaDMeaT]

Helios is not outputting an Export.lua

[slicker55]

Helios is not outputting an Export.lua

 

..

 

 

Are you saying this is what's causing my problem or are you saying you've found something else?

 

 

 

 

..

Edited October 4, 2015 by slicker55

[Capt Zeen]

My first experiences using Helios width DCS 1.5 (still in windows 7):

 

- I was abble to run my mi-8 helios profile whidhout problems. Everythings work the same way.

- I was abble to run my ka-50 helios profile whidhout problems. Everythings work the same way.

 

- I was abble to continue working on the helios profile editor, implementing all the new 1.5 features of the mi-8. No problems at all.

 

- I was forced to change some export.lua data to fix the uv26 digits in the mi-8 profile. In the 1.2.16 version the indicator you need to export is the 4, and in the 1.5 version the indicator changed to 5.

 

i can export the abris and the Skhival too:

 

 

still need to test pvi digits and ekran

 

..

Edited October 4, 2015 by Capt Zeen

[SEDUNDERI]

I got my A10C working properly but I realize using the Capt Zeen profile for F-15 and P-51 I cannot get the buttons to work in these planes. The gauges works well on all planes but not the input? (except for A10C)

 

What could be wrong? I am quite new into this so any input is highly appreciated.

 

Thanks

[Hippo]

I can't seem to get any of my A10C touch screen controls working since 1.5. Anyone have Helios working with 1.5 at all?

 

It is working for me (only tried A-10C so far). However, I am getting VERY ANNOYING stutters every few seconds when I turn Helios on. Is anyone else seeing this / have any suggestions how to fix it? ** EDIT ** Stutters seem (could be intermittent) to go away as long as I start Helios before starting DCSW (and don't start it whilst already flying).

 

I have just done a clean install of Windows 10 (I was on W7 until a few days ago) and of DCSW 1.5.

 

I installed Helios, then copied my old "my documents\helios" folder from my W7 backup.

 

I also had to copy my old export.lua to the following location:

 

"C:\Users\USER_NAME\Saved Games\DCS.openbeta\Scripts\Export.lua"

 

(Note that I had to create the Scripts folder).

 

I use the export.lua offered in the following thread:

 

http://forums.eagle.ru/showthread.php?t=97222

Edited October 5, 2015 by Hippo

[sobe]

Hippo

I tried to use the Loz A10-C profile for Helios in beta 1.5 but no joy. I created the scripts folder and put in the export file that I am using for DCS 1.28, but the gauges would not work. I had just copied what I used in 1.28 into the appropriate JSGME folders and changed the location of the Helios profile to the new open beta. what did I forget?

 

Perhaps someone would be kind enough to provide a little step by step instructions on how to go from 1.28 to 1.5 with the Loz profile. Thanks.

Edited October 5, 2015 by sobe
added last sentence

[Hippo]

Hippo

I tried to use the Loz A10-C profile for Helios in beta 1.5 but no joy. I created the scripts folder and put in the export file that I am using for DCS 1.28, but the gauges would not work. I had just copied what I used in 1.28 into the appropriate JSGME folders and changed the location of the Helios profile to the new open beta. what did I forget?

 

Perhaps someone would be kind enough to provide a little step by step instructions on how to go from 1.28 to 1.5 with the Loz profile. Thanks.

 

I would suggest you try what I suggest above. Not sure about JSGME (I think this is a patching tool), which I don't use. I'm also using my own profile.

 

To summarise, install a clean Helios, copy the loz profile to my documents/helios (IIRC this profile might need a bit of extra setup, see the readme), and copy the export.lua (try the version I suggest above) to the Scripts folder in Saved Games.

[sobe]

I have redone everything and while the viewports work correctly, I cannot get any of the gauges or touch buttons to work in the Helios profile on my second screen. I am using Loz's profile and everything works nicely in 1.28.

[sobe]

Still no joy in getting helios to run with the A10-C. I know that I am making a silly error, but I just don't know what it is. For example, in the profile editor for helios, I have inserted the following in the A10C setup box:

d:\Program Files\Eagle Dynamics\DCS World OpenBeta

 

Is that correct?

[Capt Zeen]

Still no joy in getting helios to run with the A10-C. I know that I am making a silly error, but I just don't know what it is. For example, in the profile editor for helios, I have inserted the following in the A10C setup box:

d:\Program Files\Eagle Dynamics\DCS World OpenBeta

 

Is that correct?

 

Sobe, this afternoon i am going to implement the caploz a10C profile in my 1.5 beta. I let you know how it goes and the steps to do it.

[sobe]

thanks

[Cloudie]

Hey guys, I'm using Loz and I'm almost completely done with the transition from 1.28 to 1.5

 

What I did was simply copy the Export.lua, Init luas and MonitorSetup I was using before into the same structure on the beta folder, then I changed the resolution and the monitor setup ingame and everything is working same as before... all is perfect except the extra viewports (RWR, countermeasures, clock, etc as you can see in the attached files)

The ports are looking wrong and the background is no longer black, if I hide Helios I can see a bugged out still frame with extra MFDs and ports (third screenshot).

Any idea about why it's doing that in 1.5?

 

At least everything is working properly, if anybody needs help to get until this point just ask :)

[sobe]

Cloudie

Besides my Helios touchscreen not working, I also have viewport issues like you do.

RWR-hard to read with a white background now

CMS-hard to read with green type

UHF-not working

Clock-not updating the time. the time seems to be correct when started, but does not update.

[Capt Zeen]

As Cloudie did, i copied the export.lua. monitor configurations, and init luas.

I just run the Caploz profile and it works.

 

I have the same problems width the viewports.

[sobe]

What did you put in the setup box in Helios?

I put

d:\Program Files\Eagle Dynamics\DCS World OpenBeta

 

Boy am I mssing something simple as I cannot get my second screen to work with the Loz profile. I will work on it again.

 

Could it be that I am also running 1.28 and just changing the setup box in Helios?

[Cloudie]

I didn't touch anything in the Helios setup program, just started the little panel as usual like I did with 1.28, which is still installed and working.

 

Just to check, the Export.lua we are talking about is the one in

C:\Users\<UserName>\Saved Games\DCS.openbeta\Scripts

right? Not the one in a Program Files\Eagle Dynamics\.. folder.

That's the key to make the touchscreen and gauges to work; if it worked for you in 1.28 it should continue to do so.

 

About the viewports if we all have the same problem then it's a common issue, hmm...

Helios or not the not-rendered part of the screen is a mess now; in 1.28 it was just black.

Hoping there will be a solution soon, otherwise is still very playable and I enjoy the revamped graphics a lot! (except the fps drain that is any kind of depth of field effect lol)

[sobe]

Cloudie and Capt Z

 

Finally I got the export to work and the gauges now work. HOWEVER, besides all of the other errors noted above, my MFD screens were really screwed up. The TAD had no labels and the Mav was superimposed on the TGP. I had made no changes in the monitor config file from 1.28 to 1.5.

At this point, some serious work has to be done on the Loz profile. Too bad.

 

UPDATE: WHEN I RAN THE MISSION AGAIN, BOTH MFD'S WORKED FINE. THIS IS GOING TO BE A FUN YEAR.

Edited October 7, 2015 by sobe
UPDATE

[Cloudie]

That's good to hear, then!

Let's see if a solution for the other viewports and the background will come to us, too :helpsmilie:

[GeneralDynamics]

I was hoping to be able to triumphantly post a solution to the viewport problems, but I got nothing after many nights of trial and error. So, I'll throw my hat in the ring and report that I have the same problem with viewports in DCSW 1.5. I have one main screen and one touch screen for Helios and exported viewports. Main screen performs fine, viewports are present on the touch screen and in the correct position, but they're being rendered on top of some static terrain display with other miscellaneous viewports showing up here and there. The MFCDs render properly, but all other viewports are screwed up in one way or another, either barely readable or not functioning at all. I've included screen prints of how the exports to the touch screen looked under DSCW 1.2 and how they look now under DCSW 1.5. Initially I tried simply copying my export, init and monitor config luas over from DCSW 1.2 and first had the problem. Since then I've tried a number of different export and init lua configurations suggested by others, and no matter what I do the same problem persists throughout.

 

This appears to be a remaining common problem shared by several. Maybe I missed it, but I don't see a clear answer regarding whether anyone has Helios, exported viewports and gauges ALL working correctly under 1.5 with everything rendered properly?

[RightStuff]

I'd just like to report that I have the same

graphical issues with the viewports (not: MFDs) like Cloudie and GeneralDynamics.

[Mewle]

Cloudie and Capt Z

 

Finally I got the export to work and the gauges now work. HOWEVER, besides all of the other errors noted above, my MFD screens were really screwed up. The TAD had no labels and the Mav was superimposed on the TGP. I had made no changes in the monitor config file from 1.28 to 1.5.

At this point, some serious work has to be done on the Loz profile. Too bad.

 

UPDATE: WHEN I RAN THE MISSION AGAIN, BOTH MFD'S WORKED FINE. THIS IS GOING TO BE A FUN YEAR.

 

Hi Sobe,

 

What was it that fixed it for you? I can't get the gauges to work at all.

 

Mewle