From Jummivana, the Community Manager from Microsoft:

 

Quote

Also one last note, as you have noticed on the most recent Feedback Snapshot, the ‘Press Any Key to Start’ Wishlist item was slated to go live with Update 4 (1.9.5.0) but it was not released today with the update. After investigation, we found it to be an error from our team. While this is being fixed and slated for an upcoming release, it was never meant to come out in Update 4. We apologize for the typo and will update the Feedback Snapshot in the coming Dev Update accordingly!

https://forums.flightsimulator.com/t/forum-announcements-bugs-issues-moderation-and-feedback-snapshot/300759

Looks like they just made a typo in the October 8 snapshot.  For me, it’s not a big deal since the bigger bugs like the VFR map CTD bug is fixed. Overall from what I have seen and from the comments from others that have tried this patch up to now, this patch is a step in the right direction.

Edited October 13, 20205 yr by abrams_tank

Too me it still doesnt seem liek they did much...with the graphics or Draw distance.

On the roadmap for updates and bug fixes  anything hat has to do with LOD or Draw Distance is classified as NOT STARTED and TOO BE INVESTIGATED. Kinda dissapointed.

 

Dont know how I'll survive if I have to press any key to continue.

It is an awkward mistake though... could not be more "High Visibility"..

Edited October 13, 20205 yr by Bert Pieke

2 minutes ago, AmeliaCat said:

Too me it still doesnt seem liek they did much...with the graphics or Draw distance.

On the roadmap for updates and bug fixes  anything hat has to do with LOD or Draw Distance is classified as NOT STARTED and TOO BE INVESTIGATED. Kinda disappointed.

 

Companies dont have infinite man power. Theres much more pressing issues than that. Not to mention its more than likely an "easy" fix. Hence why its not started and more difficult problems are prioritized.

You'd think they'd go above and beyond on the QA front after the recent shambles. 

2 minutes ago, AmeliaCat said:

Too me it still doesnt seem liek they did much...with the graphics or Draw distance.

On the roadmap for updates and bug fixes  anything hat has to do with LOD or Draw Distance is classified as NOT STARTED and TOO BE INVESTIGATED. Kinda dissapointed.

 

I think they wanted to fix the most critical bugs in this patch like the VFR map CTD bug and at the same time, they don’t want to break things and cause further bugs. The LOD and Draw Distance fix may be much more complex and a shallow attempt to fix it may cause more bugs.

From my understanding, they are resurrecting the player testing group to test the VR patch release.  I agree with you that they need to keep up with a high volume of fixes and feature additions, but I also think it’s okay if they do that once they have a player testing group to test patch releases.

I think for this update, they wanted to stabilize things without breaking things further. So at least for this update, I agree with their decision.  But once they have that player testing group up and running to test patch releases, they need to go back to releasing more fixes and features for each patch.

1 minute ago, Drumcode said:

You'd think they'd go above and beyond on the QA front after the recent shambles. 

I'd guess they probably have on the backend dev and QA work, but still some work to align the comms and marketing folks... being transparent is a double edged sword

Can you imagine these poor people responsible for preparing the feedback snasphot? And these publishing this on the net? And their managers? And the Asobo boss who said on the interview how easy is to fix that? 

But at the beginning of the chain was one guy who misunderstood the content of update 4. Or who is just blamed for it. He most probably won't be able to sleep well tonight...

They just destroyed all the potential positive response to the hard work of the entire team working on the patch.

They are not very lucky recently:

- 1.9.5.0 - all destroyed by the "Press any key issue"

- 19.9.3.0 - all positive reception of Japan destroyed by VFR map, tall buildings and LOD issues

- the previous one - Airbus issue, sensitivity interface issue.

Is it continuous bad luck or rather management issue?

Edited October 13, 20205 yr by Steku

Next thing you know, they'll be trying to sell us oceanfront property in Arizona.

No way the feedback summary charts don't go through multiple levels of review before being published.

Edited October 13, 20205 yr by marsman2020

There are community fixes available for the "press of a key" and for the "tall building" bug, so I will survive to the next patch.

11 minutes ago, Bert Pieke said:

And, it looks to me that the "Tall Buildings fix" was incomplete, at best.

I have put the 1.9.3. Community fix back in.

(And yes, I did delete my Rolling Cache first..)

Look in your Content Manager and see if your Japan-Procedural Buildings and Japan-Points of Interest items are up to date. I was having the same issues and took the advice from someone on the MFS Forum to make sure these are updated. They were not, so I updated them and it all worked properly. Give this a try.

Also, the file that is affected by the "Tall Buildings fix" (distribution.toml) seems to have changed quite a bit with this update so I would caution reverting back to a older version of the distribution.toml, which basically had a number of lines ripped out. Could cause other problems as this seemed more of a hack than anything. 

 

Just now, Ixoye said:

There are community fixes available for the "press of a key" and for the "tall building" bug, so I will survive to the next patch.

Where is the fix for "Press of a key" ??

1 minute ago, MikeT707 said:

Look in your Content Manager and see if your Japan-Procedural Buildings and Japan-Points of Interest items are up to date. I was having the same issues and took the advice from someone on the MFS Forum to make sure these are updated. They were not, so I updated them and it all worked properly. Give this a try.

Also, the file that is affected by the "Tall Buildings fix" (distribution.toml) seems to have changed quite a bit with this update so I would caution reverting back to a older version of the distribution.toml, which basically had a number of lines ripped out. Could cause other problems as this seemed more of a hack than anything. 

 

 

OK, will do.

2 minutes ago, Bert Pieke said:

OK, will do.

Please let us know how it works out.