Tanuki44

Fixed mod 'Miniguns' V2.3_1 : a file was missing https://www.digitalcombatsimulator.com/en/files/3321772/ Check your keybind of 'Weapons' category, I used by default the 'G' key for the additionals functions of gunsight. This might conflict with your settings.

Pilot-Copilot and Miniguns (functional) for UH-60L Mod - Version 2.3 - Add a Gunsight - Add 5 new entries of binding for the Gunsight : - GunSight ON/OFF - GunSight Brighten - GunSight Dim - GunSight ON - GunSight OFF The GunSight automatically turns ON when the Master Arm is ON and OFF when OFF Uninstall from previous version https://www.digitalcombatsimulator.com/en/files/3321772/ (modifié)

Pilot-Copilot and Miniguns (functional) for UH-60L Mod - Version 2.2 Fixes the compatibility problem with the Bronco Mod https://www.digitalcombatsimulator.com/en/files/3321772/

Hope a livery artist comes through this forum

For those who want to shoot with the M134 miniguns Video https://www.youtube.com/watch?v=miUdl7YcWJU OvGME File Pilot and Copilot UH-60L Miniguns UH-60L - functional Add 2 entries : \keyboard\default.lua : - M134 Fire - Master Arm ON/OFF \joystick\default.lua : - M134 Fire - Master Arm ON/OFF There is no physical switch in the cockpit, you will need to use the keyboard for 'Master Arm' or bind a Hotas button. https://drive.google.com/file/d/1lyD660l0oURV268Xz2mmAttYyEwotTzF/view?usp=sharing https://www.digitalcombatsimulator.com/en/files/3321772/ Incompatible (without knowing why for the moment) with the Bronco 1.00 mod Be careful, weight has been added to the guns, this changes takeoffs and inertia during flight... TODO : -Gunsight ... if you have any ideas ... -Limit shots according to installed Miniguns if you have any ideas ...

I didn't convert the png's, but I can confirm that the time lag when loading the liveries, but it's not the only one, some mods (aircraft, tech) also have this lag. I don't know if this has any impact once the mission starts

Right, the problem is only with the keyboard, On Discord, they don't even answer, just to see if it's a known problem ...

Tested with only this mod, it's the same problem. I tried it with an axis control, the joysticks work perfectly. I looked at the *.lua file, it refers to the common DCS file "Config/Input/Aircrafts/base_keyboard_binding.lua" ... Other binding works, but not those of the throttle ... Confirmed on my other PC (usually used for DCS)

No

I didn't have time to do much testing, but quickly tested in aligned mode on the runway, same problem as you, the throttles don't move with the keyboard. I'll look more tomorrow ...

French translation of the Manual Traduction française du Manuel https://drive.google.com/file/d/1T4z7xEv54NZv-FCBDaZ6ynoC00lBpnx_/view?usp=sharing

Intéressant... Y aurait il un exemple concret de mise en pratique dans DCS ? Is there an tangible example of use in DCS?

An explanation here, but in French... https://aviation.narkive.fr/54826wYM/comment-et-quand-utiliser-le-bouton-bfo-sur-un-adf

I documented it in the bugs section of TF51 with its fix, last summer...

This is the remark that I had also made. In response, this answer : no comments ...

The deactivation avoids problems with the allocation of these axes when using a new module I had found this video to improve the settings that look quite realistic when the pilot is strapped into his seat.

I saved the profile of the TrackIR column, disabled the ED Tracker column menu and for each aircraft I reload the saved profile.

Do you use EDTracker directly or do you use a software such as opentrack to adjust the curves?

Maybe hack the routine controlling the nav lights and add the formation lights command Not tested but maybe on this principle: .../... for example -- be careful the names of the commands are to be taken from the default.lua file of the folder 'input/keyboard', here the names are for example elseif command == Keys.ExtLightNav then dev:performClickableAction(device_commands.extlight_nav, value, false) -- control for navigation lights --then add the command line for the formation lights dev:performClickableAction(device_commands.formation_light, value, false) -- control for formation lights -- elseif .../... To be adapted and checked if the transmitted values are correct for the 2 commands and to be redone at each ED update... While a third-party script is easier to use and does not change the integrity of the original file.

Maybe by directing the key action to a .lua file that itself performs both actions, but I wouldn't know how to edit it...

Modifiers are great for altering a mapping (e.g. switching from flight mode to combat mode), but the question seemed to be being able to run multiple commands with a single button.

I don't feel any fps problems with key management, on the other hand I had tried to manage an axis and the result had not been good. I have different scripts (helicopter, warbird, jet) depending on the material used and the aircrafts.

You have to use CTLD https://github.com/ciribob/DCS-CTLD

I haven't found how to do it other than using third party software, 'autohotkey' for example

Yes, to our great sadness, this is all behind the SDK.