**** Official Microsoft Flight Simulator Thread ****

My cpu usage is very low running between 2-4%. :confused:
During flight my game froze momentarily and then frame rate dipped from around 24Fps to 17-18Fps and cpu usage went from around 20% to 1-4%. Very strange :confused:

Playing on High Settings in 1440P 144Hz resolution.

[email protected]
GTX 970 Stock
64GB DDR4 3800Mhz CL17



 
I finally did an IFR landing. I'm not sure if it was me or not but seems very hit and miss. Auto pilot needs some help with the altitude even when it's dialed in, sometimes doesn't change. Am I missing something ?
 
I finally did an IFR landing. I'm not sure if it was me or not but seems very hit and miss. Auto pilot needs some help with the altitude even when it's dialed in, sometimes doesn't change. Am I missing something ?

What type of approach were you making (e.g. ILS) and in what aircraft?
 
My cpu usage is very low running between 2-4%. :confused:
During flight my game froze momentarily and then frame rate dipped from around 24Fps to 17-18Fps and cpu usage went from around 20% to 1-4%. Very strange :confused:

Playing on High Settings in 1440P 144Hz resolution.

[email protected]
GTX 970 Stock
64GB DDR4 3800Mhz CL17



Could you have run out of vram? 3.5gb isn’t nearly enough for this sim?
 
What type of approach were you making (e.g. ILS) and in what aircraft?

Airbus A320.
Simple departure from Heathrow and then landing in Gatwick. ILS 26 (I didn't think the number made any difference).

Tower would advise a certain altitude. I would then acknowledge and dial it in. Unless I guided the nose myself it would rarely follow the input even though the target altitude would show up blue on the main dial.
 
Airbus A320.
Simple departure from Heathrow and then landing in Gatwick. ILS 26 (I didn't think the number made any difference).

Tower would advise a certain altitude. I would then acknowledge and dial it in. Unless I guided the nose myself it would rarely follow the input even though the target altitude would show up blue on the main dial.
Once you dialled in the altitude, how did you activate the FL change?
 
You need to both select an altitude (or FL) and then activate a climb or descent mode, whether that be managed CLB/DES by pushing the alt knob, Open CLB/DES by pulling the alt knob or selecting an appropriate V/S on the V/S knob and pulling.

The only time when you can simply change the Altitude selection is when you haven’t yet reached your selected level and are still in an active climb or descent mode.
 
Last edited:
You need to both select an altitude (or FL) and then activate a climb mode, whether that be CLB by pushing the alt knob, Open CLB by pulling the alt knob or selecting a positive V/S on the V/S knob and pulling.
That’s why I like the FBW mod, I prefer descending using a 3 degree angle as that’s what most glide scopes are set as, with the exception of London City, which is practically falling out of the sky!
 
Right so the Alt nob has 2 options. Click in or out. I recall it saying "engage mode" or change mode. There's no feedback anywhere when you do either one of these.
 
Right so the Alt nob has 2 options. Click in or out. I recall it saying "engage mode" or change mode. There's no feedback anywhere when you do either one of these.

FMAs at the top of the PFD tell you what modes are engaged. FBW has better FMAs than the stock model.

Pushing Alt knob in should result in a managed descent or climb (there are a few occasions when it won’t but that’s a bit beyond this conversation) which will respect constraints. Pulling it will result in open climb or descent which doesn’t respect flight planned alt constraints and will continue until it reaches the selected altitude where it’ll revert to Alt* for capture.
 
FMAs at the top of the PFD tell you what modes are engaged. FBW has better FMAs than the stock model.

Ok I'll look out for it. So assuming if there is a climb mode there is a descend mode?

So auto pilot on -> change altitude on nob to desired level -> CLB mode if climbing -> engage nob. Check PFD to confirm mode.
 
@robfosters Ah right got you… yeah the stock model doesn’t have FPA.

In general (as always there will be exceptions) we’d only fly in TRK/FPA when doing a non precision approach or visual. All the rest of the time (99%) it’s HDG/VS.

@Buddy it’s context sensitive… eg pulling the knob with an altitude set below will result in open descent and pulling it with an altitude set above will result in open climb. Also see my above post as I edited with a little more info.
 
Last edited:
Thanks will test it out. The game really should have more comprehensive training for airliners. I've been spending hours going through YouTube videos.
 
Hmmm good point. It is a possibility that 3.5gb may well be affecting the gaming performance. But in terms of cpu usage the sim update 5 should have been helping with this also.
It’s just a thought but if vram is hitting a wall then cpu useage would drop too as no point pumping out more fps if gpu can’t handle it. I would run gpu-z and see what the perf.cap is.
 
Thanks will test it out. The game really should have more comprehensive training for airliners. I've been spending hours going through YouTube videos.

Haven’t looked at them, but actually decent comprehensive tutorials for complex aircraft is not necessarily an easy task… especially when the stock airliners in the sim have very low systems fidelity.

There are some very good content creators on YouTube focused on the A320 who are Airbus pilots… you would probably find more value from their tutorials and using the FBW (or upcoming fenix) than you’ll ever get from Asobo and the stock aircraft.

Or you know, stick to flying something actually really fun like VFR in a spitfire ;)
 
Last edited:
Back
Top Bottom