Jump to content

Recommended Posts

Posted

Hi

I’m using Helios to show instruments that are not viewports. Eg aoa, vvi, backup adi, back-up airspeed and backup altitude. After seeing things up in Helios and running dcs, I can see the viewports, but not the simulated gauges. First question: do the simulated indicators set up in Helios actually respond to dcs outputs?
Second question: why are the simulated gauges not showing up on my displays? The displays are working.

Posted (edited)

You need to use a Capt Zen profile and reduce what is in it to leave what you want - if you search my posts you will see one on making Helios profile files work

Cheers

Les

Edited by lesthegrngo
Posted

Like Les writes. You need to use a Helios profile with the instruments added, download or make your own. Helios in itself does not export the view ports, but I guess you know that. Ikarus is another alternative, while it seems not to be in development anymore.

Sent from my SM-A536B using Tapatalk

Posted

Actual, my profile is based on the Capt Zeen f-16 profile. However, I found out that I was trying to run the wrong profile in the control Center. 

i managed to get things working. 
note I’m struggling with performance of the gauges. 
1) the Mach meter is inaccurate above 1.0 (it might be below that, I didn’t measure accurately), but when I fly m1.2 the Helios gauge indicates 1.0.

2) the altimeter stutters. The stuttering seems to reduce at a certain pitch angle. In the video I posted here (

) you see it’s around +20 degrees of pitch that the stuttering stops. 
I have another video that shows the stuttering stops at about 12 degrees pitch. The difference between the videos is a pitch ladder image calibration in Helios, as the pitch ladder was not aligned with the in game gauge. 
 

regarding point 2: vsync in DCS is enabled, and I manually set max frame rates to 60 in the graphics lua, in line with my monitor refresh rate. 

  • Like 1
  • 3 weeks later...
  • 1 month later...
Posted

Curious why the current F-16 Interface doesn't seem to work with gauges on a new profile build? Is the only way to get gauges to work on separate screens by taking Zeen's current F-16 profile and hacking it up?

GIGABYTE X870E AORUS Elite WIFI7, Thermaltake 1200w PS \AMD Ryzen 7 9800X3D - Corsair iCue Titan Liquid CPU cooler \ 64GB G.Skill Z5 DDR5 \ SBlasterX G6 \ 4TB NvMe M.2 Boot Drive \ Zotac GeForce RTX 4090 Trinity 24GB - Nvidia 576.52 drivers \ 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz Gsync \ Win11 Pro Ver. 24H2 - Build 26100.3915 \ TIR 5 \ Warthog HOTAS  with VirPil stick base \ MFG V3 Pedals \ TM MFDs  on 2 8" Lilliputs \ Simgears ICP \ Varjo XR-3 VR

  • Recently Browsing   0 members

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