-
Posts
575 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Tanuki44
-
Tu confonds la version de l'add-on pilots-miniguns 2.3.1 et la version du mod BlackHawk 1.3.1 Il faut intégrer l'add-on avec OvGME qui remplacera et ajoutera les fichiers nécessaires au mod UH-60L You confuse the version of the addon pilots-miniguns 2.3.1 and the version of the mod BlackHawk 1.3.1 It is necessary to integrate the add-on with OvGME which will replace and add the necessary files to the UH-60L mod
-
fixed Dysfunction of the Wing Flaps Handle of the TF-51D
Tanuki44 replied to Glow's topic in Bugs and Problems
I bet a banana that this will not be corrected -
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é)
-
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 ...
-
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)
-
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 did not use Gumroad, just installed like others plugin in Blender Download the ZIP archive (do not unpack it after downloading) Open Blender and go to: Edit > Preferences > Add-ons > Press "Install..." button Browse to the location of the ZIP and select it, then press "Install Add-on" Enable the addon by pressing the checkbox
-
fixed Dysfunction of the Wing Flaps Handle of the TF-51D
Tanuki44 replied to Glow's topic in Bugs and Problems
I documented it in the bugs section of TF51 with its fix, last summer... -
fixed Dysfunction of the Wing Flaps Handle of the TF-51D
Tanuki44 replied to Glow's topic in Bugs and Problems
This is the remark that I had also made. In response, this answer : no comments ... -
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.