7 minutes ago, mjw8899 said:

I honestly think some people here are paid by MS or Asobo, because while previously I had been unable to complete any flight under any flight plan, now, post patch I have no airplanes except for a c152. Now I know I will be told that its my system, or its my impatience or

 

They pay for this! Oh man where do I sign up? 

2 minutes ago, Frostbitexp said:

Probably because complaining about problems over on the official forum where Asobo lives actually does something and makes issues known to them. But creating duplicate topics venting about the same issues on a forum Asobo pays no mind to doesnt do anything.

 

Time for glasses my dude.

IT SAYS NOT STARTED TO BE INVESTIGATED   sorry for dup post I dunno why it didnt qoute the first time

 

8 minutes ago, mjw8899 said:

I honestly think some people here are paid by MS or Asobo

 

Say no more! LOL

Yes I do believe though if ASOBO hire few CFIs (not those transitional hour builders) things could  go much smoother with their "improvement". Some CFIs do have college degree in computer science, you know  ;););)

Well, well, well it looks like I rubbed some here the wrong way.

Some of you need to take a break from posting at AVSIM.  I would give some of you a long vacation.

Unfortunately I don't have the power, so keep making word not allowed of yourselves.

Bunch of ASOBO sycophants!

Edited October 13, 20205 yr by DJJose

1 minute ago, mjw8899 said:

Now I know I will be told that its my system, or its my impatience or whatever, but the product is just obviously broken and I am not sure its getting better.

There are usually tthree types of bugs   Systemic, Configuation and Environmental.  Systemic bugs happen on all systems regardless of the configuration.  The VFR map CTD or "large buildings" bug is an example of this. These bugs are usually the easiest to fix as they manifest themselves universally.  They are usually low hanging fruit because they can be easily identified and quickly resolved.

Configuration bugs are harder to suss out.  The Avionics shutdown bug was an example of this.  It appears that only users who had a specific setting enabled in options (which btw, had nothing to do with avionics at all), experienced the bug quite frequently, whereas those who did not have that setting didn't have it at all.  These bugs are not much harder to fix, but can be a lot harder to replicate because you first have to determine what it is in the configuration that causes it to occur.

The hardest bugs to replicate and fix are environmental.  Those deal with the end users environment.  Your bugs are of that variety.  There is not a single "setting" which erases all your airplanes, nor does there appear to be a setting that prevents the completion of a flight plan.

Those types of bugs usually require the assistance of technical support to help troubleshoot and resolve.  They often result in having to clean out folders, or reinstall so that a baseline can be established.   

If you are patient enough with this type of process, even these issues can be resolved.  But if your answer is to somehow expect the developer to have clairvoyance into your specific machine and be able to automagically resolve your particular issues based on the scant information you just provided in this thread, then you are setting yourself up for disappointment.

5 minutes ago, AmeliaCat said:

IT SAYS NOT STARTED TO BE INVESTIGATED   sorry for dup post I dunno why it didnt qoute the first time

 

Yes, but its still there under the list of bugs. So they are aware of it. Again, they cant work on every single thing at once.

Be happy you could even update. I am in a endless loop install. Unreal.

I do not see this going anywhere except for a gripe session and we have a lot of those.

Locked