Anyone care to take over AACalc?

@aequitas:

I am ok with it and don’t see way it should be removed.

The problem will be that if your computer crashes while the box is being displayed, you won’t get the autosave if it’s the last thing done after displaying the end turn panel.

But it seems there is a strong view to maintain the status quo and no concern about that potential problem. Has no effect on me given that I turn it off so there’s no reason to change that aspect.

Ok…  my mistake, reinforcing after the battle is allowed.  Thinking back to the original game where you had to move everything in combat.  Not a bug…  IJN moving navy towards south america and getting stuck due to the canal being closed…  this is a bug with the Hard AI.

@Hepps01:

Remember the calculator is simply calculating the odds of victory or loss based on casualties from weakest to strongest in attack or defense value.  meaning it is removing the weakest units first followed by better ones later.

That’s about what I suspected, thanks!

I guess anything from OS X 10.3 and beyond are ok.  you won’t know until you try.

Thanks Veqryn, I’ll keep that in mind.

Actually, I made some code contributions to TripleA back in the old days.  Basically responded to a post like this and fixed the map rendering so it would work on Macs.  Long time ago though…

Cheers,
Mot

Thanks to two helpful guys, Greg and Aaron, there is now a new version of AACalc with functionality for AA50 and 1942 (or whatever, I’m way out of it.)

Check it out at http://aacalc.nfshost.com/

I saw someone mention earlier about sub hits coming off first.

I believe a DD changes when a Sub fires. With one, a sub fires when everything else does.
So I think a defending sub would fire in surprise strike, but the attacker sub would fire with other units if the defenders have a DD.

Also in the opening fire phase, sub hits could be taken on defending subs that also fire, thus preventing a unit from not getting to fire if you have enough subs to cover the hits.

Sounds like the version you are using is still the “hacked” version that was never part of the sourceforge project.  Therefore, nothing is supported in your version, and nothing will ever be fixed in your version.  The unstable version at triplea.sourceforge.net are at least supported by the tripleA development team, so there may still be bugs with them, but at least any bugs will be fixed in future releases.

I’d recommend running (not walking) to triplea.sourceforge.net and downloading the lastest unstable release 0.9.4.1 (since no stable releases yet have support for PBEM).

Convince your opponent to use the same version - it shouldn’t be hard if they were using the same version you had (that you say doesn’t work any more).