12 hours ago, Gregg_Seipp said:

The airplane *should* switch over to mach somewhere around FL270...ish?

The plane auto-switches to Mach mode at 31,500 feet, which is the same altitude that it switches to half bank mode. You can manually switch to Mach before that by pressing the center of the “Speed” knob. I typically climb in speed mode at 250 knots to 10,000 feet then increase to 290 knots passing 10,000. I manually switch to Mach when the Mach for 290 knots hits 0.76, which usually happens around FL280 or so.

The super critical airfoil of the real (and simulated) CRJ wing is most efficient at high speed. Under no circumstances should a cruise climb be attempted at something like 160 or 180 knots. The pitch required to hold that slow speed in climb would result in a massive increase in drag. 

Edited March 29, 20224 yr by JRBarrett

15 hours ago, avhpilot said:

found out that the problem derives from me having a 1st gen i7 CPU

...

So i have to buy a new computer because neither aerosoft nor microsoft seem to fix this

Yeah it's a total bummer that they won't support hardware from two decades ago. 🙉🙈🙊

Yikes.

2 hours ago, kiwikat said:

Yeah it's a total bummer that they won't support hardware from two decades ago. 🙉🙈🙊

Yikes.

Not the biggest AS lover but IIRC that cpu topic is WASM related and thus rather attributable to MS/Asobo

7 hours ago, kiwikat said:

Yeah it's a total bummer that they won't support hardware from two decades ago. 🙉🙈🙊

Well, the thing is, they did when i made the purchase. and then, a few months later, they did not.

By the way, my CPU (i7 980x from 2010/11'ish) is still capable of delivering great fun flying in VR with all other aircrat in FSX, X-PLANE11 and, to my amazement in December 2020, in MSFS2020 VR as well. As a matter of fact, MSFS2020's performance on my old system is that 'acceptable' still that there is no immediate urgency to buy a new PC.

 

57 minutes ago, avhpilot said:

Well, the thing is, they did when i made the purchase. and then, a few months later, they did not.

 

According to the article below from August 2020 the minimum supported for MSFS has always been an Intel 4th Gen.

So basically you are using a CPU that is 3 generations earlier then the supported minimum and are upset that a developer is not supporting your CPU on their product ?

https://www.windowscentral.com/microsoft-flight-simulator-pc-requirements

It is really good your system can run MSFS 2020 acceptably. BUT it is still not supported, there is no obligation on anyone to make sure these old CPUs still work, if things work that is just good luck on your part.

Edited March 30, 20224 yr by Glenn Fitzpatrick

16 minutes ago, Glenn Fitzpatrick said:

According to the article below from August 2020 the minimum supported for MSFS has always been an Intel 4th Gen.

So basically you are using a CPU that is 3 generations earlier then the supported minimum and are upset that a developer is not supporting your CPU on their product ?

https://www.windowscentral.com/microsoft-flight-simulator-pc-requirements

It is really good your system can run MSFS 2020 acceptably. BUT it is still not supported, there is no obligation on anyone to make sure these old CPUs still work, if things work that is just good luck on your part.

Yes you are correct. 

Upset? what makes you think that? just dissapointed i am slowly running out of luck. But hey, it's about time for a new PC anyway

 

1 hour ago, avhpilot said:

Yes you are correct. 

Upset? what makes you think that? just dissapointed i am slowly running out of luck. But hey, it's about time for a new PC anyway

 

I was in your very same position and jumped onto the upgrade train after my 12yr old i5-whatever was excluded from the club. Did not regret it, just gave me a valid reason to build my modest new PC

All's been great but still it doesn't want to climb to anywhere near its rated altitude.  Today had a lovely flight from KJAC to KSBA and during climb with MAX power it began being unable to make it past about FL360 after which it stopped its climb and started losing speed and eventually was again headed for a stall.  Our climb rate was around 220 and switching to mach was something like 0.60 at this altitude.  I'm not getting any ice warnings and this time I did make sure wing anti ice was off to not lose the power that happens when it's on.  Anything else I should be paying attention to for this issue?  

Never mind I haven't used JB's Rx and that is to use a much higher climb speed so am trying that now...

Edited March 30, 20224 yr by Noel

44 minutes ago, Noel said:

All's been great but still it doesn't want to climb to anywhere near its rated altitude.  Today had a lovely flight from KJAC to KSBA and during climb with MAX power it began being unable to make it past about FL360 after which it stopped its climb and started losing speed and eventually was again headed for a stall.  Our climb rate was around 220 and switching to mach was something like 0.60 at this altitude.  I'm not getting any ice warnings and this time I did make sure wing anti ice was off to not lose the power that happens when it's on.  Anything else I should be paying attention to for this issue?  

I think you’re climbing at the wrong speed.  I select speed 290 after 10,000 feet and then switch over to continue the climb at Mach 0.74 when that equals my actual speed, somewhere usually in the 20-25,000 foot range.  You shouldn’t be anywhere near Mach 0.6 at 36,000 feet.  Note that you need to manually switch over to Mach speed and not wait for it to do it automatically.

Edited March 30, 20224 yr by Gilandred

5 minutes ago, Gilandred said:

I think you’re climbing at the wrong speed.  I select speed 290 after 10,000 feet and then switch over to continue the climb at Mach 0.74 when that equals my actual speed, somewhere usually in the 20-25,000 foot range.  You shouldn’t be anywhere near Mach 0.6 at that altitude.

Yes as I mentioned in my edit I am following JimB's recommendation and it's much better now thanks--up to FL360 w/ a rate of about 800.   I simply did 290 then let it switch itself to mach at FL315 and all's well ;o)  And that mach was 0.80. 

Edited March 30, 20224 yr by Noel