Tanuki44

Waiting for the authorization of Nibbylot, for the publication of the submod, there are two grenades or a mortar shells or two lazy smoke bombs Submod Features v1.0 *********** Add HUD with vertical view for dropping with Velocity Vector, Slip Indicator, Ground Speed, IAS, Altitude, Heading, Bank Add Camera View inclinable 0 to -90° Add 'LOW Battery' alert if <= 10%, red flashing Add 3x ammunitions droppable Add SunVisor Add NVG view Improved ground stability The angle mode is selected by default at startup Advice At start, the engines must be started with the lowest power level. Zip archive is OVGME compatible

WIP HUD with imperial or metric units Underlying view for dropping Adding a droppable ammunition (mortar shells)

I added the same ammunition but droppable , I am now working on the inclination of the view (even if the camera is not adjustable and is above ammunition) in order to be able to aim vertically.

In a waypoint action, Whatever the code, it works perfectly in a perform command with a copied and pasted script. But if the same code is in a *.lua file, the perform command with script file doesn't work... Tried with this code example : trigger.action.outText('aircraft has reached WP', 3) Thanks for any help

MH-60R submod v3.8 Release https://discord.com/channels/776815105810759701/1073159705465204797/1233860033461354497

Super merci !!! Un lien pour en profiter ?

J'aurai tellement aimé que ce cône d'hélice soit d'origine dans le modèle 3D, cet ajout est un peu trop gros, mais nécessaire pour couvrir l'original. I would have liked this propeller spinner to be original in the 3D model, this add-on is a little too big, but necessary to cover the original. null

Here the latest version on Discord https://discord.gg/FfEEW2ru while waiting for the soon v3.8

The winch can be used with the MH-60R submod for CSAR missions. https://www.digitalcombatsimulator.com/en/files/3331106/

Superb work I'll see some polar bears on it...

Everything works again for me with this update which allows using TouchPortal 4.1.2 Thanks for the work

Same for me, no problem

for the MH, there is a submod : SeaHawk MH-60R Submod V3.6.2.1 Update with features ASW, ASUW, CSAR https://www.digitalcombatsimulator.com/fr/files/3331106/ To be installed on the excellent UH-60L Mod

FlightPanel should include the MH-60R (UH-60L compatible) mod in the next release of DCS-BIOS. Afterwards, I will make my pages available with the explanation of my workaround for HOT START

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.

It's more of a holding aid than a true autopilot.

An autopilot on BlackHawk ? Where did you see that? Unlook the tail wheel , it would rotate according to the orientation of the BH

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...

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...

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 yet in TouchPortal it shows Current: OFF

Question asked to Warlord

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

An error on my part, the value under DCS is between 0 and 1, but under DCS-BIOS it is converted between 0 and 65535. My event test was therefore bad

Perfect, the line is now accessible. I use this function to read the value of an argument (here 206), however the value does not change and always remains at 0 while the arg goes to 1 That I use a 'Event' or a 'If Statement' Again, have I missed something?

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