# Again issues with database

**URL:** <https://forum.navigraph.com/t/again-issues-with-database/18742>\
**Category:** General MSFS Data\
**Created:** [February 20, 2025, 12:16pm UTC](https://forum.navigraph.com/t/again-issues-with-database/18742 "2025-02-20T12:16:18Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![NAVData](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.navigraph.com/navdata/32/30549_2.png) [@NAVData](https://forum.navigraph.com/u/NAVData)\
**Post date:** [February 20, 2025, 1:31pm UTC](https://forum.navigraph.com/t/again-issues-with-database/18742/7 "2025-02-20T13:31:07Z")

</div>

The problem here is that ASOBO/MS has changed its loading priority rules, and it seems that third-party scenery doesn´t follow these new rules now. I assume it´s only a kind of “transition phase” and that all scenery designers are following these rules (link see above in my posting).

In the meantime, we have only two possibilities - to follow the official rules (what we have decided now due to the navdata development) or to rename the packages. Both “solutions” are currently not optimal, but we had to decide on one of them.

Sorry, Matteo, for the additional effort at the moment, but again, it was not our idea to change a working logic 😉

Cheers,  
Richard

---

_[View the full topic](https://forum.navigraph.com/t/again-issues-with-database/18742)._
