SPAACARS Version 2.3.2 Released

Pilots:

The latest version of SPAACARS is available for download. As usual - just get the latest zip file, unzip it and then copy the folder contents over the old SPAACARS files you are currently running. Successful install should say Version 2.3.2 in the 'about' area in menu, and the Manual will also show latest version number.

V 2.3.2
 Catches ‘Position Update’ errors if server problems prevent connection during periodic position updates during flight. Will be reported in SPAACARS log as Pos Update Error.


Note: An earlier version already deals with similar problem when sending log at end of flight - allowing multiple tries if server misbehaves.

These changes should mitigate pilot frustration by avoiding SPAACARS crashing due to server problems outside of my control.

John

Stop crash landing.

Thanks for giving it another test drive Yoland, and I'm pleased that we might have traced the last error to server related issues - although in the greater scheme it would probably be less impact if just my program.

Yes - I'd hold off on P3d testing until I take time to further test and fix known issues.

...and Steve, just kidding about the landing rates. I'll check again that code to see if I can account for unreasonable variances in landing rate calculations. Fortunately that problem causes no disruption in normal flight ACARS uploads at this point - until we do something with that number.

Haven't done anything on it yet Steve...busy housebreaking a puppy and trying to keep peace between the resident dog and the new pup.

I did research the issue, and noted some options that might help - the most significant is to read a different memory location that takes the descent rate of the plane rather than the one that reads the gauge - which often lags as we know. Surprisingly the gauge reading was suggested by Peter Dowson - the FSUIPC guru, although I wasn't aware it was a gauge reading. That shouldn't account for some real crazy readings you had though. I'm also looking at my calculations and the variables - but this plays out like that duplicate global/local variable issue we saw with flight time. I've not had a chance to recode yet and may not till after holidays.

John

William,

The PAX/Cargo option is based on the Total Payload of your aircraft at the time you initialize (start) the SPAACARS program. You must adjust your Payload settings in FSX before starting SPAACARS, or restart SPAACARS if you make changes to your payload in FSX.

To get PAX/Cargo to meet the capacity of your plane, you must load your plane to the full payload capacity in FSX before starting SPAACARS. SPAACARS will then recognize the full capacity of your plane.

This ensures that SPAACARS will not allow greater values than what your plane is currently configured for.

Note: I'm releasing a new version today that corrects an error in calculating that could result in a negative cargo weight.

Let me know if you have further questions or problems.


John