Not a trolling comment
What factors determined that the DCS software performed so badly with a frequently changing schedule?
I can appreciate the calculations might be complex when working out optimum balance but we’re talking hundreds of data points, not thousands, or even millions
And once a loadsheet has been created which I imagine contains passenger seating and pallet loading plan - can’t be larger than a few kb? Maybe a meg? Can it? So there should have been no issue sending this to the loaders
And despite the chaos, are we talking about a dozen flights or thousands?
Ok ok ok, I get the 5 minute window / manual entry thing, but otherwise? We’re talking a few thousand data points per plane x a few hundred planes (max) x a few kilobytes, maybe megabytes, per plane. Computationally at least, a 386 could’ve handled that
See title. Not trolling, but as a developer, recently, of load scheduling as it happens, I’m curious as to why and would like to know what I’m missing