[MSFS2024] Pilatus PC-12 NGX

I just hate how the files are hidden and encrypted. I would love to tweak the colors on the Honeywell.

There are two main things keeping me from this plane:

  1. The heat blur effect is ■■■■ and intrudes into the cockpit and across my view in VR so I can’t see anything
  2. The avionics are so washed out/low contrast that I can’t really read it in VR without leaning forward and sticking my face in the screen
4 Likes

Yeah that looks odd for sure. It shows you having only used 3lbs according to the fuel flow sensor which is clearly not the case.

I never really paid much attention as I’ve only flown this a couple times.

The avionics were made by Working Title so should be able to do what you want no?

New to the PC12 here… how do you make the cabin temp comfortable?

1 Like

They are still generally embedded with the aircraft files

Not simulated AFAIK.

1 Like

Where would we find those files?

Like I said above, they are with the aircraft files, so under microsoft-pc12-ngx or something like that, I forget exactly.

But to get them you have to use the Dev Mode VFS Projector, and while you can view them, you can’t modify or copy them as they are encrypted.

how did you get AT to work for the climb phase? when I try it set to FLC it just pins the throttle and makes my ITT gauge go red near instantly.

In 2024 the PC-12 is a death trap, no heat an no pressurization, if you want realistically to stay alive, stay below 15000ft. Then you can go as high as 19000 feet, or even higher depending on outside atmospheric pressure, before hypoxia kick in and kills you.

This may seem a joke, but it’s not. :rofl:

My biggest complaint so far is the taxi speed at idle. I just broke the landing gear going over the bridges at Orlando and have to restart. (No O2 is minor IMO, I can live with flying low while waiting for the fix.)

Having to ride the brakes is a pain.

5 Likes

Wait for it to be fixed. :frowning_face:

Im still manually controlling the throttle, not using the auto throttle. For career mode yes, the auto throttle will really stress your engine and will probably break your plane pretty quickly.

On take off I just put the throttle a little bit below all the yellow/red lines, I guess its like 75% throttle, even less possibly. I leave the throttle at that and then once I am ready to put the autopilot on with FLC mode, the plane will just climb as fast as it can whilst maintaining 140 kts, which is absolutely fine.

Its better than using vertical speed mode.

1 Like

I use FLC to climb and just set the throttle manually to keep everything in the green

5 Likes

It’s such a shame that this aircraft has so many bugs. Tried a couple of DCTs but that wasnt working for me, and it also didnt want to capture the ILS at all (not even showing it on the PFD, while the freq was correct for sure).

1 Like

the PC-12 has an optional Honeywell SmartRunway™ and SmartLanding™ system (a sort of RAAS on steroids), but i don’t believe it can actually autoland in real life.

in any case i don’t think those systems are implemented in the game, otherwise we’d get aural warnings (“too high, runway too short, too fast, unstable approach”, etc).

1 Like

Ah ok, yeah good to know.

Yeha I have no idea if that is the “real life” way of doing it, I am trying where possible, so I have all the visual aids etc turned off, but I am still a bit of a noob, getting to grips with the navigation system.

So basically what I am trying to say is I had no idea if it would land it or not, but I just left the AP on to see what would happen, and it did land it on teh runway.

I was basically more pleased I managed to get the plane to follow the glide path down.

Infact, as you seem to know a bit more than I do, can I ask what your method is for decending?

For my climb, I just set the altitude on the knob and also in the FMS computer, and I manually control the throttle, use FLC mode, the plane climbs as fast as it can at 140kts and that seems to work fine for me, plus doesnt stress the engine like it will do using auto throttle.

However I have no idea what the correct way (or working way) of decending is?

The ATC seems to be very awful and telling you when to decend, most of the time it doesnt at all, and you’ll fly over the runway at cruising altitude. So what I have been doing (and I appreciate this ISNT correct) is just eyeballing the distance to start decending, then use vertical speed mode and manually control the throttle so I get a smooth decent without overspeeding it.

I then try to be reasonably low so I intercept the glide path from underneath as I get close to the runway. I usually try to get down to about 2000ft over the runway altitude, then usually about 2nm (give or take) thats when it’ll intercept.

But I know this isn’t the correct way, the trouble is, if you try and use FLC mode to decend, the plane will literally dive at the ground, overspeeding and braking the plane.

As far as I can tell (again, me being a noob most likely) there isnt a way to tell the FMC to start the decent, like you can on the 737 for example.

That being said, I have not been pressing the VNAV button, so maybe I should be doing that, and the flightplan should already have the various altitudes set for each waypoint?

ATC has no conception of actually “landing”. it will very often ask to you to climb to cruise altitude when you are on a 3 mile final. VERY RARELY it will give you descent instructions and/or just tell you to cancel IFR and resume VFR, but usually i have to either request descent 5 miles before the TOD mark (if i can be bothered), or just cancel IFR (i usually do this).

if the plane has a proper approach programmed, and you have VNAV engaged and you have dialed your altitude down below the cruise altitude, it will capture the vertical path at top of descent* and smoothly fly you down using autothrottle and VNAV along a computed path which will put you exactly at the final approach fix (2000 ft above the runway, 6 nautical miles out, ready for a standard 3 degree descent). the autothrottle usually does a pretty good job at this. it is very bad at holding a speed on the actual glideslope though and starts chasing itself. disable it and manually set the speed.

*you will usually only see a Top of Descent marker if your programmed flight plan is contiguous (no discontinuities) and ends on the ground at runway. if you don’t see the TOD marker, check that those bases are covered.

although it can be used to descend, in practice i mostly use FLC for emergency descents. VS is safer in the descent, because you have control of the descent speed (the reverse of climbs, where VS is short for “very stupid” because it can easily lead to a stall if you’re not watching your airspeed.)

once VNAV has brought you to the Final Approach, you can enable APR mode, and the plane will switch from using GPS path to following a glideslope (assuming you have chosen an ILS or RNAV approach), otherwise you have to do it yourself VFR.

hope that helps!

4 Likes

It is total disaster. I am unable to handle with this GA… Too bad with too many bugs… My heart is burning with anger.

You sure you are referencing the PC-12 NGX?