Tanuki44

Using AutoHotKey I managed to unlock the axis at the push of a button, the script checks that the throttle is at the minimum to trigger a series of key presses 'PageUp'. I even added a few options at boot time. Joy5:: ; Unlock Throttle axis with the button n°5 of joystick - xJoyb : x is the joystick number (nothing if only one) ; b is the number of button if (GetKeyState("JoyR") > 97) ; 'JoyR' is the 4th axis of the joystick ; 'JoyU' and 'JoyV': The 5th and 6th axes of the joystick. ; 97% or 3% along the throttle axis curve { Loop 12 ; counter for maintaining the pressure 'PageUp' { SendEvent {PgUp Down} Sleep 20 SendEvent {PgUp Up} } Sleep 20 Send #h ; (optional) disable 'Crew Panel' at start (LWin + H) Sleep 20 Send <+{F10} ; (optional) disable 'Labels' at start (LShift + F10) } return Enjoy :pilotfly: Idle Unlock.zip

This TARGET script, do you have it?

By assigning a collective button to the 'PageUp' key, as soon as the cursor has passed the 'idle ground', the accelerator becomes functional. It's not perfect, but better than nothing.

Same thing, I ended up removing the connector and soldering the 4 wires directly on the pro micro and glue the cable, but it's very thin (it's better to do this before the tracks are ripped) :blink:

I corrected the link and the screenshot was missing ... :thumbup:

I'm not sure of the scale Unzip and put the file 'sight_XM60.tga' => \Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Uh-1H\Cockpit\IndicationTextures I have taken the original circle sight_XM60.zip

See Post https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-uh-1h-huey/7139897-reticle-pattern-m60

:thumbup: It works perfectly :thumbup: until now, I calibrated in the joystick manager of Windows...but MMjoy is more powerful. Thanks

Thanks for your answer All my axis are 'nothing' ... I'll test your solution and get back Is it necessary to do this for all other axis ?

I defined 4 virtual buttons at the ends of a mini joystick. ​ When MMJOY2[v20160818upd1] starting, the state of these buttons is not initialized correctly or unstable. After moving the mini joytsick to the 4 ends, everything becomes ok. Would there be a solution so that the initialization is done automatically? We read on the web that the latest version [v20161101] is buggy ... Do we know the problem, is it a particular function?

Door Gunners and the CoPilot do not have the ability to fire rockets ... why could AI ? and the M60 and M134 do not fire on armored vehicles (ineffective) I thought that only the pilot could fire the rockets or am I wrong?

My experience is only from SP. For I won't stand up for ED on the Huey's broken things :smilewink: The problem is not that it happens, but the delay in getting it fixed.... The function is not really removed, replaced by default by a positioning indicator ... know if it's better, it's everyone's taste but leave the keyboard / button shortcut did not bother. Other keyboard or button shortcuts are missing, but luckily the code is accessible, customizable and the community is here to help.

It is good to know how to edit the 'default.lua' files of the Input folder in order to be able to customize at will (example keys F1-F12 in the 'Radio Communications' menu ). :smilewink:

- with an helicopter with no minigun and 'external carry points' in 'Mission Editor => Payload mode' is checked => the flexible sight descends automatically. Two solutions, install miniguns or edit the mission and uncheck the case 'external carry points' But if an armament is loading on the slots (door gunner or pod) the case is automatically checked and the bug is there again :(

See post : https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-uh-1h-huey/221084-mod-uh-1h-enabled-keys-and-buttons#post3622861 You just need to add the keyboard and joystick shortcuts LCTRL + LSHIFT + C Tested and still functional

Some things are broken (altimeter, texture, sight of the co-pilot descending alone) but are also repaired (texture), but alas, the UH-1H does not seem to be the priority over planes ... (altimeter is broken since August ... and however since a release is out DCS 2.5.6.55960 - 09.10.2020...) But with the latest Open Beta 2.5.6.57264, jumping into the co-pilot's seat, using the flexible and firing with or without the autopilot works perfectly for me ... The LALT + LSHIFT + Q cargo camera or the RCTRL + RSHIT + P cargo view also works.

Very good initiative, :thumbup: The realization of commands increases the pleasure and immersion of piloting. ​ Nothing is the same after ​:pilotfly:

This seems fixed in yesterday's OpenBeta update, but still no fix for the altimeter setting ...

Is there a similar solution for the Gazelle SA342 in MiniGun mode, I am using 'opentrack' for my EDTracker and it's impossible to use the mouse for aiming movements, the only solution would be not to connect the EDTracker when starting DCS ... :cry:

Answer here => https://forums.eagle.ru/forum/english/digital-combat-simulator/dcs-uh-1h-huey/bugs-and-problems-ah/art-issues-3d-textures-animations-aa/289383-m261-texture-issue?t=286755

Hello, I need some help ;)​ I created a modifier called 'Combat' in switch mode for my joystick mapping in 'modifiers.lua' file local modifiers = { ["Combat"] = { ["device"] = "Joystick", ["key"] = "JOY_BTN5", ["switch"] = true, }, .../... How to test the 'state changing' only (without any another key or button) of this modifier (false or true) to display or not a panel on the screen ('Crew Panel' in the UH-1)? Even having some knowledge in lua, I don't know how to start... :cry: Thanks in advance

I reduced the size of the panel, changed the position, the transparency and the color. Just change this file .. \Eagle Dynamics\DCS World\Mods\aircraft\Uh-1H\Cockpit\Scripts\ControlsIndicator\ControlsIndicator_page.lua ... (for those who still fly with :smilewink:) I commented on the changes. ControlsIndicator_page.lua

To position the panel at the bottom left corner, you can change this line: base.init_pos = {aspect + shift_X, firstLineY + shift_Y} by this : base.init_pos = {-aspect - border_s, firstLineY + shift_Y} :smilewink:

+1 many hours of practice, time to spend to refine the settings, reading some litterature of the flight model etc ... and fun replaces frustration :pilotfly: