Your Grandmother was a wise woman … I must try to remember that wise advise when I am active on the forum, and resist replying to some of the Trolls here.
I agree with you in part, but whatever it does its failure state should not be a CTD. The sim should gracefully deal with problems, not just fall over.
That would be great in theory but if the conflict is so catastrophic that the parent programme does not or cannot catch it in time then a crash is all that can happen. It’s actually preferable for it to crash rather than freeze your system.
1 Like
Somewhat facetious I would venture. Having seen photos of your system there is a level of complexity that invites problems. At just 8 months old I think this game is not yet robust enough, in many ways, to handle what some are trying to do with it. It’s annoying for sure but it can be enjoyed with more simple setups for now until the complex plugins and cross communication apps can all behave themselves when running. Major software manufactures regularly break third party addons when they make changes, it has always been that way. It is also well know that the SDK, at present, is not very mature and will invite issues for those developing for it.
I’m primarily wondering if the coffee button was functioning before the update… rofl
Literally my setup requires 3 plugins - the Logitech panel plugin (which I could get by without), the Air Manager service, which only interfaces with SimConnect, and Mobiflight, which is a WASM module. The first 2 of those still work fine.
The thing is, it’s not compatibility that got broken. Asobo outright broke their own WASM connectivity. No WASM modules work now, not even the example one shipped in the SDK. This isn’t a case of 3rd party issues or compatibility. This is Asobo that outright broke their own software.
And to make it worse, the broken WASM was reported by the beta testers immediately. Asobo made the decision to not fix the issue and launch with this rather major bug present.
5 Likes
Coffee is the only one to work actually, is the only one not using MSFS2020
So soon we’ll be closing in on a year after release and you think it’s professional and appropriate to still be breaking things that were previously working?
How “old” does a retail product need to be before we can start expecting it to not break previously working features? lol c’mon man.
1 Like
You phrase the question poorly, it doesn’t matter if it’s appropriate because of course it’s not, but it’s how software is developed. Ask the developers who made Twitter clients how they felt about that company messing around with the API to make their software useless. It happens and it will always happen.
Now that is disappointing to hear.
That’s why I have no faith in the beta process as it’s being run with MSFS.
It’s not that it’s a bad idea - as long as Asobo act on the reports. But history and many reports from alpha and beta testers prove it didn’t work prior to launch. It didn’t work when they started issuing early releases to 3rd party devs, and it won’t work in the future unless there’s an internal change of culture and they actually act on bug reports provided by the testers.
2 Likes
I can’t say I disagree with any of that.
If nothing else, I can imagine when the call comes to beta test WU5, or SU4, those who volunteered their time, and expertise may think differently next time around. Which is a real shame.
Your line of thought doesn’t even make sense because they didn’t modify their API and break a third party plugin.
They released software with another bug (asobo admitted this so it’s not even a debate).
8 Months into a release they should not be breaking core features of the sim (WASM). This is not “third party” related because the third parties cannot take action to fix this. Any WASM module will crash the sim. It is a bug.
1 Like
As far as I’m concerned, this beta process is more of a PR thing than an actual beta program.
As for the testers, because of the way they selected the first 300 applicants, you can bet the majority were just the impatient kids who wanted an early copy of the patch vs people who genuinely wanted to be part of the testing process. This will just invite more of the same in the future I’m afraid.
1 Like
Ideally it would be an arrangement where both parties get something out of it, and above all each party respects the other persons time, because that is exactly what a beta tester is doing, donating their time, for free, to improve the quality of a product they love using. To squander that free resource is bad PR.
3 Likes
Couldn’t agree more. But like with government, it seems that establishing the public perception that something is being done is more important than actually doing something.
1 Like
I agree. They talk so much about how the feedback is important and the community is so important, but when they do something that causes those of us who have spent thousands of dollars in add-ons they say that they want to support to render them useless the least they could do is say something to us in regards to an update. It was the same way during the Alpha which was more understand because there was no charge to for the Simulator but now we are all paying for it and it’s useless for many of us right now.
1 Like
Yeah i cant play with my hardware because everything based on WASM events. C-mon devs you know about it before patch, so why you ignore it? Did you fix it today or tomorrow? It will be nice to can play during weekend.
1 Like
Lots of PPL have also not only MSFS to run with the equipment, but that does not mean that Asobo doesnt has to do its Homework, the equipment was running fine until last update and apparently they new about the issue before releasing the update as some of the 300 testers made hem aware of it before release. So this is a self made issue.