Suddenly the airport tower object that I use for my freeware Brown Field airport (KSDM) scenery is invisible in MSFS2024 SU3 1.5.25.0. The scenery is compiled in MSFS2020, copied to the MSFS2024 community folder and works in MSFS2020. It works this way since the MSFS2024 released. But suddenly the main tower is now invisible. It has been reported by a user of my scenery. I don’t know if it happened with the previous SU3 beta.
Object is the control tower from the stock MSFS Miramar KNKX: Miramar_TowerControl. It’s streamed in MSFS2024.
You are not alone…
Have you cross cross-checked with the “standard” FS24 1.4.20.0 for the same airport ? If not, take a look…
I have the same problem since 1.5.25.0 (possibly 1.5.24.0)
I’m working on a project at LFPG and I had to move a part of a Terminal because it was not correctly positionned, and,a few days ago the object… disappeared. Someone at Asobo tampered with the Library objects and it changed names/GUID. It was surely a very urgent and important necessity obviously, but if the object changes its ID/name then its not recognize anymore by the sim. Simple as that. The good news is that I realized that the objects in the classic (1.4.20.0) version and the beta are not exactly the same anymore. If you roll back to the classic version may be you will find your object with another name/instance.
In the 1.4.20.0 your object is labelled/titled : “Miramar_TowerControl”
I believe that this object is still there but under another name in 1.5.25.0.
I hope it was not done purposedly because I can’t see why…
EDIT : your file is from 1.4.20.0 of course… and so have a look in the beta to see…
Your KNKX Tower in 1.5.25.0 (1.5.26.0 now) doesn’t exist anymore as I suspected. It has been replaced by two objects… KNKX_75 and KNKX_75_Props. The first is the Tower by Itself and the second the furnitures, aerials, technical bazaar etc… that are inside it.
Hey! Thank you for your support and all the debugging!
I suppose I have to manage two .BGL files. The standard one compatible with MSFS2020 and a second one dedicated to MSFS2024 that will include the KNKX_75 and KNKX_75_Props. I will double check this when in front of a MSFS2020 PC.
You did all of my job debugging this stuff
To be prepared for other object re-allocations in other of my sceneries, do we know the rational behind changing the object name from MSFS2020 to MSFS2024 and splitting one object in two ?
Thank you for stepping in @FlyingRaccoon,
Do we know if it’s by-design that this tower object has changed and how to identify other changes like this one ?
Hello @FlyingRaccoon
In version 1.5.25.0 (or..24.0?) the “LFPG_124” object replaced the 1.4.20.0 “CDG_Terminal2_06”. I did not dive inside it to see what the differences are but they look very similar. I had put an exclusion rectangle in my project and then select the 1.4.20.0 object and repositioned it to match the ground markings. and the result in 1.5.26.0 is…
If the object comes from a bespoke airport, it is likely the object will be modified or entirely redone with a new GUID when the airport is reworked.
This would be different if the object was coming from a generic asobo modellib that are intended to be shared and used by everyone.
The issue is the Scenery Editor makes no distinction and lists every objects, allowing scenery developers to create risky dependencies.
I will raise this issue internally.
I fully understand and I personnaly assume the risk of re-using objects from the library (generic Asobo modellib or bespoke airports). As we claim in french “Le beurre et l’argent du Beurre” (can’t have the cake and eat it too).
I’m not sure if the modified/updated/redone bespoke airports are listed with their status, at least in the Beta (didn’t see any reference in changelog).
I beg to differ with the idea of “assume the risk” because it’s not only the developer but also the end-user that would have to cope with it. If we create an add-on for ourselve to enjoy it, then it can be discussed but what about the people who download it?
Moreover there is the fact that some users and likely the vast majority do not even know what a beta version is. I cannot imagine creating two versions, one for the beta and another one for the “normal” one, knowing that in one day, one week, or one month someone somewhere will amend a part of a building of a bespoke airport. Another thing is the end of the beta version one day or the other, replaced by another beta with another library and so on? Shall the Library objects be injected in the classic one? Yes but with a new GUID…too complicate to handle for developers and users I’m afraid. I believe that bespoke airports should not be visible in the library, beta or not. Especially the Asobo ones…
Early this morning I decided to remove the exclusion and reinstate the original object/building in lieu. Very quick to type and read but it took me about two hours to realign the parkings, paths, jetways, markings. Fortunately I had not modified all the terminals…lucky me!
Bien à vous.
: 