Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Tanuki44

  1. I documented it in the bugs section of TF51 with its fix, last summer...
  2. This is the remark that I had also made. In response, this answer : no comments ...
  3. 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.
  4. I saved the profile of the TrackIR column, disabled the ED Tracker column menu and for each aircraft I reload the saved profile.
  5. Do you use EDTracker directly or do you use a software such as opentrack to adjust the curves?
  6. 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.
  7. Maybe by directing the key action to a .lua file that itself performs both actions, but I wouldn't know how to edit it...
  8. 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.
  9. 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.
  10. You have to use CTLD https://github.com/ciribob/DCS-CTLD
  11. I haven't found how to do it other than using third party software, 'autohotkey' for example
  12. Yes, to our great sadness, this is all behind the SDK.
  13. For those who don't follow discord: Version 1.0 of M134 miniguns integreted in mod of pilots https://www.digitalcombatsimulator.com/en/files/3321772/ Currently it is a mod that adds to the main mod of the UH60L, it is the 1st phase which is static, the files will be sent to =X51= Kïnkküjüstövöïlëïpä which is the only one to have the capacity to make them functional.
  14. French Version of Rudel_chw on Normal Procedures. UH-60L_-_Normal_Procedures_by_Rudel_chw_FR.pdf
  15. French version of the manual 1.3 https://drive.google.com/file/d/1ejhpIVF0BVwkNKAOfbx5o5K0mtk_oRc0/view?usp=sharing
  16. WWII planes must be balanced, the Spitfire is equipped with 2 axes of Trim, the P51D in 3 axes. It is more pleasant to do it via axes than by impulses on buttons. Apart from DIY equipment, I do not know of 'standard' (commercial) equipment have as many axis.
  17. UPDATE VERSION *** Pilot and Copilot UH-60L *** Version 5.2 (Correction of a bug preventing the adjustment of the quantity of fuel during a refuel) https://www.digitalcombatsimulator.com/upload/iblock/e42/56g7dv0p2dkqf2nwdeychzx30zj0rmkq/UH-60L-1.3_Pilot_v5.2.zip
  18. OK, everything has become normal again after having repaired.
  19. Strange, it just corresponds to the update, it does with all my more or less strongly modules ... If I have time I will try to downgrader to be sure. Thanks for the feedback
  20. Since the last OB update, the aircrafts seem to be behind a thick fog that makes them all white. Previously, they were already overexposed but now ...
  21. To lock it, the brake axis must be at least 70% (on my equipment) when you pull the lever. @DmitriKozlowsky your post has disappeared ...
  22. For the 'Formation Lights' the decrement function does not work with keys or joystick buttons The bug is line 362 in the file ...\Saved Games\DCS.openbeta\Mods\aircraft\UH-60L\Cockpit\Scripts\Systems\lighting.lua The correction is: elseif command == Keys.formationLightsDec and formationBrightness > 0 then lighting.lua
  23. If I understand correctly, you want to bind a potentiometer to these buttons, But these do not seem to be managed as axes but simply by key pulses. I am not sure that management functions and axes exist. Personally, I managed this via rotary pulse buttons. For info, Windows can manage 8 axes per controller, X, Y, Z, RX, RY, RZ, Dial, Slider
  24. Often it is because the line was not created in the default.lua file which is in the folder : ...\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\xxxx\Input\joystick\ You are looking for what line?
  • Create New...