5 hours ago, regis9 said:

"To start, press any key." Well where's the "any" key? I see Esc, Catarl, and PigUp. There doesn't seem to be any "any" key!

― Homer Simpson

 

I too had this issue. I even purchased a genuine MS keyboard but alas no "any" key to be found  on that either.

I have however found a great work around. Simply write the word "any" on one of those sticky post-it note things and attach it to your space bar.

The system then recognises  the space bar as your "any" key and continues as normal.

 

 

On a more serious note it is rather annoying and i am unclear what function it is meant to serve. It is not as if you get any other choices you either press a key or have to kill the game in task manager.

8 hours ago, ChaoticBeauty said:

The problem is that because of the long time that it takes to load into the menu, people want to get up and do something else meanwhile. You cannot do that while this step exists, you have to stay and press a key to make sure that the simulator is fully loaded by the time you get back. It is not about the minor inconvenience of having to press a key.

 

Absolutely!  Great ID of the "problem determination".

Edited October 28, 20205 yr by fppilot

I still get the japan add to update when I

Already have anyone else?

3 minutes ago, Bigsby said:

I still get the japan add to update when I

Already have anyone else?

I do get the Japan marketing blurb but my background screen is now a shot of that South African ZU registered Jabiru J170, even though it is not in the marketplace yet.

I assume you have actually gone into content manager and downloaded the japan update ?

I have a better idea that will solve everyone's problems:

Why not have the sim boot you back to your desktop? I mean, might as well save yourself the arduous wait for the menu, the tedious wait for the sim to load into the aiport, and and the laborious task of actually flying the plane.

I have an even better idea that will solve problems:

Why not blacklist these forums on your browser? I mean, save yourself the guaranteed reaction of getting riled-up by people raising their issues about MSFS, the effort required to mash the keys on your keyboard in response, and the inevitable despair when people continue to discuss all things MSFS that aren't to your personal liking.


No-one has the right to police people's own experiences and thoughts surrounding MSFS. We're a disparate group of individuals with different needs and desires. The fact that "press any key to start" is an issue that ranked as one of the top user concerns means a top developer like Asobo should investigate and respond. And being sensitive to their customers' wishes, they responded (well, sort of).

 

14 hours ago, Ricardo41 said:

I don't get it, why is this at the top of the bug list? 

Boggles the mind. 

So, an additional 1 second of pressing a key is more troubling to folks than the dozen or so other issues?

Maybe you have missed the moaning here when MSFS was released, complaining that one second of their life is just so important to waste and Asobo/Microsoft has listened and said okay, we are going to get rid of it. This is just a proof that Asobo/Microsoft listens to the community. 

28 minutes ago, F737NG said:

I have an even better idea that will solve problems:
Why not blacklist these forums on your browser?..

I wouldn't worry about even replying.  Some people here are starting to become (or have been for some time actually) just a constant stream of negativity and hot air.  It is like they are trying to gag people or putting them off posting or something.  It's like watching a grumbling old man moan about everything that is not right with the world.  I am actually beginning to find it funny now. 😄

I think this is down to the "I want it! And I want it 3 weeks ago!!" brigade.

48 minutes ago, SierraHotel said:

I think this is down to the "I want it! And I want it 3 weeks ago!!" brigade.

Exactly! This should have been fixed at SP1.

Live weather should have been addressed SP2.

Fail to plan, plan to fail.

36 minutes ago, DJJose said:

Exactly! This should have been fixed at SP1.

Live weather should have been addressed SP2.

Fail to plan, plan to fail.

ohhh SP1  like 14 months after release  and SP2   16 months after?    okay sounds like a recommendation 🙂

 

Graham

18 hours ago, Ricardo41 said:

I don't get it, why is this at the top of the bug list? 

Boggles the mind. 

So, an additional 1 second of pressing a key is more troubling to folks than the dozen or so other issues?

It is a top WISH LIST item not a Bug list item. 

Very easy to confuse the two and usually they show the bug list first, for some reason ton the last update hey showed the Wishlist first.

People should understand how things work in a complex development environment.  The order things get finished isn't the same as their priority.  Something lower priority may get done sooner simply because it is a lot less work.  It isn't like they decided to put effort into the any key removal over say fixing the G1000.  They are working on the G1000 and that is going to take a lot more time.  The fact that relatively simpler things find their way into release sooner doesn't mean they were deemed more important, just quicker to work on.  

Between coding, testing and waiting for fellow workers to get related pieces done, we spend a lot of time on things that aren't the #1 priority, because that's the most efficient way to work.  If my #1 task is waiting on something, I don't take a break and stop working, I look at the #2 priority.  If the #2 is complex and long, I may even go much further down the list and grab something small I can get done.  That doesn't mean that the #1 still isn't getting as much attention as I can give it.  

It can look odd from the outside (we frequently have to have the same conversations with our customers), but there is method to the madness.  This is a relatively new trend in development.  Like it or not, it is pretty much standard for any kind of development.  The goal is to get as much total "stuff" done for the customer in the time given.  Sometimes that means knocking off things way down the priority list because that's just the way the work fits.  

1 hour ago, kerosene31 said:

People should understand how things work in a complex development environment.  The order things get finished isn't the same as their priority.  Something lower priority may get done sooner simply because it is a lot less work.  It isn't like they decided to put effort into the any key removal over say fixing the G1000.  They are working on the G1000 and that is going to take a lot more time.  The fact that relatively simpler things find their way into release sooner doesn't mean they were deemed more important, just quicker to work on.  

Between coding, testing and waiting for fellow workers to get related pieces done, we spend a lot of time on things that aren't the #1 priority, because that's the most efficient way to work.  If my #1 task is waiting on something, I don't take a break and stop working, I look at the #2 priority.  If the #2 is complex and long, I may even go much further down the list and grab something small I can get done.  That doesn't mean that the #1 still isn't getting as much attention as I can give it.  

It can look odd from the outside (we frequently have to have the same conversations with our customers), but there is method to the madness.  This is a relatively new trend in development.  Like it or not, it is pretty much standard for any kind of development.  The goal is to get as much total "stuff" done for the customer in the time given.  Sometimes that means knocking off things way down the priority list because that's just the way the work fits.  

Yes exactly.  Take the low hanging fruit first!

A large customer request, an easy fix, get it done, off the list.  That's all this is.

I think it would be funny if they forgot to put it in the patch again after all of this!   😄

Does anyone know the gender of the Any Key?  Asking for a friend...