Tanuki44

No problem for me, I just now tested with the QuickStart Target Practice (with no mod)

This is my curve for 35° of travel and I use sensors HALL for better precision and stability. I reproduced this, but on the 35°, I never use the maximum.

On my PC, the key 'menu' between the key 'ALT GR' and 'RCTRL' is recognized by DCS as 'RWIN'

I am delighted My last creation :

In a cyclic-collective configuration, usage of mouse (and for a right-hander) is not very easy and requires an available area. My idea was to make a 'tactile' mouse with buttons suitable for dashboard instruments. (Initially for the Huey, but also usable in other modules). A pad (recovered on an old PC) for the cursor. In center, a rotary encoder to replace the mouse wheel with a function 'pressed' for a fast mode. On left, a rotary encoder for left and right button of the mouse and 'pressed' for the middle button (which I use to freeze 'momentarily' the trackIR). At right, a momentary switch (on)off(on) for up and down position that also corresponds to the left and right buttons of the mouse. All driven by a Pro-Micro Arduino in 'mouse' mode. This makes it possible to get closer to the natural movements of the (left) hand for dashboard buttons and to be able to keep the right hand on the cyclic. I am still trying to improve the management of the wheel, simultaneous use of Interrupts and PS2 communication of the Touchpad hang the Pro-Micro Arduino. For the moment, without solution, I do not use the interrupts, it already works well. If a specialist in the coding of the Arduino has an idea ...

Great solution for this management with the mouse Thanks for this info

Indeed, mouse wheel is really slow, while waiting for better you can edit the file \\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Uh-1H\Input\UH-1H\keyboard\default.lua and add two lines : {combos = {{key = 'W', reformers = {'LAlt'}}},pressed = device_commands.Button_7,cockpit_device_id = devices.ADF_ARN_83, value_pressed = -2.0,name = _('ADF Frequency Decrease Fast'), category = _("ADF Set Control panel")}, {combos = {{key = 'X', reformers = {'LAlt'}}},pressed = device_commands.Button_7,cockpit_device_id = devices.ADF_ARN_83, value_pressed = 2.0, name = _('ADF Frequency Increase Fast'), category = _("ADF Set Control panel")}, You can also assign two buttons...

Copy !! This is a new approach of mission, find the best tactic

Thank you for your mission I just find it lacking guidelines, in RL, is it the pilot to decide what to do? The choices are theoretically ordered by the QG to organize the CAS, As a pilot I have trouble having a vision of the real need to succeed the mission. But the action is nice, I will do and redo the mission to try not to fail Keep going

After research, I found the place where the problem is : In Mods\aircraft\Uh-1H\Cockpit\Textures\UH-1H-CPT-TEXTURES.zip, there are two files : uh1_dev_2.dds uh1_pribors_c.dds where the colors are not same, an excerpt from the images : Current colors do not match the original, (compared to the doc)

Very nice pictures The strangest thing is that the last 'stable' version is at the same level as the OB, why this difference? ... And it doesn't appear to be in the Huey mod folder ... maybe a layer ... If a graphic designer from DCS could give us the info

59 views and not a single confirmation or infirmation

I already had this, in the flight controls, wouldn't there be an axis of two different devices for the same command? EDtracker with opentrack... I disabled EDTracker since it is managed by opentrack

Ahhh, it is therefore linked to Hotas itself, pity ... It is therefore preferable to map the toggles on push buttons as initially planned. If it's possible...

I reproduced on my config, for 'toggle' buttons, the problem is not in the file default.lua, you must declare the two positions of the inter, did you do it ? For me, the button 15 is the high position, the 16 the low position. This should work fine with all 'toggle' buttons.

I may not have understood correctly, You just want to reverse the top and bottom for the Auto-Slaved Toggle?

Have you tried with this : {down = device_commands.Button_12, cockpit_device_id = devices.AUTOPILOT, value_down = 1, name = _('SA342 Auto-Slaved Toggle'), category = _('SA342 Pilot Stick')},

That was the purpose of my post The soft under Windows is just for settings.

Whether you flash your arduino code or the MMJOY code, it's the same... Your 'DoorGunner' will be recognized directly as a joystick in Windows / DCS. Not more 3rd party apps.

This is the filter integrated into the MMJOY firmware, adjustable for each axis up to 15 levels. I don't have more info on how it works, undoubtedly a smoothing of the peak on an average of values... He does the job well better than I can program him.

Despite the last update of the stable version, this difference persists. Is it only on my installation ?

Apply a filter ? Personal, I replaced all the potentiometers by HALL sensors and with a x2 or x4 filter (with MMJOY) it is very stable.

Wait ... this is the lot of helicopter pilots

I just tested missions 2 and 3 of the WORLD APART Spring 2025 campaign which are not modified, but here is the log of autoupdate_log.txt 0 file download, change and nothing to install... Isn't there a problem with the update which was already retired yesterday and then reuploaded this morning ?

Sorry, I hadn't seen RazorbackNL's request, now the handle of the cyclic is interchangeable, I am finishing the handle of the Gazelle. I also changed the settings, no curve, just saturation adjustment for the sensitivity following the advice of FragBum.