NickDAL

This is a known and logged issue for Xbox users using v1.2.4

@CaptnHook Thanks for the great intel. Yes, the pink textures issue has been growing in 2024 with iniBuilds. I've been trying to test each update to help iniBuilds' scenery team rid themselves of these old texture pathways as they come out but it seems to be in the way the file is packaged for Marketplace....especially if it contains or uses a file path from a ported textures from MSFS2020...meaning not native to the 2024 SDK. Obviously, I'm limited on how I can test with the Xbox being a closed off system but you can read more about how these older 2020 textures behave in 2024 and are causing problems for iniBuilds here... Cheers, Nick

Hopefully this is where other corrupt shared textures are that affect so many other INI sceneries and developers can go in and piece them apart, especially for Xbox users as we no access to folders and files.

All, this post is largely my ongoing study of how iniBuilds Sceneries interact with the Sim and one another. Specifically, the packages uploaded to the Sim's Marketplace as I am on Xbox X. My original thread on the ongoing pink textures for Xbox users at KDFW is here: Lately, many users, including those on PC, have noticed more and more pink textures appearing in iniBuilds sceneries as the Sim evolves and updates itself but also, and importantly, more and more iniBuilds sceneries come onto the scene and loaded into the Sim. This is a story of how one corrupt scenery package, and, more specifically, using the same texture files over and over again in multiple sceneries without fixing their text pathways, corrupt multiple iniBuilds sceneries over time. For our study we'll look at how updating one scenery, KLAX v1.0.2, which has many user complaints in the forum, can create bugs in other iniSceneries. In our study today we'll look at the effects on KPSP v1.0.0 and KDTW v1.0.5. All are packages streamed from the in-game Marketplace. It's important to note that all three of these iniSceneries are updated ports from MSFS2020, meaning they are not original to the 2024 SDK, simply enhanced and updated for 2024. For every test below, everything was streamed directly from the Microsoft servers and all caches were cleared to ensure old or conflicting data was removed. Let's dive in... First let's look at KLAX's effect when installed and updated piecemeal by the user over time on KPSP...below we see that KLAX v1.0.2's texture files has corrupted ramp equipment at KPSP. Other user report even cars are pink in the parking lots. Now let's watch what happens when KLAX is completely removed from the game and KPSP is allowed to stream on its own...the textures are restored but notice the stairs truck has completely vanished. Now that we've cleared out corrupt files let's re-stream KLAX on the Xbox.....not only has the stairs truck reappeared at KPSP but it has its correct textures applied, no more pink textures at KPSP. OK great, but what about KLAX v1.0.2's effect on other iniSceneries? Let's go to KDTW v.1.0.5 and check for pink corruption. Bingo, there it is, didn't take long to find one. KLAX's runway caution lights have duped over KDTW's texture/object file and not only corrupted it, but now they face the wrong way. Now let's disable KLAX and see what happens at KDTW... Look at that, KDTW's caution lights revert to their original texture/object file used in MSFS2020 and they face the correct way now. So now let's uninstall KDTW and stream both the latest versions of KLAX and KDTW to see the effect on a clean Xbox system... A mixed bag, KLAX has placed its texture and object file for the runway caution lights at KDTW but it still faces the wrong way as in our first example.... Now back to KDFW, a 2024 SDK original scenery that has been missing texture files since release on Xbox...texture files we should note, DO show up in original 2020 sceneries now enhanced for 2024 but still not native to the SDK....KLAX and KJFK. Below we see two pics of one of the two missing texture files at KDFW (see my original KDFW post above) correctly show up at the older two airports. Even with KJFK and KLAX disabled and the cache cleared, it still does not load at KDFW....you can see the pics of this in my other post linked above. That means the script for the textures files submitted for Xbox in a full 2024 SDK made scenery were copy and pasted from older 2020 enhanced versions and do not read the same in the new SDK. The bad code must be located and cleaned up to fix these overlaps and corruption across iniBuild's sceneries with particular attention paid to old texture and object code that predates the 2024 SDK kit and were used in older 2020 ports. I hope this helps out the developers, especially when it comes to Xbox and how packages are loaded to the Marketplace and read but the system. I'll continue to test out all these things as updates and fixes are released over time. Please reach out with questions, thank you so much! --Nick N. cc: @IniJamir @IniSteve

