Nobody is talking in absolutes. No, not all XBbox players are casual gamers. Just like not all PC gamers are serious simmers. Heck I don’t even know what the exact difference is, it’s a fluid transition.
But it is very hard to argue that the core audience, the hardcore flight simmer, is much more likely to be on PC. You are just very limited on a closed platform. No Vatsim for example. No freeware at all. To me and a lot of folks, flightsim is more than just flying. Sites like avsim and the hobby, freeware community has been an integral part of it’s success and longevity for literally decades. The XBox is bypassing all this, in the name of livery DLCs to make a quick buck. Closed ecosystem, closed market.
Instead of focusing on these players, a lot of us perceive Asobo to spend an ungodly amount of man power on somehow trying to make it work on Xbox. And Xcloud. How much time and engineering effort do you think has been spent on the whole Wasm debacle? Value able time that could have been spent elsewhere as it’s just not an issue on an open platform. How much time was wasted fixing the startup crash just recently, time that would have otherwise gone into SU10.
I don’t even get it, you don’t need a top of the line PC to play flightsim. You don’t have to spent 2000 dollars. Certainly not to get a comparable graphic experience as on XBox. And hey, you can mod, and get liveries for free. Imagine that, not having to pay for everything. Might even save money in the long run.
Hey I agree on some of your points, but don’t say time wasted on fixing things like startup ctds issues recently, many spent a fair amount on this sim for Xbox and expect it to work, it was pretty much fine prior SU9, so that needed their full attention.
As for the WASM issue on Xbox, they have that hopefully sorted for SU10, perhaps then can they sort out other issues going forward.
To you it is a waste, since it doesn’t effect you. It is time spent not on your platform.
So what if there was a major issue with a VR headset you didn’t have? Or major time spent trying to track down issues with eye tracking hardware you don’t have, or maybe it is a HOTAS you don’t have. Are those "waste of time"s?
Seafront Simulations had a major issue that ended up being a bug in the sim. Asobo spent a lot of time working on diagnosing that issue with Seafront Simulations. Suppose you don’t have a mod that they spend a lot of time diagnosing an issue. Waste of time?
And there is the problem. If you define what is a waste of time on whether it effects you or not, whether it is a distraction to evolving what you do care about, that is a bit insulting. Because ultimately, you are stating you are more important than the other person effected. So you are saying, you are more important than all XBox users, because spending time fixing XBox issues was a waste of time. You would be more important than the PC user who has the VR headset than has an issue. Waste of time fixing that VR headset.
You can’t define what is a “waste of time” by a measure of whether it effects you or not.
I’ll be honest I’m happy they’re doing this but That doesn’t go without saying that it pathetic it took them almost 2 years to realize this is what should’ve been done from the start.
We’re still saddled with grossly incomplete documentation of the core components of the SDK, including correct descriptions of functionality of many configuration variables.
At this point I’m starting to believe that even Asobo and MS have lost track of what some things do and the only reason the docs are incomplete is the information doesn’t exist at all.
The real problem is that literally nothing you said in your post about the nature of the slowdown bug is necessarily true.
You, and others who do have this issue, should participate in betas and engage and provide feedback. Capture real data to help reproduce this.
For all the actual data collected, this could be users with Windows 10 running Firefox browsers and with Spotify subscriptions who have the right combinatorial edge case to encounter this bug.
No one can fix it because no one knows what it is. It’s as likely to be a bad coexistence interaction as a core sim issue.
In fact, the simple case that most people cannot replicate this indicates it is not an obvious common-to-all core issue.
Look around this forum just after a SU drops. Many users who participate in their BETA say that problems were encountered, & logged, only to see the problem appear in the SU official release. A person can only feel ignored so many times before they stop offering feedback.
Encountered and logged is only the tip of the iceberg in terms of a resolution. If it’s not breaking, sometimes you have to leave it in and find more data to reproduce.
We cannot even disconnect a USB peripheral without the game crashing, that’s instability right there. The sim is riddled in bugs and not stable, to pretend otherwise…
Fine, but you suggested that we, users with issues, should do our part and join the BETA and report. Well we do and do not see the results. We are doing our part, often to no avail. How the internal process works, is not of our concern, the final product is.
I am a very serious flight simmer. I’m now on Xbox for a variety of reasons. Personally I think it’s possible to get MSFS working at an acceptable level of performance for all of us. I am an ex-PC user by the way. I don’t think you can generalise when it comes to MSFS users - just look around at the huge diversity in use cases and needs in this forum, if you want an idea.
That’s great as far as I’m concerned - if I’m able to help any user here I will regardless of whether they’re deemed serious or not or what platform they use. That just isn’t important at all as far as I’m concerned. We all deserve a stable MSFS UX and we should be supportive of anyone who is experiencing troubles and try to help them resolve issues - and that may include lobbying the dev team if we need to.
Personally I think that The QA process needs to be improved - stability is much more important than new features, it’s a complex SW system and it’s difficult to get sufficient SW test coverage unless there’s a concerted focus on resolving some of the key issues - updating unstable software can lead to problems with the configuration that might only be resolved by a rollback eventually - an unwanted situation for everyone… I’d like to see a level of guaranteed performance on PC and Xbox - a kind of SLA that is maintained through each update cycle. Something like that is needed I think.
