Jump to content

Denver29

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by Denver29

  1. Thanks for pointing that out, I also have this at a higher setting, and without it the flickering is much more noticeable.

     

     

     

     

    I would look at the examples in the A-10C.lua file, it combines pressure values into a new value how you would like to:

     

        [59] = "%.4f",        -- pressure_setting_0
       [58] = "%.4f",        -- pressure_setting_1
       [57] = "%.4f",        -- pressure_setting_2
       [56] = "%.4f",        -- pressure_setting_3
       [61] = "%.1f",        -- AAU34_PNEU_flag
    
       --  Pressure setting 
       --------------------------------------------------------
       local pressure_setting_3 = mainPanelDevice:get_argument_value(56) * 10000             -- {0.0, 10.0} {0.0, 1.0}
       local pressure_setting_2 = mainPanelDevice:get_argument_value(57) * 1000             -- {0.0, 10.0} {0.0, 1.0}
       local pressure_setting_1 = mainPanelDevice:get_argument_value(58) * 100                -- {0.0, 10.0} {0.0, 1.0}
       local pressure_setting_0 = mainPanelDevice:get_argument_value(59) * 10                 -- {0.0, 10.0} {0.0, 1.0}
       local pressure_setting = ((pressure_setting_3 + pressure_setting_2 + pressure_setting_1 + pressure_setting_0) / 100)         
       ExportScript.Tools.SendDataDAC("2006", string.format("%5.2f", pressure_setting))

    For the landing gear light, finding this value may be a bit more involved, instructions for how DCS ExportScript gets their IDs are found here: https://github.com/s-d-a/DCS-ExportScripts/wiki/Documentation-in-English#Create

     

    The DCS Bios folks deal with a lot of this stuff as well, and there may be some threads that have knowledge of that export value or how to find it. I haven't explored too much in extracting lamp export IDs from modules other than what has already been done by ExportScript/Helios/DCS-Bios people.

     

     

    Well i found the value for landing handle light that is [227]

     

    But for the pressure no way to have it works. I try in the A10 and the value 2006 of the bas export script do not work

  2. I fix the problem of flickering switch by changing "ExportLowTickInterval" from 0.5s to 0.1 and "ExportInterval" from 0.05s to 0.1 in the config.lua of DCS-ExportScript folder.

     

    An other Question, in the script some data are ti be export separetly like for example pressure setting of the altimeter:

    -- Standby Pressure Altimeter AAU-52/A

    [218] = "%.4f", -- Altimeter_100_footPtr {0.0, 1000.0} {0.0, 1.0}

    [220] = "%.4f", -- Altimeter_10000_footCount {0.0, 9.0} {0.0, 1.0}

    [219] = "%.4f", -- Altimeter_1000_footCount {0.0, 9.0} {0.0, 1.0}

    [221] = "%.4f", -- pressure_setting_0 {0.0, 10.0} {0.0, 1.0}

    [222] = "%.4f", -- pressure_setting_1 {0.0, 10.0} {0.0, 1.0}

    [223] = "%.4f", -- pressure_setting_2 {0.0, 10.0} {0.0, 1.0}

    but if i want to have the full pressure setting on only 1 buton how can I?

     

     

    I also wanted to have a button working as a lamp for the red gear lever light but found in the export that it has no number:

    -- Landing Gear

    --[] = "%1d", -- CPT_LTS_LDG_GEAR_HANDLE

  3. Hi

     

    First thanks a lot for this great plug-in. I realy enhanced streamdeck experience with DCS.

     

    I'm at work for a F/A-18C hornet profile but encounter some trouble with toogle switch. I'm not sure the rigt way to explain that but when i press a buton on stream deck, the fonction change in DCS (no problem for that), but on stream deck the image first change to new state then go back to the previous state an update again to the new state, all that in a seconde. It's like there is two image update command in conflict ...

  4. my DCS export script looks that:

     

     

     

     

    userprofile = os.getenv ("userprofile"):gsub("\","/")

    -- dofile(userprofile .. "/Saved Games/DCS.openbeta/Scripts/DCS_NMEA.lua")

     

    -- load the DCS ExportScript for DAC and Ikarus

    dofile(lfs.writedir()..[[scripts\DCS-ExportScript\ExportScript.lua]])

     

    pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

     

     

    dofile(lfs.writedir()..[[scripts\Helios\HeliosExport16.lua]])

  5. Hi everybody

     

    I desesperatly can not make this work on my ipad with foreflight

     

    I copy the script as you said, i open the UDP port 49002 and 4353.

     

    I go to my forflight "device" option and nothing!! It's empty !!!

     

    What am I mistaking??

  6. Hi I encounter some troubles with helios UFC and UEFI for the hornet.

     

    The UEFI nozzle indicator needle don't move and is stuck to 0

    The UFC ":" selected option indicatore is replace by a "1" when selected and "0" when unselected ...

  7. Hi everybody

     

     

    I'm using the wonderfull Capt Zeen F/A-18C Helios profile on a 24" touch screen and a 27" as main cockpit view. Helios works great but i'm in trouble with my DDI and AMPCD export. I can't deal the strokes definition between the DDI and AMPCD on the 24" with HELIOS and the HUD on the 27" main screen.

    With the DrawLineAsWire option to true the export are unreadable because too thin, if false there are too big. If i adjust the stroke def in the common multipurpose display script from 0.8/0.5 to 0.4/0.2, DDI and AMPCD in HELIOS are quite acceptable but the HUD in virtual cockpit is too thin!!!

     

    Is there a way to tune the stroke def of DDI/AMPCD independently from th HUD!!

     

     

    Sorry for my poor english writing

     

     

    Denver

  8. I can't go threw mission 6 ... after taxiing behing the leader the runway access is blocked by a vehicule and my leader wait for him to move ... indefenently!!! :cry:

     

    Does anybody encounter this problem? And how to fix it?

×
×
  • Create New...