Tanuki44

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.

If you press PageDown, the throttle goes down to 'Idle Ground' and stops. Press RWin + T once, the button will sink and you can press PageDown again to lower the throttle to 0 to turn off the engine completely. Like the IRL procedure... but only with key press not axis Checked just now with the latest OB

I have just tested a mission with a cold start and the training mission, the 'Home' button works without problem But the training mission sometimes reacts strangely to key. Check if you are forgetting something in the start-up procedure, especially throttle at Ground Idle.

"Haters gonna hate" Don't pay attention to it and enjoy creating your missions, at least you have that ability

Indeed, the key/button bindings have been fixed. Shouldn't the phenomenon be the same for the Spitfire? I don't know about the others warbird, I don't have the modules. Thanks for these precisions. N.B. I confirm that the TF-51D is not corrected, neither for the canopy nor the flap lever.

I just noticed that the canopy can only be opened at a reduced flight speed, in the manual it is not indicated that one can open it in flight... So that's where ours keys or buttons problems come from. This canopy lock does not exist on the Spitfire. Does anyone have any info on this?

Indeed, some lines (in english) are as you describe.

Would it be related to the translation? and I have no mod, same for the P-51D I will install an English version to compare ...

Absolutely not, the display of 'Actions' (in French) is normal

You can try this...

The speed of the V1 in the mod is 238 mph If we miss the interception, the spitfire can catch up but only slowly. The P-51D and Mosquito seems to be faster for hunting with this mod.

From Wikipedia https://en.wikipedia.org/wiki/V-1_flying_bomb

Not having the Persian Gulf map, I can't see your tracks. But the problem of the slippery Huey has already been mentioned

The mission 1 starts right from Tarawa à 11 knts with wind, cold start is not a problem.

I believe that in the mod, the speed of the V1 has been decreased to allow the Spitfire to compensate for this problem...

Test of the 1.0.4-FR : Without being able to explain, I lost the first crate just before I drop it down (no message after a approach correction announcement)... I'll do it again to be sure Otherwise everything went well, the 3 crates were dropped and the mission ended without a bug. I even got a medal

Is there any way to create a mission in SP with the same conditions (weather ship...) to reproduce the problem?

There are the commands in the joystick/default.lua {pressed = device_commands.Button_4, cockpit_device_id = devices.CPT_MECH, value_pressed = -1.0, name = _('Canopy Closing'), category = _('Systems')}, {pressed = device_commands.Button_4, cockpit_device_id = devices.CPT_MECH, value_pressed = 1.0, name = _('Canopy Opening'), category = _('Systems')}, {down = device_commands.Button_5, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Canopy Emergency Release'), category = _('Systems')}, but a bug has been reported, the lines should be : {pressed = device_commands.Button_2, cockpit_device_id = devices.CPT_MECH, value_pressed = -1.0, name = _('Canopy Closing'), category = _('Systems')}, {pressed = device_commands.Button_2, cockpit_device_id = devices.CPT_MECH, value_pressed = 1.0, name = _('Canopy Opening'), category = _('Systems')}, {down = device_commands.Button_5, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Canopy Emergency Release'), category = _('Systems')},

Indeed, you should not miss the interception and I seem to remember that you can't tip the V1 from the wingtip, it blows him up and the plane too. (unless the mod could be adapted)... But it's a very well made mod

I only use ProMicro and MMJoy2, never had a problem either

In VR ? Do you have a track to try to replicate?

Also, the message indicates 3 crates to be unloaded, but I had to drop 4 (undamaged) to complete the mission ...

Error message at the end of the mission once on the bridge with 1.0.3 version

Hi cfrag I replayed version 1.0.2, after transporting the troops and secure the airport, I arrived in the zone of the bulkers for transport of the crates. After selecting a cargo with F6, there was no smoke. I flew over the bulkers and saw that there was no crates, nothing on the decks. This is the first time this has happened. Note : at the airport, the mission can continue only if all hostile are destroyed, even if only one with 1% vitality remains.