Tanuki44

CW = Clipped Wing ...

A simple text file with a custom extension just like a cfg or ini. Probably a DCS specific file, sdef sounddef, I suppose ... For the maximum value, only the tests will tell you

I don't have the P-51D module activated anymore but if I compare the 'default.lua' in the folder TF-51D\Input\TF-51D\joystick, the lines are : {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')}, while that of the P-51D : {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')}, Try changing the 4 to 2, I think that a member had already given the info ...

Open the sdef file with a text editor: wave = "Effects/Aircrafts/SpitfireLFMkIX/Cockpit/ValveDrainHissIn" spatial_crosstalk = true inner_radius = 10 outer_radius = 100 attack = 0.15 release = 0.3 gain = 1.2 The gain can be changed.

Without the btd's file, I can't hear anything... I put the file here C:\Users\username\Saved Games\DCS.openbeta\Sounds\sdef\Aircrafts\SpitfireLFMkIX\Cockpit\ValveDrainHissIn.sdef it's different from your path C:\Users\username\Saved Games\DCS.openbeta\DCS\Sounds\sdef\Aircrafts\SpitfireLFMkIX\Cockpit\ValveDrainHissIn.sdef The sound is audible only in the direction down to up... difficult to know if the volume is too low or not, is the cockpit volume at 100% ? Maybe increase the gain value in the file according to your own settings ... gain = 1.5 or 2.0 Thanks to btd for the file

Your link points to the I-16 but you talk about the Spitfire...

It's like Christmas Eve

Is it normal that in the P-51D.lua, the Nominal_RPM value is the RPM Limit? .../... engine = { Nominal_RPM = 3000.0

The ideal is mapping axis for each trim, with the adjustment of the curves, we can really refine the setting. Especially since there is a response time in the flying dynamics.

Personally, the zoom is equivalent to a cheat mode, I don't think our eyes are equipped with it For the TrackIR, I use the EDTracker module and for the zoom, I have assigned an axis of my controls( helico or warbird) exclusively to this function. In RL, there is no physical reason for the zoom to be associated with head movement. The axis gives good stability. This is just my opinion, all the other tests made me feel nauseous

Yes, but is't efficient to use all the dataflow and power through a single port USB ?

You should have write 'I do not need ...'

I use 'AutoHotKey' with this script : ; ---- 'JoyR' is the 4th axis of the joystick ---- 'JoyU' and 'JoyV': The 5th and 6th axes of the joystick ---- 97% or if (GetKeyState("JoyR") < 3) 3% along the throttle axis curve 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) ; Enable the loop function only if throttle is down or if (GetKeyState("JoyR") < 3) in the normal or reverse direction of the axis { Loop 12 ; counter for number of pressure 'PageUp' { SendEvent {PgUp Down} Sleep 20 SendEvent {PgUp Up} Sleep 20 ; (optional) if the pulses are skipped } } return

I forgot to check the folders in MODS, two of them had the wrong 'Input' folder. By removing them (useless since they are AI planes), everything became functional again. Thanks for your help

Dans les Menu des Commandes : Onglet Interface Quelque soit la rubrique (General, Interface, VR), dès que l'on essaye de modifier une assignation KeyBoard ou autre périphérique, DCS commence à collecter les commandes des profils et se bloque. In the Commands Menu : Interface tab No matter which section (General, Interface, VR), as soon as you try to modify a KeyBoard or other device assignment, you will see that it is not possible to change it, DCS starts collecting profile commands and crashe.

It seems I misspoke ... I mapped a button with a repeat function to 'go up' to idle ground. (0% of throttle) When the cursor is at 'idle ground', the axis mapped on the throttle works perfectly ...

No, just start engine with throttle on idle ground. Have you finished the start procedure ? I just tested, all works ...

Did you follow the Peter's orders correctly? - - Let’s use the time and set up the Altimeter. Elevation is about 1130 feet MSL or according to the Weather information from BATUMI close to 29,92 inches of mercury - - Start up the engine - - Check Frequency's on ARC-51 Preset 2 and ARC-131 CHARLY/MAIK Checkpoint 52,00 - - Switch all the Radios on including the ACR-134 witch is still set to BATUMI TOWER and in order ?

I agree with you I'll just explain what is needed to activate the rotation mapped on an axis Excuse my bad English expression

When cold, the rotation is not done because you have to unlock the throttle before you can turn it. To unlock it, you must press the PAGEUP key several times so that the cursor passes the iddle ground position then the rotation of the axis is functional. In fact, it lacks the ability to unlock with just a button click. To compensate, I programmed with autohotkey the repetition (~12 press) of the PAGEUP key on a button.

Test my fix

I think my correction in the file : clickabledata.lua corrects the problem. Pending the official correction of ED Decompressable file usable directly with OvGME TF-51D.zip

The value is defined in the file : P-51D.lua Line 60 : M_max = 4800, -- kg => 10582 lbs http://www.u-boote.fr/p-51.htm https://en.wikipedia.org/wiki/North_American_P-51_Mustang Maybe 100% is not the authorized max value but a security value ...

MAX is the weight limit of what the plane can take so 100% This value does not increase, on the other hand, TOTAL indicates the load of charge. % = TOTAL / MAX This is identical for other modules, planes or helicopters.

To test, a simple mission with a departure aligned on the runway The flaps are in up position, the handle is in the 50° position After dropping the flaps in down position (5 press on the 'F' key). After one press on SHIFT + 'F', the flaps go back from 10° (one step), but the handle goes back to 0°. The flaps do not follow the number of keypress and the handle is always desynchronized. This bug doesn't exist with the P-51D.