2 hours ago, Donstim said:

Reference? Asobo has repeatedly said the target audience is simmers first. Can then also make it accessible to other with various assists.

Well we shall see. I just believe money drives everything first.

On 9/22/2020 at 8:28 PM, C130FE said:

Seems that everytime I try to fly it's always something.  One time I fly and the autopilot works perfectly.  The next time I fly the same airplane the autopilot a total disaster.  The heading bug still will only move 10*.  I thought FSUIPC7 was supposed to take care of that but it does not.  The update did not take care of it.  Every time I go to fly, I start at the runway, I'll push the throttle up and the engines quit.  Every time.  So I have to restart the engine/engines.  Every single flight is something different.  I'm about to go back to P3D because I just can't take it anymore.  Yeah, the scenery is hands down better than anything else we have, but I just want to take a pleasant VFR flight and enjoy it instead of trying to keep the airplane from crashing as soon as I engage the autopilot.  I am not about to reinstall this program, it took tech services over an hour and a half to get this program to load on my computer..Not going thru that again.  And I'm not going to go and start making 50 tweaks to try and get this thing to work.  I have an excellent computer and on the off chance I get things to work, it is a fantastic experience, but they are getting few and far between.  Just looking for a reason not to have to go back to P3D.

I'm sure, that you must do something wrong. After last patch there are only one significant problem with A320Neo engine no.1 stops during preflight procedure. It can be fixed by don't switch APU and APU bleed off before take-off. Next the plane fly exactly as I want, include AP. And I can fly every off others smaller planes too without any problem. I can use their autopilots with every modes, like ALT,  VS, HDG, NAV (to localizer or FMS plan), APR with ILS etc. I can fly every VFR and IFR procedures. I haven't tested only the biggest planes (787 and 747), but every smaller yes and I enjoy it.

I strongly suspect that about 80-90% of these "bugs" that people are reporting post-patch are either user error,  something specific to their computer set-up, or the result of bungled assignments within external controllers.

The problem is this: the folks experiencing these "bugs" scream at the top of their lungs, starting thread after thread, thus pushing a discussion of legitimate concerns as well as posts with helpful tips off of the front page.

I really don't understand why avsim doesn't put a sock in these whine and cheese posts.

43 minutes ago, ludekbrno said:

I'm sure, that you must do something wrong. After last patch there are only one significant problem with A320Neo engine no.1 stops during preflight procedure. It can be fixed by don't switch APU and APU bleed off before take-off. Next the plane fly exactly as I want, include AP. And I can fly every off others smaller planes too without any problem. I can use their autopilots with every modes, like ALT,  VS, HDG, NAV (to localizer or FMS plan), APR with ILS etc. I can fly every VFR and IFR procedures. I haven't tested only the biggest planes (787 and 747), but every smaller yes and I enjoy it.

Also, since the patch...try turning with water rudder, the Icon to the right...good luck...she will start to turn...and then you go straight...with the rudder fully right deflected.   There are so many new bugs...that I sit with a can of RAID....beside my joystick....

It's only been a month....

23 minutes ago, Ricardo41 said:

I strongly suspect that about 80-90% of these "bugs" that people are reporting post-patch are either user error,  something specific to their computer set-up, or the result of bungled assignments within external controllers.

I strongly suspect that you are wrong. Black avionic screens for starters. 

I've done at least 9 flights post-patch and have never encountered this issue  of "avionics turning off". Flights ranged in terms of distance from 200 to about 900 nm. I have a word not allowed 5-year old PC .

You have to accept: The Game was released months too early. Its in an alpha status. Needs many patches. Nice for screenshots, but not more in my opinion (maybe manual flying as well).

But no IFR.

I accepted it, i will try with every patch, but starting to play/simulate seriously with FS20, i will wait until next years.

So long, i am having more flying fun with DCS, BMS, Sturmovik 46 and Sturmovik BOS and P3D.

17 minutes ago, Paladin2005 said:

Nice for screenshots, but not more in my opinion (maybe manual flying as well).

But no IFR.

That was known before the sim was released.  Not 'news'

The best VFR sim,  ever created - covering the entire world,  with so much to see -  and everyone is crying about IFR.   The mind boggles.

Edited September 24, 20205 yr by ErichB

12 minutes ago, ErichB said:

That was known before the sim was released.  Not 'news'

The best VFR sim,  ever created - covering the entire world,  with so much to see -  and everyone is crying about IFR.   The mind boggles.

