IMHO this is one of the many examples where a fundamental new “issue” of FS2024 shows up:
- delayed or out-of-sequence delivery of assets.
I guess that a lot of other “bugs” are a consequence of this condition, which is a result of the “streaming first” strategy. It is visible that Asobo still needs time to really make streaming as robust as pre-download … or even more robust.
Here is one of many examples that I did see … partially loaded aircraft (traffic):
Now while the above can be filed as “funny” … it is just another testament to the new problem category of unpredictable asset data availability.
I am pretty sure that a lot of WASM code for making objects “work” lacks the proper logic to protect against “using objects” that actually do not exist yet.
While the decision to “got full streaming” was the correct one, it triggered a new category of problems and makes understanding the bugs which we are seeing hard(er). This goose is guessing that partial asset download plays a big role here.