April 27, 2023 Development Update Blog Discussion

If you feel that way but I’m not the one repeating the limitations of using an Xbox. :grin:

1 Like

I cannot get IniBuilds KJFK to work on my Series X. I have tried taking off from there, instant CTD. I have tried taking off from KISP (further east on Long Island) and flying an approach in, landed but then CTD when taxing to my gate. Tried one more, where I took off from Newark and tried an approach, same thing…landed, crash on taxi.

All my “tests” were done using the default 787-10. So for now, anyone on the fence, do not buy IniBuilds KJFK until they release an update, which hopefully fixes the issue!

For those of you that have it, if you are somehow getting it to work completely…please let me know how, haha…not that we can do a lot of diagnostics on the Xbox version.

2 Likes

There is no communication of this sort between Asobo and 3rd party developers.

There are tools, however in the Scenery Editor and documented in the SDK for dealing with it.

It all depends on how Inibuilds created the airport, they should have selected to delete the airport in the scenery editor (or however they develop their airports). If they forgot that “Delete Airport” and all the other associated delete choices, then there will be issues. It’s also true that it’s possible those functions don’t work properly. This has been an issue in the past. At which point, it’s out of Inibuilds hands and hopefully they’ve submitted a bug report to the SDK team at Asobo.

And then there’s the way that MSFS deals with textures is not bug free either. At one point there was a bug that put all textures together, ignoring the VFS (Virtual File System) rules of replacement and other rules that are supposed to be in effect to avoid issues like this. I believe this was fixed, but maybe not totally, and perhaps another VFS consequence is biting us in this case.

1 Like

I very much doubt they will at this stage…

Hi Kevin, when do you think Asobo is going to restore LOD?

I don’t think they will…

1 Like

Even if we set aside the tired and false trope about consoles not being fit for flight sim, this specific issue l has nothing to do with Xbox as a console. Being able to uninstall certain packages is certainly doable, but has not been implemented yet. This is likely just due to prioritization of other projects.

1 Like

When will we see a fix for the lights on the Honeycomb Bravo Throttle Quadrant XPC (for Xbox)? Honeycomb has said that it might be in SU13 or SU14, but I never see it mentioned on roadmaps. It’s very difficult to use the AP when you don’t get feedback to indicate that a button press has been seen by the software. Warning lights for landing gear and various engine faults are also dependent on getting this fixed. My Bravo was ordered around Christmas 2021, delivered September 2022 and is still only semi-functional as we enter May 2023.

If purchased for Xbox, the answer is probably yes. There is a bug report from someone who previously owned TNCM and now can’t use it because of the existing Microsoft TNCM that’s uninstallable on Xbox:

And there is a Wishlist topic to be able to remove default content on Xbox:

CC: @ArchBlizzard278

Here’s another two Wishlist topics for you (no endorsement of the title!):

1 Like

:rofl:

Thanks!!

3 Likes

Hallelujah, we can finally learn how many weeks or months more we have to wait for the absurdly too-intrusive connection lost message – something that should have been about 15 minutes work for someone to disable – will finally be fixed.

It’s the tiniest of tiny bits of progress, but it’s progress at least.

This week needs a fix for the ridiculous ugly engine vortex behind the 4simmers A320 liveries.

Also why have the updates to the Bijan Season Packs never dropped?

1 Like

Finally, from the Twitch stream they’ve announced AAU2 will be out next month, so only ~two more months to get a fix for this utterly infuriating, trivially easy-to-fix problem. It really, really shouldn’t take this long to fix tiny-in-complexity but major-in-terms-of-user-impact issues and I’d like to see that corrected going forwards – this frequently happens to me 4-6+ times per flight – but at least we know how much longer we have to wait now.