jrw4

Not directly responsive to the original question, but assignment of the spoiler axis to a Thrustmaster HOTAS slider works fine on my setup. I can't help with regard to the buttons.

Works fine here. You might want to open a support ticket with PMDG. The one or two times I have had a problem with one of their planes, they were able to help me sort it out quickly. Good luck.

Sorry, Rob, but me, too. I didn't switch to FS2024 for the first few months, so I can't speak to that. I have not been satisfied with most of the default aircraft and so stick to payware for the most part. I have no clue why I haven't had problems, but run MSFS as clean as possible with the minimum number of Community add-ons, and only a few bits of support software. My system was purchased in 2022 and wasn't at the cutting edge back then. I do have to limit stuff like traffic and run at moderate graphics settings between medium and high. I run at 2K, capped at 30 fps, and in HDR, but it all fits in the 8K of VRAM. I don't have any third party airports because I learned years ago that this can cause all sorts of problems, but have not had performance issues with Fenix, PMDG, etc. Most all of the problems I have had along the way have been due to user error on my part. This is hugely complex software that works very well if used with a bit of discretion.

I'm not sure if anyone is interested, but this post on the PMDG support forum provides some useful information regarding one aspect of the problem, namely possible issues related to the presence of other add-ons in the Community folder: https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/390136-please-assist-us-understanding-wasm-crashes-better-even-if-you-do-not-see-them?p=390730#post390730 While not as definitive as one might like, the results do suggest that the frequency of WASM crashes is correlated to the total number of add-ons present in the Community folder. I keep my Community folder pretty clean and have had no WASM crashes in FS2024, but if I did, I would empty everything out other than the subject aircraft and see how it goes. But that's just me. Others might find better, easier ways of debugging the problem. Cleaning out caches might help, too. Of course, someone might have better data than was collected by PMDG. Please share so we can all learn. PS It is tempting to say, "It worked last week without crashing, so if it doesn't work this week, I know it's the fault of the most recently installed add-on.", but that might not be the case. If nothing else, the data seem to suggest that the scale of the problem is defined by interactions between the add-ons as much as it is by the add-ons themselves. K.I.S.S. may well be the best advice of all.

Published April 1?

Unless we're shown some evidence, let's not.... So much speculation, so little in the way of facts.

Has the 737 been released yet? I thought it was only the 736, 738, and 739 so far. With regard to the overshoots, no, I can't say I have observed this in MSFS 2020 (737) or 2024 (738). I fly the intercept at Flaps 5 speed, and it seems to work fine so far as I can tell.

It's available in the Market Place. Looks very fine.

Does anyone know whether or not a discount will be available for owners of the current BSQ Analog Caravan? Thanks.

No discernable problems in getting started today in the southeastern US. Could also be a CDN issue with regard to the reported failures. Presumably this will be cleared up "soon".

Wait, what? If one can't tell if the sound package is installed just by listening then why is one even bothering to install the sounds? Why is it necessary to confirm installation if there's so little difference Thanks.

This post goes back to the end of 2024 and reports a problem in MS2020. At the very end, there are two recent responses pertaining to the new 738, which briefly report contradictory results. Are there any posts that specifically address the new add-on?

It appears that there might be multiple sources of the "wobble" phenomenon, of which Chaseplane may only be one. Perhaps this is a good moment to remind everyone that the PMDG 737 Introduction manual has a section on Simulator Settings, Limitations and Compatibility Simulator Settings, Limitations and Compatibility - PMDG 737 Introduction that states in part In addition, it includes a discussion of assistance settings that includes a note that reads as follows: Perhaps it would be good for those who experience what they feel is anomalous behavior (e.g., wobble) to start the debugging process from a state that is consistent with these known limitations.

I haven't seen anything like this. Otherwise empty community folder? Turbulence setting? PMDG support ticket? Best wishes.

No, should it? Just had a totally amazing flight today, my first full A to B journey in the new B738. Totally astounding how well the system performs. Life changing experience. OK, maybe not, but still very satisfying.