Have you tried to start the PC-6 from Cold and Dark

User Support Hub Aircraft & Systems
, , ,
1

Does anyone have tried to start the Porter from cold & dark ?
Does it work ?
If yes, how did you do ?

2

Yep, struggled a bit as the checklist doesn’t highlight or focus the camera on whatever control it’s referring to (something I’ve only experienced in third-party aircraft so far) but muddled through and got airborne.

Didn’t feel like the rudder was doing it’s job as I was taking off - narrowly avoided veering off the runway into a hangar, despite having assistance set to true-to-life.

Landing was fine however.

3

Do you mean that you succeeded to start the engine following the check-list ?

1 Like
4

I also managed to start the engine from cold and dark with the checklist. As mentioned above the highlights are missing, so if you are not familiar with the cockpit layout, it will take some time to find the correct switch.

The Porter is a beast, and you need to pay attention to proper trim settings before take-off (note that large sticker on the instrument panel).
The IRL POH says this on the before take off checklist:
- Rudder trim GREEN MARK (7° right)

1 Like
5

Alright thanks, I’ll check that out later.

29

Is there anyway to get the Pilatus PC-6 to spawn cold and dark? Mine already has some switches turned on.

2 Likes
30

Well, it seems that there are significant differences between steam gages and glass cockpit versions. I managed to start and fly the steam gage version yesterday, but not the glass one today. Weird.
Also, the glass cockpit version has a working gust lock, the other not. I also miss the rudder trim indicator, or any kind of feedback on the trim status before taxiing. The steam gage version has an elevator trim indicator, at least.

31

Same here, battery and gen is on, also Garmin displays.

1 Like
32

Same here. Thought I was missing an assistance setting

33

Got the glass cockpit version working, what part did you get stuck on?

34

Whats even worse: unlike the Milviz version this one is unable to go into Beta-mode

Kinda sad - its a unique feature of the PC-6 after all

35

As well as all the active switches, the beacon is also on for me when opening the PC-6 in the Hangar, from the menus. (Presumably the same cause - it spawns in the hangar with almost everything ‘on’.)

Might be worth moving this to the bugs forum?

36

It does not react to the throttle. This issue seems to happen randomly to me (both in the glass and steam version), and I have to dig into the details. I really want to understand whether it is a bug, or I do something wrong.
I have already seen that others have filed reports with similar issues.

37

If it’s not reacting to the throttle, make sure the fuel valve is in the correct position. I don’t believe it’s labeled, but it should be pointing in the vertical position. This confused me because the Milviz version has it in the horizontal position, so it’s opposite in this version. The fuel valve is located in the bottom left corner area. You’ll know it’s right if the ITT starts to climb.

1 Like
38

With a quick check yesterday I wasn’t able to start the PC-6 with CTRL + E (“auto engine start”). Yes, I know, I know
 CTRL + E.

But I wanted to give it a quick try. What happened was that the propeller did indeed start to rotate, but there was no distinct engine sound to be heard. Also, the tooltips kept reminding me to “auto-start the engine with CTRL + E”. And releasing handbrakes (yes, I did that ;)) and pushing the thrust upwards did not make the aircraft budge.

So anyone else having more luck with CTRL + E? I will try to follow thec checklist next, but again, wanted to give it a quick try yesterday and failed with CTRL + E


UPDATE: The problem persists (so it wasn’t a freak incidence yesterday). But for whoever this may be useful, a workaround (besides properly following the checklist ;)) is to:

First, make sure that “Assisted Checklist” is turned on:

  • Go to settings (ESC)
  • Select ASSISTANCE OPTIONS
  • Select PILOTING
  • Enable option ASSISTED CHECKLIST
  • Apply & save settings

Then at the parking space (“cold and dark”):

  • Enable checklist (SHIFT+ C)
  • Select second menu entry “STARTING ENGINE”
  • Click the AUTO COMPLETE PAGE

Et voilà, the engine starts properly. I haven’t figured out yet what this checklist does what CTRL + E does not do - maybe someone else has spent more time with the checklist yet?

And yes, also referring to the Asobo PC-6 version here.

2 Likes
39

Can anyone tell me where the rudder trim gauge can be found?

40

Hello,

don’t know if this is your issue but I’ve discovered that after Update sim brokes my assistance settings completelly. After reassign all again I can start it without problems but main stick/yoke doesn’t move, rudders and throttle ok.

41

All assistance options were indeed all (re-)set to “Easy”, so I adjusted those to my preferred settings.

But whatever the assistance options are, they should not prevent CTRL + E to auto-start the engines, of course. But either way, CTRL + E does not seem to work


What’s more, I just realised that FS 2020 has reset all my assistance options back to “Easy” again. Duh. But that’s another issue then


42

YES.

I discovered this strange issue after Update finish and load Porter first, at parking. Some strange Tips and messages appeared that I knew that something was broken with Assistance. But when I had look at that, that mentioned Tooltips are OFF set :slight_smile: so I did next options as I need and quit FS. After that, Porter can start with CTRL+E but that main stick doesn’t move, in other planes what I tested all is ok.

43

Oh, so you are saying that CTRL + E actually does start the engine for you, but you simply cannot move the steering stick? That’s interesting.

And it might indeed be related to key assignments (I hardly change them ever from their default settings, but I remember some past update where my keyboard / mouse / joystick profiles were indeed set to “Custom” and hence some important new key assignments were not done (which, from a technical standpoint might have been correct: “don’t automatically modify custom profiles”).

So if this CTRL + E runs some startup sequence which relies on (new?) default key sequences then this might be something to check then.

But with my workaround above I can move the steering stick around (and also the throttle), or in other words: once the engine is running, I can fly with the PC-6 just fine.

By the way my assistance settings are now kept as well just fine, so not sure what made them reset to “Easy” before (I did, however, uninstall the LSZH airport from Asobo - perhaps that caused a “reset” of the assistance settings?).