Jump to content

[REPORTED] Radiator Flaps axis


Recommended Posts

No possibility to assign axis to radiator flaps control. Only buttons are here.

You do not miss something.

F-14A/B

P-51D | P-47D | Spitfire | Fw 190D | Fw 190A | Bf 109K | WWII Assets Pack

Normandy | The Channel

F-86 | F-16C | A-10C | FC-3 | Syria | PG | NTTR | CA | SC |

Link to post
Share on other sites

I can not explain your screenshot, but what is your version?

 

Because i do not have it in any, i have 1.5.7 stable, 1.5.7 beta and 2.1 alpha...

All are without it.

 

So, i have no idea...

Screen_171102_091545.thumb.jpg.1055e0b5d298fabb093e1bce5f2a42e9.jpg

Screen_171102_091704.thumb.jpg.c1731db7e04c911384456287fd60d45a.jpg


Edited by saburo_cz
pictures

F-14A/B

P-51D | P-47D | Spitfire | Fw 190D | Fw 190A | Bf 109K | WWII Assets Pack

Normandy | The Channel

F-86 | F-16C | A-10C | FC-3 | Syria | PG | NTTR | CA | SC |

Link to post
Share on other sites

In the stable version 1.5.7.10872 the FW-190 D4 has in fact an axis control option for radiator flaps, and I confirm it doesn't work. That same option also exists in 2.1.1.10527 and it has no function there either.

I guess the option was put in by mistake and we should ignore it.

Just like we ignore the axis options for TDC Slew which also appear under the FW-190's axis control options.


Edited by LeCuvier

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to post
Share on other sites
  • 7 months later...
  • 1 month later...
  • 4 months later...

There is an axis command for Radiator Flaps in the file "Throttle - HOTAS Warthog.lua", but it doesn't work.

I tried to create axis commands using info from "clickabledata.lua" with these lines in the "Throttle - HOTAS Warthog.lua":

{action = device_commands.Button_4, cockpit_device_id  = devices.EZ42_GUNSIGHT, name = _('EZ42 Gunsight Brightness Knob')},
{action = device_commands.Button_13, cockpit_device_id  = devices.CONTROL_SYSTEM, name = _('Radiator Flaps Control Knob')},
{action = device_commands.Button_1, cockpit_device_id  = devices.LIGHT_SYSTEM, name = _('Instrument Brightness Knob')},
},

They work kind of, but they utilise only a part of the signal range. The radiator flaps command is almost ON/OFF.

It might be possible to alleviate these problems by reducing the gain values in "clickabledata.lua" and applying curves, but then they would become unusable for pushbutton control. I don't have enough axis controls so I need to continue the pushbutton controls and therefore don't want to mess with gain adjustments.

You guys will have to wait for ED to do their homework.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...