Jump to content

Tanuki44

Members
  • Posts

    574
  • Joined

  • Last visited

Posts posted by Tanuki44

  1. For my mod MH-60R
    There are currently 6 pages: NAV, RADAR, ASN1-28B, ENGINE, ASW, CSAR
    Some elements communicate bidirectionally, others via keybinds.
    Everything seems OK in COLD START, there is still the problem in HOT START, a workaround is in place but still needs fine-tuning.

    Thanks again for your help and your work on the plugin that made this adaptation possible.

    Touch_Portal.png?ex=653157fd&is=651ee2fd

  2. here is the line, but I don't think that's the problem, the battery switch is just an example (also found on the Huey page)
     
    BATT_SW|batt_sw|Battery Switch, OFF/ON|4|0|OffOn|OFF

    but I will test to understand the difference, this concerns all of cocpkit's elements (inter, light, value of arguments).

    Everything works normally from COLD START, with all the tests that I have done, I am convinced that in HOT START mode,

    there is no event at the start of the mission, the elements are not initialized or maybe I missed something in the cockpit concept?

    To be continued... 😉

     

  3. On 9/22/2023 at 5:10 AM, xoomigo said:

    In your case, just use the text editor to remove the 2 hash characters in the line concerned.

    LIGHTING_SWITCHES|lighting_switches|Lighting_Switches|0|0|=int(65535)|0

    Then, add the same line to the file CustomACParam.dat. This will ensure that the next time you run the PP extractor script, it will not add the hash characters for the line concerned. You will need to do the same for all new record lines with the data type concerned.

    I tested this
    LGHT_SW|lght_sw|Lighting_Switches|0|0|#=int(65535)#|0
    modified 
    LGHT_SW|lght_sw|Lighting_Switches|0|0|=int(65535)|0

    I added this edited line in the CustomACParams.dat file

    but when I execute the extractor script, the line is not taken into account 

    after the script .\dbParamExtractor.ps1 MH-60R
    in MH-60R.tt
    the line is 
    Lights|analog_gauge|LGHT_SW|Lighting_Switches|0|0|65535|integer

    after the script .\ppGenerator.ps1 MH-60R
    in MH-60R.pp
    the line is always
    LGHT_SW|lght_sw|Lighting_Switches|0|0|#=int(65535)#|0

    I tested with the option --verbose
    98 LGHT_SW : Not customized

    I tried to read the script but I'm not comfortable with this language...

  4. Quote

    Bios shows the actual stateof the pit. It does not matter in wich state it is, since bios reads the switch position in the cockpit.

    Using ctrldef we can see that the values are correct during a Hot Start.

    For example, in Hot Start, the Battery switch is positioned on ON


    on1.png

     

    yet in TouchPortal it shows Current: OFF

    on.png

  5. I come back to my question about starting a mission in Hot Start,
    I tried different things, but I can't figure out how to synchronize the objects.
    Some events seem not to happen which is not the case with a Cold Start.
    Is there a way to make a button that would run a series of tests to resync the elements of that series which could be triggered by the event 'Aircraft connection is ON'
    Thanks

  6. I defined in the lua of my mod in DCS-BIOS :

    local defineFloat = BIOS.util.defineFloat
    defineFloat("LIGHTING_SWITCHES", 206, {0, 1}, "LIGHTS", "Lighting_Switches")


    that I find in the .json

                       "LIGHTS": {
                                     "LIGHTING_SWITCHES": {
                                                                  "category": "LIGHTS",
                                                              "control_type": "analog_gauge",
                                                               "description": "Lighting_Switches",
                                                                "identifier": "LIGHTING_SWITCHES",
                                                                    "inputs": [  ],
                                                                   "outputs": [ {
                                                                                      "address": 25088,
                                                                                  "description": "gauge position",
                                                                                         "mask": 65535,
                                                                                    "max_value": 65535,
                                                                                     "shift_by": 0,
                                                                                       "suffix": "",
                                                                                         "type": "integer"
                                                                              } ]
                                                          }
                                 },


    and in  .pp

    LIGHTING_SWITCHES|lighting_switches|Lighting_Switches|0|0|#=int(65535)#|0

    Everything seems OK, but impossible to find it in TouchPortal to test its value,
    What am I doing wrong or forgetting?
    Thanks for help

     

  7. No problem to help according to my knowledge (I am new to the DCS-BIOS, DCS-COINS and TouchPortal environment)
    Since I need to create the DCS-BIOS file for my *.lua mod, my main difficulty at the moment is choosing
    the right type of switch or button for the commands to make sure I can use it in TouchPortal.
    I also need to understand how to synchronize the lights, buttons during a hot start

  8. Hi,
    To add a functional winch, you must be able to modify the 3D files and add the necessary args and commands and gameplay
    This was only possible for me because I had permissionfrom the UH-60L mod author (@Kinkkujuustovoileipa) and  files to make a submod of the MH-60R.

  9. I got help from WarLord from DCS FlightPanels.


    This made it possible to find the problem in the lua file, currently DCS-BIOS seems (I have to complete the file) to be functional in bidirectional mode.

    It will be necessary to regenerate the *.pp file, for the moment I will modify the current test file manually

    • Like 1
×
×
  • Create New...