Jump to content

Recommended Posts

Posted

Hi there,

 

I decided to start a new thread because I've tried several topics in this forum, but maybe I've tried wrong topics.

 

So, my problem is that after a fresh install of DCS World 1.2.1. my Helios cockpit (A-10C) has stopped working.

 

I've been using Helios for 10 months now and everything worked fine. But after I've installed the new 1.2.1 version of DCS World, my gauges stopped working on my second monitor which is my 'cockpit'. I've enabled Aero in the sim, but nothing.

I made an uninstall and a clear reinstall (deleted all the folders in Documents and settings and in Program files).

I've created a new Helios file (after I've reinstalled Helios) from Loz vSM1.2 template. I've added the DCS-A10C interface and modded the install path for DCS World.

I've modded all the .lua files that I needed to.

And still doesn't work. I can see all the MFCD's, the RWR, Digit Clock, etc. indicators on my second monitor, all of them works fine (I resized and repositioned them to fit for the Helios profile), but the gauges are still stationary.

 

I sent my profile to a friend of mine. He's been using Helios for many months. He tried it on his system but it doesn't work for him.

 

It must be a little problem, and maybe it is Helios's fault.

But at this moment it doesn't work.

 

If anybody has any idea what to check in my Helios profile, or what driver/software I need to check, please share with me. :helpsmilie:

TM Warthog no.00128

Posted

The dcs a10 interface in Helios needs to be the first thing added in the profile. As In Before any gauges are added. Otherwise nothing will work.

Airdog

| Asus ROG Strix Z370-E Mobo | i7 8700K @ 4.7 | 32 GB DDR4@3200mhz | Gigabyte 2080Ti OC 11GB| Samsung M.2 960 Evo 250Gb and 500Gb | Win10 Pro | Hotas Warthog #02743 | Track IR 5 | Toshiba 47" 120hz LED | Acer 23" Touchscreen | HELIOS |Oculus Rift-S|

 

http://www.blackknightssquadron.com/

Posted

Thank you for your answer!

As I can remember it was the first thing that I've done when I made the profile, but I'll try it today.

TM Warthog no.00128

Posted

Once after updating the standalone version of A-10C I had the same problem; gauges didn't work. The cure was that I opened the Helios Profile Editor, added the interface and refreshed the A-10C Setup Install Path. Then I opened my working Helios Profile and saved it with a new name. I activated the new one and everything was OK after that.

 

I hope you'll get your profile working OK as well.

Posted (edited)

Hi there,

 

I've tried all the ways that you've suggested me and it still doesn't work... :cry:

Edited by 59th_Bird

TM Warthog no.00128

Posted

I think we talk about the same thing: my method means that always run that program as admin, but I've tried the way that you've mentioned. No success.

I use Win7 64bit. Everything is updated, including all the drivers.

TM Warthog no.00128

Posted (edited)

Hello,

 

You are very familiar with Helios, sorry I did not notice that earlier in my answer.

 

Can you create a profile from scratch, with only one gauge as a test, do not use Loz's file? This will help rule out if the profile is at fault. It is the only constant I see in all the failures.

Edited by JG14_Smil
Posted (edited)

Thank you for paying attention on me, gents, I'll try to create a gauge for a test.

to agrasyuk: I'm so sorry, my English is so poor. Can you reword me your question please...? :unsure:

Edited by 59th_Bird

TM Warthog no.00128

Posted

I hope that I understood right. :)

When I use the Helios profile editor, DCS never runs. I previously checked the export.lua file and I noticed that the editor can write the file (it can modify the export.lua file).

TM Warthog no.00128

Posted

So, here is the test gauge. It doesn't work.

Perhaps something wrong with my w7 status, maybe one of the background services has stopped (but I don't know which one, because I didn't change anything).

 

The attached file includes my monitorsetup.lua and export.lua files.

birdsetup.rar

TM Warthog no.00128

Posted

yup no bindings with the setup you provided....that would definatley make the gauge not work

Airdog

| Asus ROG Strix Z370-E Mobo | i7 8700K @ 4.7 | 32 GB DDR4@3200mhz | Gigabyte 2080Ti OC 11GB| Samsung M.2 960 Evo 250Gb and 500Gb | Win10 Pro | Hotas Warthog #02743 | Track IR 5 | Toshiba 47" 120hz LED | Acer 23" Touchscreen | HELIOS |Oculus Rift-S|

 

http://www.blackknightssquadron.com/

Posted

Question: did you add the a10 interface to Loz's profile after you had the profile open in the Helios profile editor?

If so and my memory may be failing me but I think there is a bug in Helios that if you add the interface when a profile is loaded in the editor it will erase all the bindings.. Does anyone remember this?

Another question.... In the profile you uploaded here did you copy and paste the adi from another profile or did you start from scratch?

Airdog

| Asus ROG Strix Z370-E Mobo | i7 8700K @ 4.7 | 32 GB DDR4@3200mhz | Gigabyte 2080Ti OC 11GB| Samsung M.2 960 Evo 250Gb and 500Gb | Win10 Pro | Hotas Warthog #02743 | Track IR 5 | Toshiba 47" 120hz LED | Acer 23" Touchscreen | HELIOS |Oculus Rift-S|

 

http://www.blackknightssquadron.com/

Posted (edited)

My method was:

1. open editor

2. save as...

3. add interface

4. open other editor with Loz's profile

5. copypaste

 

But nothing has changed in Helios, the only one has changed is DCS World.

 

Uploaded profile: no, I didn't use any profile, I used a template from the menu on the left: A-10 gauges.

Edited by 59th_Bird

TM Warthog no.00128

Posted

In the test profile you provided you didn't fulfill the test condition. Please bind sone events to that ADI and try to see if it works.

 

I've never used any other than Loz's profile and it worked for 10 months... What are your suggestions....?

I'd try (not sure if you already did):

0. Start Helios profile editor with elevated admin rights (ie the dark screen with UAC confirmation)

1. Take a clean copy of Loz file.

2. Reset monitors as needed.

3. loz file already has a10 interface. Update the path. Click setup.

 

If it doesn't work I'm at loss what to do.

  • Like 1

Anton.

 

My pit build thread .

Simple and cheap UFC project

Posted

And finally it works!!!

Thank you agrasyuk for your help, I'm so happy with my 'cockpit' again!

I really don't know what was the problem, but I'm sure that it was my fault.

Now it doesn't matter - everything works fine as previously.

Thank you! :) :thumbup:

TM Warthog no.00128

  • Recently Browsing   0 members

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