34 minutes ago, Manny said:

Q for folks have the CRJ up and running.

I managed  to get the CRJ up and running (It works sometimes) and I flew a full flight plan from Sim Brief from KDFW to KIAH. Did not read any stinking manual. HA HA 🙂

Used the Auto Pilot to navigate the flight which it did nicely but I had a hellaof a time maintaining altitude.. It was weaving up and down by pluss or minus 2000 feet. Been fighting with the throttle and VS to maintain altitude. 

I used the AP altitude tihngi like I would in any aircraft. Tuned in the altitude, pressed ALT button and then the VS and dialed in the VS feets per minute using the Down/UP rollon thingi. It started climbing, but went past my altitude and I had to take over to come down to the level I needed to be. andn then it started the descend, it was up and done the whole trip. But Nav was fine.

Any ideas? 🙂

Manny you really are doing somthing very wrong. PM me your email.

22 minutes ago, Nyxx said:

Manny you really are doing somthing very wrong. PM me your email.

Sent. 🙂

LOL, kind of joking here, but maybe I found the "problem" with SU3.  They're trying to push us to go fly around WU3 areas. 😄 I compared the CRJ's FPS at my local field here in the US just now to sitting at ORBX EGLC with their updated London Landmarks pack, in the current heavy real weather.   I very very very surprisingly got slightly better FPS, lower CPU usage, higher GPU usage.  Those last two are important as since SU3 I've had random airports in the middle of nowhere essentially with the abnormally high CPU usage vs pre-SU3 and it has an effect of killing GPU usage even in external in some planes.  

I.e. normally in some planes I expect to see very high GPU usage externally (like the A32NX) vs when in the cockpit with all the gauges and systems.  With SU3 at airports with high CPU usage that does not happen though.  In this example I'm not talking about comparing to an airport that's literally out in the middle of fields with no cities around (though I've had the high CPU at those as well) but just a more regional airport in a smaller city vs something like KPHX or KSFO which actually give better results strangely.

It's now been 9 days, and they've not even delivered a patch for a game breaking bug.

Someone on MSFS forums claims turning off virus protection helps. I seriously DO NOT recommend doing that even if it works (which seems unlikely) .

Edited March 18, 20215 yr by Glenn Fitzpatrick

7 minutes ago, Glenn Fitzpatrick said:

Someone on MSFS forums claims turning off virus protection helps. I seriously DO NOT recommend doing that even if it works (which seems unlikely) .

It makes no difference to an issue like this

Still listed as "Under Investigation" in the March 18th update - fair enough but I was hoping for more detail on how they are progressing on addressing.  I would hope to have more information on what they have gleaned from the ease of reproducing at Airport 76T.   

17 minutes ago, marcg11 said:

Still listed as "Under Investigation" in the March 18th update - fair enough but I was hoping for more detail on how they are progressing on addressing.  I would hope to have more information on what they have gleaned from the ease of reproducing at Airport 76T.   

Easily reproducible does not always equate to the fault being easy to track down or fix.

You get this in real life aircraft all the time. Examples that come to mind are the yaw instability in the early P51s, especially with full fuselage tanks,  or the history of structural failures in V Tail Bonanza's .

5 hours ago, Glenn Fitzpatrick said:

Someone on MSFS forums claims turning off virus protection helps.

Even if that did help, I already have MSFS folders excluded so it wouldn't matter in my case.

Rolling back to pre update would fix it.....not hard.

From the MSFS 2020 forums; In DEV Mode - disable; "Draw On Terrain" will fix the tanking but you'll lose a whole load of vector stuff and nothing in your Community folder will show up.

More for testing purposes and to point a way to Asobo than a "Fix".

11 hours ago, Republic3D said:

It's now been 9 days, and they've not even delivered a patch for a game breaking bug.

...is exactly the type of thing someone would say when they know nothing about software coding!

They can't just release a patch for the sake of it, they need to reproduce, examine, take time in coding changes, test those coding changes (laughs at the back of the room) then release. If they get stuck at any of those first 3 points then it'll take as long as it takes, now I'm one to call them out on releasing poor patches, but I also appreciate that coding is very hard on a Sim of this magnitude so in this instance they need all the time they can get.

4 hours ago, Nyxx said:

Rolling back to pre update would fix it.....not hard.

How do you know it's not hard? if it's "not hard" don't you think they would've done it by now?!

59 minutes ago, MarcG said:

...is exactly the type of thing someone would say when they know nothing about software coding!

They can't just release a patch for the sake of it, they need to reproduce, examine, take time in coding changes, test those coding changes (laughs at the back of the room) then release. If they get stuck at any of those first 3 points then it'll take as long as it takes, now I'm one to call them out on releasing poor patches, but I also appreciate that coding is very hard on a Sim of this magnitude so in this instance they need all the time they can get.

True, and if they had beta tested the last update before infecting our PCs with it, we wouldn't be in this mess to begin with. 

It is somewhat amusing that people are simultaneously complaining that they rushed the updates without enough time testing and at the same time demanding that they rush out a fix as soon as possible.