Welcome to
Microsoft Flight Simulator’s SDK Q&A Platform!
OK. I get it. Parking, taxi links, hold-shorts, and runway links all need to be connected together for AI to be able to use them. However, there are many cases where this simply does not need to be done. Small GA airports that will likely never see any AI traffic, fictional airports, helipads, etc.
Whereas these special use cases can certainly accommodate the new changes, it doesn't make since at all to be forced to.
I would like to suggest that instead of treating disconnected parking spots as an error, you treat them as a passable warning and let the addon developer decide if they want them linked or not. Just as it has been since the beginning.
The major downside to the current error method, whether it was intentional or not, it prevents you from saving your project until you fix all of the errors present in the package. For larger projects that can take hours to resolve, this can be a major issue, as one crash can set you back hours of work.
There are already two threads here talking about these complications, just to further drive my point home that this needs to be resolved:
https://devsupport.flightsimulator.com/questions/3928/sdk-error-invalid-child-when-saving.html
