Tanuki44

I put my old modified file. The problem is solved, the definition of the bridge height is not good CV6_Entreprise.lua

Indeed, I just tested, the flyable planes cross the bridge... I'm going to look for what I had done ....

Do you have the *.miz file?

I don't have a Virpil, but they are similar (seems to be the commercial version of MMJOY for DIY), Have you tried another axis to compare yet? In the positive case, keep the values and modify those of the RZ. I see that RZ has an offset, is it voluntary?

You can add this section: -- FLARE DISPENSER {down = device_commands.Button_2, cockpit_device_id = devices.FD, value_down = 1, name = _('Flare Dispenser SEQ'), category = _('Flare Dispenser')}, {down = device_commands.Button_2, cockpit_device_id = devices.FD, value_down = 0, name = _('Flare Dispenser C/C'), category = _('Flare Dispenser')}, {down = device_commands.Button_1, cockpit_device_id = devices.FD, value_down = -1, name = _('Flare Dispenser D'), category = _('Flare Dispenser')}, {down = device_commands.Button_1, cockpit_device_id = devices.FD, value_down = 0, name = _('Flare Dispenser G+D'), category = _('Flare Dispenser')}, {down = device_commands.Button_1, cockpit_device_id = devices.FD, value_down = 1, name = _('Flare Dispenser G'), category = _('Flare Dispenser')}, {down = device_commands.Button_3, cockpit_device_id = devices.FD, value_down = -1, name = _('Flare Dispenser AR'), category = _('Flare Dispenser')}, {down = device_commands.Button_3, cockpit_device_id = devices.FD, value_down = 1, name = _('Flare Dispenser LE'), category = _('Flare Dispenser')}, {down = device_commands.Button_3, cockpit_device_id = devices.FD, value_down = 0, name = _('Flare Dispenser VE'), category = _('Flare Dispenser')}, in - the .lua file used in the folder ..\Eagle Dynamics\DCS World\Mods\aircraft\SA342\Input\joystick for adding button shortcuts. - the .lua file used in the folder ..\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\SA342\Input\keyboard for adding keyboard shortcuts. The FLARE DISPENSER section will be added to the configurable list. Enjoy or use the JsGME / OvGME if you use the default.lua files SA342 Flare Dispenser.zip

Retested on my dedicated DCS PC, the axis works normally without any clicking sound. What are your audio settings for comparison?

I have isolated the problem a little more, some static objects (civilian ?) like a comm antenna, the WC prevent from engaging the enemy if it's too close. other static objects such as a guard tower, water tower is not a problem. You were unlucky enough to pick up an object that causes a problem

For these tests, I started from your mission, I just created a new mission and the problem disappeared .... so the bug is elsewhere To be continued

Good question!!! the original mission is with a static object, so I redid the test with a 'tv antenna' object of the “ground units” category. It works properly, the gunners engage well the fire on the insurgents near the object. To be checked with other objects but the problem would be with the static objects...

No sound, neither open nor closed, nor during. I will try again tomorrow on my other PC

Just tested, without any mod, flaps assigned to an axis, it works normally, the steps do not exist anymore, the flaps follow the position of the axis.

After various tests, I found that the gunners did not fire if the insurgents were near structures. Move the antenna to 1500 feet from the insurgents, the gunners will start firing again...

+1 Settings to 30-60-90-120 Diamonds rotate with adjustment just like a diaphragm of a camera It does not matter, the only important thing is the ring inscribed in the diamonds, regardless of the position of the head, the plane, the target.

@Hawkeye60 Your screenshots show the F4U and the P-51D ? Can you try with one of the 3 mods of the pack "ai-1940-battle-of-britain-with-3-flyable-planes" ?

Yet the structure of the folders of the mod F4U (use folders of the TF51 and P-51D) and the mod folder HURRICANE, DEWOITINE et STUKA is different. and with one of the three mods the P51-D in yellow (flyable) does not appear... It is possible to make them appear at the same time, one as static, one flyable, but can not activate them as a client.

Not at home, as stated in the first post, <<In addition to the AI Pack, you will find 3 FLYABLES PLANES with the cockpit and the avionics of the P-51 these are to be installed with the JSGME and to be used only individually, in summary you should only use them one by one in the JSGME , Its very important !!!! As it replaces the P-51D you could not pilot this one (as long as the mod is activated in the JSGME), but you will find it in the AI Pack.>> only their mod F4U can be used at the same time as the P-51D The three mods HURRICANE, DEWOITINE and STUKA deactivate the P-51D ...

OVGME is a Windows program, it settles like any soft https://github.com/Have-Purple/ovgme It does not matter if your path is different, point right on yours.

I do not use JSGME but OVGME I put the three folders separately with my other mods in a folder called 'Archives' in \Saved Games\ Here is my config The three mods appear in the main window, here I activated the 'Hurricane' : It works perfectly so

Ahh probably was it at the same time as I asked for repairs

@cfrag Could you confirm if it's the wind that is the real cause?

Refueling can only be with engine turned off, rotor stopped. What seems logical side security.

Is it a drift during navigation (wind?) and/or canoe ... or an approximation of bearing received I made myself the same remark, but by repeating the mission several times, it is wise to make a very regular point to reorient. But it's a little object on the ocean with a lot of swell and spot the illuminating rocket when you are close enough.

I admit that my English is not good

Ci-joint un fichier *.trk montrant le fonctionnement du bouton. Test fait seulement avec des touches sans aucun axe Les gaz sont au max, je réduis avec la touche PageDown jusqu'à la butée Idle Ground Je coupe l'alarme J'appuie sur le bouton (ici avec la souris, mais c'est identique avec les touches RWIN+T), le bouton sur le collectif reste enfoncé ce qui déverrouille la butée et permet avec la touche PageDown de réduire les gaz à zéro. Attached is a *.trk file showing how the button works. Test made only with keys without any axis Throttle is at max, I reduce with the PageDown button until the Idle Ground I turn off the alarm I press the collective button (here with the mouse, but it's the same with the RWIN+T keys), the button on the collective remains pressed which unlocks the stop and allows with the PageDown button to reduce the throttle to zero. throttle.trk

Flappie's request for the button is for safety so that he doesn't cut the engine by reducing the throttle, it doesn't intervene in the throttle rise. We agree that the management of the throttle axis is not in accordance with RL, but the management only with the keys seems correct.