The Xbox Insider Hub - besides the MSFS beta testing - also offers testing for Xbox “Update Preview” (Xbox OS), with various “rings”:
Alpha (newest test, least number of users)
Beta
Delta
Omega (close to final, wider number of users)
Once you have been enrolled in Omega for a long time, their selection algorithm might offer you to join Delta, and so on. I was enrolled in Omega for a while but because MSFS was so buggy it was hard to tell if a bug was due to MSFS or the Xbox OS, so I stopped.
If it was an Xbox update, then it is more than likely an issue with the WASM add-on needing to be updated. I remember when they released it early before an Xbox and MSFS update, if you installed it then it caused a bunch of issues.
Complete guess on my part but I’m sure it will get resolved.
I think a platform-independent system is impossible. Since there are always problems on Xbox. There are differences in the operating system and hardware of the Xbox compared to a PC with Windows and it will always be necessary to make special adjustments for the console version.
Interesting that in this week’s Dev Q&A the specific question was asked, about PC vs Xbox shared code, and Seb did say (around the 35m mark):
It is the same code base, it’s the same project and we can just change the platform, and all the code is shared - but then there is some source code which is exclusive to some platforms. Programmers will know stuff like this which allows you to have lines dedicated to each platform - it’s still pretty rare. Most of the code is shared, and bugs which only happen on one platform are therefore also pretty rare, but it happens. And they are more difficult to identify because you only see them on part of the users or part of the platform …
And that’s fine as long as the developers know what is different and what will behave differently. For now, the SDK simply does not hold that information so we have to assume the code will behave the same on both platforms.
I am supprised that it takes so long to solve this. The 737 was working perfectly on my Xbox-series S till I got the last “update”. I have no longer Simbrief import. No winds import. The calculator on the tablet is doing nothing. I can use the tablet now only to look at my charts.
I can import simbrief to the tablet, but not to the mcdu. So what else is “updated” to my 737? Please give me back my former plane.
We had code that worked fine, but we did not change it, and it stopped working. So either the platform or the ingestion process changed (both out of our control). We asked Microsoft for assistance. If there is anything we need to change, we gladly do it, but after many weeks, we only got the information that they had received the bug report.
It’s highly frustrating, but until we understand what happened, we simply have no way to fix it. On PC we could simply try to do things differently and see if that changes the outcome, but for Xbox even the smallest change you make involves sending the new code through the marketplace process before you can test. That means a few minutes of coding and then waiting a week before you can test. Rinse and repeat.
To ingest poor quality products they are quite fast, a lot comes every week, the only thing missing is the Titanic in this “Flight Simulator”. All support to PMDG and MUST Microsoft/Asobo gives special attention to the PMDG team, as their products are widely used in Sim on Xbox. This is unacceptable.
Is it possible to get a refund of the purchase price for the 737 because this product can no longer be used for me. Under SU14 I only get BS and under SU 15 Beta it can no longer be used because of wasm. In addition, the simbrief import is no longer possible and the tablet no longer offers all functions.
Forget about refunds!!! My recent purchase of ATR is parked in the hanger with both EFB and Avionics Panels cold and dark.This was after perhaps the 1st.or 2nd.Test flight.I am hoping some miracle will happen with SU15 which may restore its electronics so that I can take to air.
The ATR was a promoted plane by Microsoft, so you can assure that it will be fixed before they release SU15.
It seems like people forget what the point of a beta is. It’s strictly for testing your new updates. If they don’t work then they keep testing until they get it right.
The major issue with this beta is that they are trying to fix many things since it’s the last SU for awhile (until 2024 is released). Because of that, they are going to have more issue pop up in testing and in turn, don’t want to rush out a totally failed update. We just need to be patient and keep pointing out the major issues we run into so they are aware of what needs to be fixed.
We just had good news from Microsoft. As we expected, the issue was not caused by us but by an error with the file ingestion path for Xbox. Tomorrow, we should see a new version available for testing.
It is a highly unfortunate issue that is rather damaging for us, but the cause of the issue lies outside our control.
After the last update 0.17 (xbox series x) the problem is still here. I can’t import the flight plan in fcu by import ( I can manually) also the take off calculator isn’t working
