VVI is running reverse

[eaglewen]

Hi,

I'm running the latest version of DCS and Helios with F-16C-50

I've setup the AOA, the ADI and the VVI on a monitor to use in the the central console.

Everything is working fine except the VVI...this one is running reverse/opposite....meaning that when I'm going up the black part is showing while I'm going down the white part is moving.

My AOA and ADi are running as they supposed to run.

Any idea how this can be solved....should I edit the DCS.F-16C_50.hif.json file for instance? Not sure what the value and mappedvalue does.

Or is there maybe an easier way in Helios?

 

Any help is welcome

 

 

 

{
      "heliosType": "DCS.Common.ScaledNetworkValue",
      "device": "Vertical Velocity Indicator",
      "name": "VVI",
      "description": "TODO: assign units, set calibration points, and write description",
      "exports": [
        {
          "format": "%.4f",
          "id": "16"
        }
      ],
      "valueDescription": "TODO: describe range of output values after calibration",
      "unit": "Numeric",
      "calibration": {
        "points": [
          {
            "value": -1,
            "mappedValue": -1
          },
          {
            "value": 1,
            "mappedValue": 1
          }
        ],
        "precision": 4
      }
    },

Edited December 22, 2022 by eaglewen

[eaglewen]

just found a solution by adding vvi=vvi*-1 to HeliosExport16.lua file

My problem now is that the preflight-check in the control center is complaining that the configuration is not as expected...but it works.

I hope someone has a better solution but for now it works for me

 

function helios_private.processSimulatorData(selfData)
    local altBar = LoGetAltitudeAboveSeaLevel()
    local altRad = LoGetAltitudeAboveGroundLevel()
    local pitch, bank, yaw = LoGetADIPitchBankYaw()
    local vvi = LoGetVerticalVelocity()
    local ias = LoGetIndicatedAirSpeed()
    local aoa = LoGetAngleOfAttack()
    
    local glide = LoGetGlideDeviation()
    local side = LoGetSideDeviation()

    -- send this best effort (NOTE: helios.send will filter nil values)
    if (pitch ~= nil and bank ~= nil and yaw ~= nil) then
        -- these are text keys, which is very slightly slower but avoids collision with modules and drivers
        helios.send("T1", math.floor(0.5 + pitch * 57.3), "%d")
        helios.send("T2", math.floor(0.5 + bank * 57.3), "%d")
        helios.send("T3", math.floor(0.5 + yaw * 57.3), "%d")
        helios.send("T4", altBar, "%.1f")
        helios.send("T5", altRad, "%.1f")
        if math.abs(vvi) < 0.04 then
            -- don't send +/- 0.0 while bouncing on the ground
            vvi = 0.0
        end
        vvi=vvi*-1
        
        helios.send("T13", vvi, "%.1f")
        helios.send("T14", ias, "%.1f")
        helios.send("T16", aoa, "%.2f")
        helios.send("T17", glide, "%.3f")
        helios.send("T18", side, "%.3f")
        helios.send("T19", LoGetMachNumber(), "%.2f")
        local accel = LoGetAccelerationUnits()
        if accel ~= nil then
            helios.send("T20", accel.y or 0.0, "%.1f")
        end
    end
end

[eaglewen]

I think I'm missing something in Helios. I managed to get the VVI working via a kind of hack but now my altimeter is showing me the wrong value...in Helios I got 6100Ft while in DCS it is showing me 8100Ft.

There must be somewhere a file to fix both issues, no?

 

Werner

[BravoSierra]

Open the [your path]\Saved Games\DCS\Scripts\Helios\HelioExport16.lua file and make the following change.

Find the line:

local vvi = LoGetVerticalVelocity()

and change it to:

local vvi = LoGetVerticalVelocity() * -1