Gustlock and flaps

[sirtopper]

Something that seems to be changed but I don't believe is correct.

If I set the gustlock on I am unable to get the flaps to move. The handle moves but the actual flap dial and external flaps do not move.

If I then turn the gustlock off the flap dial and the external flaps move to the set handle position.

[JGregory]

Just tested this and it is working as expected. 

The gust lock only affects the Ailerons, Elevator, and Rudder... NOT the flaps

Note:  Flaps require Left Battery Bus power AND Main Hydraulic Accumuoator pressure > 1650.0 in order to actuate.

[sirtopper]

33 minutes ago, JGregory said:

Just tested this and it is working as expected. 

The gust lock only affects the Ailerons, Elevator, and Rudder... NOT the flaps

Note:  Flaps require Left Battery Bus power AND Main Hydraulic Accumuoator pressure > 1650.0 in order to actuate.

Thanks for looking at this but there is a problem if you use the commandref's

'les/sf34a/acft/fltc/mnp/gust_lock_lever_on' and 'les/sf34a/acft/fltc/mnp/gust_lock_lever_off'

If you use the mouse to move the gust lock lever then it sets this dataref 'les/sf34a/acft/fltc/mnp/gust_lock_lever' to 0.9 and the flaps work with the gustlock on.

If you use the commandref's to set the gust lock lever on then dataref 'les/sf34a/acft/fltc/mnp/gust_lock_lever' to 1 and the flaps dont move with the gustlock on.

Hope this helps many thanks

[JGregory]

3 hours ago, sirtopper said:

Thanks for looking at this but there is a problem if you use the commandref's

'les/sf34a/acft/fltc/mnp/gust_lock_lever_on' and 'les/sf34a/acft/fltc/mnp/gust_lock_lever_off'

If you use the mouse to move the gust lock lever then it sets this dataref 'les/sf34a/acft/fltc/mnp/gust_lock_lever' to 0.9 and the flaps work with the gustlock on.

If you use the commandref's to set the gust lock lever on then dataref 'les/sf34a/acft/fltc/mnp/gust_lock_lever' to 1 and the flaps dont move with the gustlock on.

Hope this helps many thanks

Yes, you are right!   However, the fix for this is out of the scope of the v1.6 update.  We will revisit this in v2.0.  Thanks for your input.