My resolve to stay out of MSFS betas is weakening by the day but at the moment I'm still on the fence. Might cave and slip in this weekend though.

2 minutes ago, Malaromane said:

My resolve to stay out of MSFS betas is weakening by the day but at the moment I'm still on the fence. Might cave and slip in this weekend though.

It does break the PMDG 737 in a small way - you can't set the comms frequencies manually. If that's important to you, wait for the release. PMDG is working on a fix, but it's likely they will release that only after the beta goes into full release. 

2 minutes ago, FlyingGoose said:

It does break the PMDG 737 in a small way - you can't set the comms frequencies manually. If that's important to you, wait for the release. PMDG is working on a fix, but it's likely they will release that only after the beta goes into full release. 

I'm mostly a GA guy so the PMDG issue won't really affect me. But a fix for that issue has been found (by Asobo as it's an issue in MSFS rather than with the PMDG) and should be available sometime in the next day or so from what I've read in other posts.

4 minutes ago, Malaromane said:

I'm mostly a GA guy so the PMDG issue won't really affect me. But a fix for that issue has been found (by Asobo as it's an issue in MSFS rather than with the PMDG) and should be available sometime in the next day or so from what I've read in other posts.

Yes, just saw this over on the PMDG forums. Looks like this should be fixed today/soon. 

 

****UPDATED INFORMATION FOR 09DEC22****
A few moments ago, Asobo advised that the bug causing the nav radio operation and nav radio switching problems in the Beta-MSFS stream has been identified and resolved internally at Asobo. The fix is expected to publish to Beta-MSFS users beginning today, 09DEC22.

Once this fix is propagated to Beta-MSFS users via the MSFS beta update, the issue will self-resolve without any further effort required of the user.

Please note that this fix will come to you as a fix to the MSFS platform, not as a fix to the PMDG 737- it is not a PMDG micro update, but is a platform update from Asobo.

All of us at PMDG would like to thank those of you who worked with us as we tried to identify the issue, and also Asobo for leaping on a fix for the issue so quickly.
****END OF UPDATED INFORMATION FOR 09DEC22****

 

Link - https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/229358-09dec22-updated-notam-for-all-pmdg-737-for-microsoft-flight-simulator-flight-crew-with-resolution

Edited December 9, 20223 yr by FlyingGoose

What's keeping me out is the threat of potentially having to reinstall my entire sim (I have the MS Store version _and_ I let it install into the default directory) when the beta ends. I _really_ don't feel like having to do a full re-install and even if there's only a slim chance that that will happen, I always seem to throw a losing roll when it comes to beating the odds. 

But I still look forward to reading about all of the improvements that you guys are testing here in this thread.

So I completed my first full flight without any major issues. 

From Mega Airport Berlin-Brandenburg EDDB to Mega Airport Brussels EBBR. Considering I'm running this on a potato, frame rates were ok-ish. 

Manually entered the flightplan, including sid and star, but had to manually edit the flightplan enroute because double waypoints had been inserted. Not sure why. Probably operator error.

I lowered the FMS commanded cruise speed because I was constantly in the red. 

I flew the ILS to RW 1 with no issues, localizer intercept and glideslop capture went off without a hitch. 

i did notice that during vnav descent the plane took a while to get on profile. 

Still getting my head around the auto throttle. 

It really is a completely different aircraft. 

One thing I noticed: there is much more ai than in previous sim versions. 

Here are two non-special and non-edited screenshots:

The BETA (!) Patch for AAU1 is availble in MS Store, at least

17 minutes ago, Ricardo41 said:

Still getting my head around the auto throttle. 

I asked about this on WT's Discord: the auto throttle only brings the speed back to 140 kts, then you need to switch over from fms to manual to slow down to approach speeds. Auto throttle retards at 50 feet agl. 

1 hour ago, Ricardo41 said:

Here are two non-special and non-edited screenshots:

Is it Aerosoft's Simple traffic you are using for AI?

7 minutes ago, Alvega said:

Is it Aerosoft's Simple traffic you are using for AI?

yes

15 minutes ago, Ricardo41 said:

yes

You were having CTD's with FSLTL?

2 hours ago, Malaromane said:

What's keeping me out is the threat of potentially having to reinstall my entire sim (I have the MS Store version _and_ I let it install into the default directory) when the beta ends. I _really_ don't feel like having to do a full re-install and even if there's only a slim chance that that will happen, I always seem to throw a losing roll when it comes to beating the odds. 

But I still look forward to reading about all of the improvements that you guys are testing here in this thread.

I too have the MS Store version and in the default directory. As one who suffered this forced reinstall in the past, let me offer a simple solution that seems to work currently (as least for me): just don't ever leave the beta. Quite apart from the standard recommendations, I do install my beta in the default MSFS directory (because I don't have storage space available for two separate installations). Nonetheless, I've gone through SU9, SU10, and SU11 betas without any problem. My previous, forced reinstall occurred when I tried to leave the beta just before a final release. I think Asobo has been mindful of this problem and has largely mitigated the risk.

2 hours ago, Ricardo41 said:

I asked about this on WT's Discord: the auto throttle only brings the speed back to 140 kts, then you need to switch over from fms to manual to slow down to approach speeds. Auto throttle retards at 50 feet agl. 

I didn't realise you could leave it in FMS that long... Does it slow with flap deployment?

 

G

24 minutes ago, David Mills said:

just don't ever leave the beta

This, it's what I've been doing since the first beta and never had a problem.

3 hours ago, FlyingGoose said:

you can't set the comms frequencies manually.

Comms? I thought it was the Nav Radios.