SPAACARS v. 7.0 and New Econ Module Is Now Released !

I think we're on the same page here Bill. Yes...all those things you mentioned:

"I guess I think of Economics as income or revenue made by flights whether cargo or passenger flights. Aircraft efficiency, flight & fuel planning along with load revenue whether cargo or pass all make the airlines bottom line which is what I thought that the Eco Mod was all about."

Yes...but when I overhauled the module to help improve standardization the changes in how cost and revenue are calculated make it impractical to mix old econ data with new econ data.

This way pilots all start at the same place. While I could bring back a display with the old data - it just adds confusion I think. I would prefer that pilots just accept the credit given for those flights as logged in their logbook and flight hours, and even hub hours, but realize that future econ flight data displayed now must all be based on the current cost/revenue formula so as to have any meaning for the displayed data.

Again - pilots can fly passengers or cargo or combination of both currently. The major issue right now is that I've limited this to smaller capacity cargo/passenger planes. While you can always fly larger planes - just reduce your payload to the 2014 Lbs. limit set for the current Econ Module - as I did with the B1900 and the DHC-6, it's entirely possible that doing so to the extreme ie. taking a 777 and flying with a payload of 2014 Lbs, will likely have an adverse affect on your profits. Eventually I'll add a separate Econ Flight group for larger aircraft. I'd like to see how this pans out after we've had a chance to test this module with smaller aircraft first. Let's get something working on a smaller scale and then build on it - adding larger aircraft flights. Those would also be tracked separately so that data can be compared relative to similar aircraft characteristics.

John

Hello Bill,

No changes were made to time or flt hour handling. Only payload (cargo capacity) calculation - a bug caused incorrect capacity with subsequent model selection prior to flight. Corrections to that led me to find an error with multiple threads running and attempting to make simultaneous calls to FSUIPC which resulted in error. This error was interpreted as a sim disconnect whereby SPAACARS would chime the disconnect alert and 'reconnect'.

I think I also found and corrected the issue Nick found regarding running subsequent flights without shutting down and restarting SPAACARS. SPAACARS logging buttons and Send buttons should remain disabled after pirep is successfully sent. Earlier version would reactivate the "stop Log" button, perhaps having pilots think they could run multiple flights without shutting down and restarting SPAACARS.

Lastly changes to force pirep sending automatically when Econ mode is set.

John