agfors

Yes DH lights flash intermittenty on the ground, even after a reset, and can arbitrarily flash on descents too even well above the descision height. To the extent that i'm not sure they function at all as intended. I'm always havnig to reset them.

Thanks for confirming. It's not just me then. Others aren't seeing this presumably because hey are not doing stepped climbs below 10000 ft. Currenly I'm having to use Autothrottle in AT (speed) mode with 250kts dialled in and v/s mode to get above 10000 ft then using TM+VNAV to avoid the issue. It seems tha EPR only gets set under some conditions, but currently on when hitting VNAV after a stepped climb below 10000f. Above 10000 ft I sometimes get stuck at the500ft/min climb rate because EPR isn't being set correctly. All in all a bit frustrating.

The NAV1 DME switch on pilot side when switched to 'normal' enables NAV1 & NAV2 DME on pilot side Similarly NAV2 DME switch on copilot side when switched to 'normal' enables NAV1 & NAV2 DME on copilot side On other aircraft I have flown and what I'd expect is NAV1 DME switch on pilot side when switched to 'normal' enables NAV1 DME on pilot side & NAV1 DME on copilot side NAV2 DME switch on copilot side when switched to 'normal' enables NAV2 DME on pilot side & NAV2 DME on copilot side Anyone else find this to be the case?

AS strange as it sounds the HSI only displays DME for INS waypoints, so if you switch to VOR even though the HSI shw VOR course/direction, the DME is still showing INS distance. DME for VOR1 and VOR2 are shown on the small HSI gauge to the left of the main HSI. You have to have DME switches on the AP panel toggled to 'normal' too. Makes no sense to me but is supposed;y how it was on TriStar.

Assumption: If my understanding is correct I should be able to use the TriStar AP with TM+VNAV modes engaged shortly after takeoff, so say for example by 2000ft, I should be able to engage both TM+VNAV and that should allow the aircraft to climb to the set target altitude at IAS250 <10000ft and IAS320>10000ft. The takeoff, climb pages in the PMS should set the correct EPR into TM system target for each phase of flight. I am seeing several issues with TM+VNAV on stepped climbs <10000ft including - TM with IAS250 does not hold airspeed at 250kts or perhaps it just gets there VERY slowly. It frequently overshoots to 300kts! (v1.0.5 release), and 270kts on previous versions IAS250/3230 does not work properly if there is a step climb below 10000 ft. So say I level off at 6000ft first before climbing further, I then dial in new target alt and hit VNAV, the aircraft will not climb at all. To get out of this stuck mode requires toggling AT modes so moving TM->AT->TM then the PMS suddenly sets the correct EPR for climbing with. After encountering #2, when I get past 10000ft, IAS320 will struggle to achieve 320kts as the PMS unit does not set the correct climb EPR into the TM system, so the aircraft climbs at a low +500ft/min climb rate instead So the PMS+TM+VNAV seems bugged when climbing with steps, and it's all down to the correct EPR not being set when it should be. If I use AT mode to hold an IAS of 250kts instead the aircraft behaves normally. If I engage TM after using AT to climb above 10000ft then TM EPR is set and works correctly. So to me there is some bug with TM+VNAV when doing stepped climbs below 10000ft. It just isn't working, and hasn't been since release.

I see that the Fokker F27 was updated to v 1.0.2 with SU5 release. Is there any chance you could publish the changelog, as there are none in SU5 release notes or in the marketplace/mylibrary.

FWIW from what I've observed (with v1.0.3). My spoilers deploy fine on landing only if my autobrakes are actually armed too. When those autobrakes are not armed, the spoilers only deploy when I engage manual brakes.