Second this. I have a bluetooth keyboard and mouse connected to my Xbox, otherwise I would be throwing things, ha. --Nick N.

UPDATE: I recreated my flight listed above, KRIC-KSDF, this morning, and sure enough, ATC changed my arrival routing at TOD. However this time I correctly and successfully changed the routing in the FMC. I think what happened last evening that caused the WASM crash was that I accidentally activated the ALTN Airport (KCVG) routing when I was trying to change the arrival STAR into KSDF. When I went into the F-PLN to try and change the STAR after that the WASM Crash occurred because KCVG was now programmed as the arrival airport and I was trying to force a STAR into KSDF and the system didn't know how to read that. Hopefully in the future it will just say NOT ALLOWED instead of completely crashing out on me. Hope this helps! 🙂 --Nick

This has been an issues for Xbox users this year. KDFW has had pink textures since release day, none of the updates pushed out have fixed the issue, something in the way the are packaged for Marketplace then unpacked by the console. Any updated world object updates/paths for texture files added by Microsoft would also corrupt these. Seems to be some kind of double-reading by the sim or a missing line of text in some texture files to match the new paths where the files actually are.

@IniJamir Just checked this on Xbox with the 2024 Marketplace version and this is what I see as well. Latest Microsoft California Update is streaming.

Hey Team, Xbox Series X user....just had my first WASM crash in an iniBuilds aircraft. A300-600R MSFS 2024 Premium v.1.0.7 from Microsoft Marketplace. Freighter variant with UPS livery. KRIC-KSDF, In-game ATC changed my arrival routing into KSDF during flight close to TOD, as I was changing it to the new STAR in the FMC, boom, WASM crash... All contents were being streamed, meaning I did not have the plane installed to the Xbox.

@IniJamir On Xbox X and can confirm this bug for 1.2.4 as well. Logo, landing and Nav lights are all not working. The strobe lights work on the tail but are barely noticeable on the wings. --Nick N.

@IniSteve @IniJamir Hey guys, just reporting back as promised on this bug now that v1.0.3 is now on the Xbox Marketplace. Good news first, the UPS cargo ramp now has all of its missing objects and looks great. Big thanks for getting that corrected. Posted a pic of it just to show how much improved it looks. The bad news is that the missing texture files for the concrete barricades and pylons around the terminals are still corrupted in the PC package uploaded to the Marketplace and needs a code correction to fix it on the Xbox package. As usual, this is tested with a clean install, cleared rolling cache, default KDFW scenery disabled and all other iniBuilds sceneries disabled as well. All other Ini sceneries work great and have no missing textures. Just let me know as things progress, thanks as always! --Nick N.

@IniJamir Haha, fingers crossed. Thanks for the info. I just know the last time @IniSteve tested the Xbox pkg on a PC it also did not show up but did once it was tested on the console itself so that makes me a little nervous. All the other airports work great, even the new Hong Kong loads correctly and looks amazing! Hoping for the best and will check on my Xbox when it drops in the Marketplace. Thanks again for all the great communication! --Nick

@Azlog According to last week's weekly email update, livery packs for Xbox users have been submitted to Microsoft for approval and we are just waiting on them now. Perhaps @IniJamir can confirm that? 🙂

@IniJamir @IniSteve Hey guys, while it will be a week or so before v1.0.2 arrives in the Marketplace for Xbox users, do we know if this update does in fact correct the missing textures for console users? I didn't see a mention in the notes. Thanks for any updates!

@Natewilly928 It's the 2024 Premium addition that's the problem. If you notice, all the liveries advertised with the plane in the Marketplace are not included once you purchase the product and it's added to your collection, only a handful are actually there.