Jump to content

Recommended Posts

Posted

Only one direction (Opening) is mapped to button action on joystick or throttle "Canopy Closing", the keyboard action works fine.

 

Throttle: VPL CM-50 v2

Stick: VKB Gunfighter MK iii

 

zprwsp-6.png

 

Posted

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 ...

Posted

Yeah. Do you remember the update where we got the clouds ?  The P-51 has been broken since that update.

The solution of Tanuki is what works for me. You have to do it after each update.

Also the airflow-levers are fubar since that update. You can edit another .lua to correct that. Must be in the bugs somewherre.

Posted (edited)

With the latest update, the TF-51D module has been modified identically to the P-51D, so now both modules are broken for the canopy ...

 

I modififed again 'pressed = device_commands.Button_2'  and it works now ...

 

----

 

I don't remember, I only tried the P-51D with the trial period after the release of the 2.7 and now the period is over.

 

I can just test with the TF-51D module, can you confirm the keyboard shortcuts? 
 

 

 

 

 

Edited by Tanuki44
Posted

@NineLine

 

Hey friend, I know this one has been reported, but the fix is literally changing just two instances of the number "4" to a "2" in the lua file.

 

It makes no sense that it's been a few patch updates and this has persisted -- is there not some way to nip this one in the bud?

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...