As software engineer myself, sometimes I feel sorry for Asobo devs when I read some comments in Avsim. 

So, at this point, it seems like the best thing to do would simply be to shut down the sim until 12/6, and then do the public beta, because we'll see no relief in the weather issues (ground haze, temperature spike above FL240 until then?

6 hours ago, fppilot said:

Hope so!  The MSL vs AGL cloud base issue is NOT the same as the haze issue, and I see no mention of the haze issue.  I steadfastly hope the cloud issue has not restricted Asobo's vision of all the issues!  You just don't have 1/2 mile visibility on the ground with clear skies and less than 60% humidity.  I have see that several times since the last SU. I don't believe they have modeled grass or forest fires yet!

Well, if it isn't the same thing, they'll be sure to hear about it during the public test...

1 hour ago, roland said:

A minor thing to fix but by the look of things they couldn't care less. Very disappointing.

Come on - clearly mentioned in the first post of the thread:

COMMUNITY TRIAGE UPDATE

Click here for the Known Issues List. There are several bugs our dev team is currently tracking for fixes ASAP and will provide an update as soon as we can. Here are some of the top reported bugs in the community:

....
6. All assistance options automatically gets set to easy every time you relaunch the sim or sometimes between flights
    The team has confirmed and identified the issue. A fix is in place for an upcoming release.

54 minutes ago, JDWalley said:

So, at this point, it seems like the best thing to do would simply be to shut down the sim until 12/6, and then do the public beta, because we'll see no relief in the weather issues (ground haze, temperature spike above FL240 until then?

Another solution, mind you, is that you don’t start the sim on your computer 😁. I’d rather have that.

If people have issues they fear aren't fixed yet, then can i suggest joining the Beta on Monday so you can test and report issues to MS/Asobo and maybe get them in the final release

I think this opt-in beta is a great idea, but I am just a bit worried about the 'might have to reinstall' thing, so I will have to read the instructions very carefully.

It sounds like the patch is going in the 'default' location which I assume is on the C drive.
I currently have MSFS installed on my E: drive, which is a fast NVME M.2 type, so I might be alright.  But I don't want to lose MSFS it as it is a 3-day download for me.

Then again, does anyone know how bit the beta patch is likely to be based on past participation?  It sounds like it might be another full shadow installation.

Edited December 3, 20214 yr by bobcat999
It changed my C: to a smiley for some reason!

Just now, bobcat999 said:

I think this opt-in beta is a great idea, but I am just a bit worried about the 'might have to reinstall' thing, so I will have to read the instructions very carefully.

It sounds like the patch is going in the 'default' location which I assume is on the 😄 drive.
I currently have MSFS installed on my E: drive, which is a fast NVME M.2 type, so I might be alright.  But I don't want to lose MSFS it as it is a 3-day download for me.

Then again, does anyone know how bit the beta patch is likely to be based on past participation?

If you are concerned about the beta potentially wiping things out, do you have anywhere you could backup your MSFS folder to ?

That way if the worst does happen you can restore the folder and point the MSFS application at it.

6 hours ago, saifs said:

Yes, you're not the only one. I'm having to now zoom on to the EFB switch on the JF Turbo Arrow (in VR) to switch it on or off because of the now tiny and displaced hotspot. The knobs on steam gauge heading indicator is also all wonky. 

Turn off lens correction in the settings. Then that will fix that for now 

39 minutes ago, bobcat999 said:

I think this opt-in beta is a great idea, but I am just a bit worried about the 'might have to reinstall' thing, so I will have to read the instructions very carefully.

It sounds like the patch is going in the 'default' location which I assume is on the 😄 drive.
I currently have MSFS installed on my E: drive, which is a fast NVME M.2 type, so I might be alright.  But I don't want to lose MSFS it as it is a 3-day download for me.

Then again, does anyone know how bit the beta patch is likely to be based on past participation?  It sounds like it might be another full shadow installation.

Last time I was in the beta; it wiped my whole install after. And it wasn’t worth it, at all. 

So the word MOUSE is missing from the very VR topic associated with the Bug, they can't be that stupid to miss this surely....will await the patch notes!

The Flight test is egg on their face for cancelling the SU7 one, especially as Jorg in the Q&A said he wanted to give the team a good break over the Xmas period and now they're having to go through this due to the strict release schedules. Lessons have not been learnt, my hope of them learning anything from these fiascos grows slimmer by the day.

Again Steam users not in a Flight test, this has to change, an Opt-In *without the pointless NDA* is urgently required but they still need to listen and act when bugs are reported, unlike in the past. Again it all boils down to the severe lack of Quality Control, which has not improved at all since release (and according to alpha testers even earlier).

I'm thankful that they've got their arses into gear, however they still should've communicated better and not left it *TWO* weeks to inform us. I just hope the Hotfix doesn't break other areas that are currently working fine...#FingersAreFirmlyCrossed

Edited December 3, 20214 yr by MarcG

5 minutes ago, MarcG said:

an Opt-In *without the pointless NDA* is urgently required

This won't happen. Everyone privy to unreleased builds, information, etc., in the industry has to sign a NDA. This isn't something concocted for Microsoft Flight Simulator, it's industry standard.

One of my associates, a couple of weeks ago, went down to visit a games developer for something unrelated to any game in development, but they still had to sign a NDA before arrival just for entering the building, in case they saw something not yet public knowledge.

5 minutes ago, March Hare said:

This won't happen. Everyone privy to unreleased builds, information, etc., in the industry has to sign a NDA. This isn't something concocted for Microsoft Flight Simulator, it's industry standard.

One of my associates, a couple of weeks ago, went down to visit a games developer for something unrelated to any game in development, but they still had to sign a NDA before arrival just for entering the building, in case they saw something not yet public knowledge.

I've been in Open Opt-In betas without NDAs before so I wouldn't say it's an industry standard, either way they need to open up the beta to everyone (i.e. Steam users) and ultimately listen and act on the bug reports - that's the main issue here!

Hm... don't understand the happiness of some here... Instead of releasing the fixes, which are in place already, they want to do a public beta, and NOT for Steam (which I am on, of course) and NOT today but monday and who knows how long that beta will take and you might have to reinstall MSFS...

Things are already broken so fixes can only FIX them or keep them broken: what worse can happen? So why don't they simply release the fixes TODAY?! I also expected a hotfix sooner that this...

57 minutes ago, March Hare said:

This won't happen. Everyone privy to unreleased builds, information, etc., in the industry has to sign a NDA. This isn't something concocted for Microsoft Flight Simulator, it's industry standard.

One of my associates, a couple of weeks ago, went down to visit a games developer for something unrelated to any game in development, but they still had to sign a NDA before arrival just for entering the building, in case they saw something not yet public knowledge.

Since Mondays Beta is open it seems it won't be under NDA (no watermarks either, thank goodness)

Edited December 3, 20214 yr by Matchstick