2 hours ago, Elvensmith said:

you have to adjust the throttle  according to the phase of flight

No you don't. The only time you need to adjust it, is in the takeoff phase. The PFD will actually tell you to set it to CL detent after takeoff. Beyond that, you leave it there the whole flight until 20 feet from touchdown, where you are warned to "retard" the throttles. It couldn't be simpler.

2 hours ago, Elvensmith said:

Asobo should have included a tutorial flight(s) to familiarise users with the quite different Airbus procedures

I'm thinking people might check Youtube tutorials showcasing the FSLabs or Toliss buses. The procedures are the same and you'd get valuable information for comparison purposes.

4 minutes ago, Keto Ketchup said:

You guys saying you have zero issues, I'm assuming this doesn't include all the actual bugs in MSFS that have been confirmed by Asobo itself? Otherwise you're saying the sim is perfect (it isn't) and every problem is the user's fault (also false).

If Asobo has confirmed a bug, then it is indeed a zero issue. They are working on it. In that sense, I've had zero issues. Plus, I expect a triple A game to be buggy at least 6 months after release.

 

Just now, airlinejets said:

I'm thinking people might check Youtube tutorials showcasing the FSLabs or Toliss buses. The procedures are the same and you'd get valuable information for comparison purposes.

I have been following some of the YT clips by "A320 Sim Pilot" (who states he is a real A320 driver) and they are very helpful. In fact I just picked up from that about the throttle gate position prior to reading your further comment.

Just now, Elvensmith said:

I have been following some of the YT clips by "A320 Sim Pilot" (who states he is a real A320 driver) and they are very helpful. In fact I just picked up from that about the throttle gate position prior to reading your further comment.

There are some amazing youtube videos of the 320. We're also very fortunate that the people behind the FlybyWiresim are constantly updating it.

On a completely different angle - worth checking your Win 10 is up to date.

On a hunch I just checked mine and for some reason it had stuck at 1904 (so not even at the minimum 1909 recommended for FS20). Now got it running the upgrade process to 2004. Probably not a huge difference in the scheme of things but there might be the odd dll which has received an update and makes things work better.

As a matter of fact, they just updated it a few minutes ago. I'm not sure what was done but the download size went from 105MB to 120MB.

 

edit

I think they added many new sounds.

Edited October 2, 20205 yr by airlinejets

9 minutes ago, Elvensmith said:

On a completely different angle - worth checking your Win 10 is up to date.

On a hunch I just checked mine and for some reason it had stuck at 1904 (so not even at the minimum 1909 recommended for FS20). Now got it running the upgrade process to 2004. Probably not a huge difference in the scheme of things but there might be the odd dll which has received an update and makes things work better.

My install of Windows was stuck on that exact update and i tried every guide out there to fix it to no avail. Finally reinstalled Windows after formatting drive and all is well. 

At the risk of veering slightly off topic I think I might have disabled auto updates on the main PC after 1903 initially borked something with my motherboard - couldn't see my secondary SATA drives. That problem eventually went away but suspect I left it in manual!

35 minutes ago, Keto Ketchup said:

You guys saying you have zero issues, I'm assuming this doesn't include all the actual bugs in MSFS that have been confirmed by Asobo itself? Otherwise you're saying the sim is perfect (it isn't) and every problem is the user's fault (also false).

keto, who is saying that??? no one as far as i can see.

everyone sees issues, but its a different matter to let those get you frustrated, thats all about a mindset.

and its possible to fly around most, also i doubt if anyone is happy with the way updates went sofar, too many new bad bugs.

 its very obvious that this is going to take  a long time before it really delivers what it promised.

in the meantime , i do have fun ,. flying low and slow.

13 minutes ago, Elvensmith said:

At the risk of veering slightly off topic I think I might have disabled auto updates on the main PC after 1903 initially borked something with my motherboard - couldn't see my secondary SATA drives. That problem eventually went away but suspect I left it in manual!

Actually i think this post is right on topic. Hopefully we can put together a checklist for people having problems, and this is definitely something to add to that list. 

46 minutes ago, Keto Ketchup said:

You guys saying you have zero issues, I'm assuming this doesn't include all the actual bugs in MSFS that have been confirmed by Asobo itself? Otherwise you're saying the sim is perfect (it isn't) and every problem is the user's fault (also false).

Oh it’s a bug fest alright. But some people have a broken sim due to constant CTDs, install problems, etc. and we are trying to stop those people from losing their minds. 

This topic is useful. 

https://forums.flightsimulator.com/t/love-the-sim-but-hate-that-i-ctd-50-of-flights-with-ucrtbase-dll-error/283509

People are heavily modding the sim plus the developer is making frequent, large updates at the same time.  I don't think everyone gets how a mod that worked fine with a previous version can break after a patch.  I'd bet the people who keep their sim more vanilla and manage mods better are having fewer issues.  Asobo is putting lots of undocumented updates in these patches too, so that makes things even harder. 

On top of that, you see a lot of intermittent bugs that aren't easily reproducible.  Those are the hardest to track down.  I work as a software developer and software testing, and even I can't fully understand a bug as it happens and then disappears before I can get any useful info on it.  I've seen bugs once or twice only since launch.  Anything that intermittent is going to mean some people might not see the bugs at all.  

17 hours ago, RobJC said:

Actually i think this post is right on topic. Hopefully we can put together a checklist for people having problems, and this is definitely something to add to that list. 

Thanks Rob.

Update went smoothly though for anyone contemplating this, took nearly 4 hours from start to completion - so don't kick it off before bedtime or if you wanted to do something else on the PC. I followed that by grabbing the latest Nvidia driver update.

Now arising from that, something else people might want to check is if your Nvidia (or AMD) desktop settings have changed. This is particularly important if you are connecting with your monitor via a HDMI lead as by default Nvidia will set "Limited" mode for the colour output which does not cross the full 256 RGB range. You need to go into desktop settings and use the pull down menu to change this to "Full". Otherwise you will not be getting pure black or pure white and could be responsible for the washed out look. Also worth checking your brightness, contrast and gamma settings - even 50% is probably too bright for most users, end up burning your eyes.

In fact it's probably good practice to check the display settings haven't reverted to the default, whether it's a Windows or GPU driver update.