"Erich...I just want to take an MSFS sled up...without it trying to virtually kill me....".

I've been flying almost exclusively IFR, so I don't agree with this "no IFR" stuff. Just a few simple workarounds and I don't have the airplane ever trying to kill me either. While I am expecting many improvements and they should be sooner rather than later, I am still able to successfully accomplish most aspects of IFR flight, but not entirely realistically. 

7 hours ago, Ricardo41 said:

I strongly suspect that about 80-90% of these "bugs" that people are reporting post-patch are either user error,  something specific to their computer set-up, or the result of bungled assignments within external controllers.

The problem is this: the folks experiencing these "bugs" scream at the top of their lungs, starting thread after thread, thus pushing a discussion of legitimate concerns as well as posts with helpful tips off of the front page.

I really don't understand why avsim doesn't put a sock in these whine and cheese posts.

I have the MFD set to map and it shows several waypoints which I might choose to fly to.  When I try to do Direct To - I am told the  waypoints are unavailable, despite being on the screen.  How can that be a user error?

I am 10-miles from a VOR (which appears in the MFD map) at 5,000' AGL andNAV1 is tuned to the VOR yet BRG1 shows No Data and changing the CDI to NAV1 shows no path to the VOR.  The VOR appears on the MFD map. User Error?  

I am flying an ILS approach as indicated by the information line in the PFD and the CDI.  The altitude tape shows a diamond for the Glide Slope and I see GS in the information line.  The AP takes me down the GS from the IF but when it reaches the MDA it stops descending and holds that altitude and crosses the threshold at the MDA.  Is that a user error?

I am flying an Autopilot HDG course, which is within 5° of the bearing to the VOR I have tuned in NAV1. The CDI shows the course to the VOR.  I click on NAV and the AP turns AWAY from the VOR and does a 355° standard rate turn to the proper course to the VOR.  But, it continues turning and overshoots the turn by 20°.  The AP hunts back and forth, left and right of the proper course for another couple minutes before settling on the proper course to the VOR.  All that with me not touching any control or button.  User Error?

AND... yes I doubted the BLACK screen / power off of the G1000 but it has happened to me in the Textron G1000 172 twice now in about 10-hours of flight time spread over 20-flights.  I am just flying along on AP at a fixed altitude and have not touched the controls for several minutes when Ding and the MFD goes black but the PFD stays on.  Plain Vanilla system with a CH yoke and pedals.   User Error?

7 minutes ago, TacomaSailor said:

User Error?

No of course not. The modeling of the Garmins are iffy at best. Nothing your doing wrong. Been using Garmins for almost two decades and the default Garmins are poorly missing functionality.

7 hours ago, Sesquashtoo said:

Also, since the patch...try turning with water rudder, the Icon to the right...good luck...she will start to turn...and then you go straight...with the rudder fully right deflected.   There are so many new bugs...that I sit with a can of RAID....beside my joystick....

I deployed the Water Rudder within the cockpit and watched the display say Deploying and waited for the noise to stop.  Then I was able to turn left and right using my rudder controls in 360 degrees up to 30 knots.

I tried this using keyboard rudder commands, My "rocker" on my CH FS Yoke and the Rudder axis on my Thrustmaster T Flight HOTAS x.

Can turn 360 in both directions with the water rudder deployed up to about 30 knots.  Then the rudder starts to lose effectiveness as the plane begins to get on the step.  This is well in excess of the maximum 10 knot limit as stated in the Icon Operations Manual

https://www.iconaircraft.com/wp-content/uploads/2019/09/POH-A5-FE-ALL-CHAPTERS-SAMPLE-ISSUE-A3-ICA012428-F.pdf

I didn't test the deploy water rudder command through the keyboard, only through the cockpit.  I guess that's my next test.  

2 hours ago, Donstim said:

I've been flying almost exclusively IFR, so I don't agree with this "no IFR" stuff.

 

8 hours ago, ErichB said:

That was known before the sim was released.  Not 'news'

The best VFR sim,  ever created - and everyone is crying about IFR.   The mind boggles.

The problem with the best sim ever created for simmers for which we paid premium for is that most of the NAV data in which they in episode 8 IFR and every YT promoter "omitted" to mention is missing and in which has been in other sims for over 7 years and where they still refuse to address the issue and for which now the AIRac is officially outdated which makes the most basic official VOR/ATC/IFR flying useless. So yes some in the community are getting seriously frustrated.