---> AACW Patch 1.10b release

[Brochgale]

We saw weather anomalies like that when testing the 1.10 beta, but supposedly they were resolved.

I never used or even installed the 1.10 beta. Only the official release of 1.10 and 1.10a patches.

[Gray_Lensman]

deleted

[Pocus]

1.10b out


[1.10b]
- Modding: You can now tweak a new variable, bmbrange, in Blockades.opt. This is the range needed by guns to fire on passing ships.
- Minor rail rework by Gray_Lensman
- Numbers of horses and guns were not valid for the Mexican - fix courtesy of Gray_Lensman
- AI: Added a new experimental algorithm: 'Repair Rail Network'. Please report if needed.
- AI: Improved: the 'Force In Being' algorithm has been improved. The AI will now consider better if remaining in place is not the best 'move'.

[Franciscus]

1.10b out
(...)
- AI: Added a new experimental algorithm: 'Repair Rail Network'. Please report if needed.
- AI: Improved: the 'Force In Being' algorithm has been improved. The AI will now consider better if remaining in place is not the best 'move'.

I do not cease to be amazed of your continuing dedication in improving AACW AI. Thank you !

[Pocus]

At the risk of auto-disparaging myself, the first algorithm is done because VGN will need it, and the second is a must be in all games

[Pocus]

If you downloaded the patch before seeing this message, please download it again an reapply it.

[type7]

I just got in a quick Shiloh scenario as Union with patch 1.10b and that has to be my best experience with AACW yet. I think it was all due to

AI: Improved: the 'Force In Being' algorithm has been improved. The AI will now consider better if remaining in place is not the best 'move'.

The scenario felt more realistic in that the AI wasn't racing all over the map. This has me excited about AACW again Or am I imagining things and this is not what this improvement does?

[berto]

[1.10b]...
- AI: Improved: the 'Force In Being' algorithm has been improved. The AI will now consider better if remaining in place is not the best 'move'.

YES!! Thank you, thank you!!

[Turbo823]

ouet:

Nous demandons à tous ceux qui le peuvent de bien!
Au secours ! Je n'arrive pas à bouger !
(Sorry thats all the French I know)

I am getting an error right after the Late April 1861 turn after installing the 1.10b. The files says 1.10b but the splash screen says 1.10a.

I've reinstalled twice!

[ATTACH]2793[/ATTACH]
[ATTACH]2794[/ATTACH]

[Crimguy]

Did you read the message about re-downloading the patch? Sounds like he released a buggy one by accident . . .

[Gray_Lensman]

deleted

[Rafiki]

As Crimguy stated be sure you have re-downloaded the patch first. Second, as I always stress... Uninstall the game, delete the current game folder completely, then reinstall the game and patch directly to the new patch. If you haven't done this, it is rather useless to site problems with the current patch as it may result from residual files that were left over from the previous installation, something the update patches cannot account for, though they are comprehensive by design for installation over the original v1.00 Setup version.

Though the above may be warranted at times, I think it doesn't hurt to install the patch directly onto an installed game; that's how it's supposed to work, after all.

However, if a problem occurs, Gray suggestion is the way to go, though if it turns out to be a problem with tha patch itself, we're still interested in hearing of it!

[Gray_Lensman]

deleted

[Gray_Lensman]

deleted

[Rafiki]

Fair enough gray; we shall agree to disagree

[Pocus]

Pocus:

As posted previously regarding "Redundant Image Errors"...They are still present in v1.10b when using "Error Logging"

Ok, I have changed the error level message. I think it is the old logo that I forgot to remove with the patch. Can you list them?

[GShock]

I've solved all problems with file using multiple installations of the game.

1) Default 1.0

2) Current patch (uninstall -> delete -> copy 1) onto 2) -> apply patch)

3) Struggle for Vast Future

[Turbo823]

After doing a defrag, I reinstalled the game on a different HD and reinstalled the patch -- works great. Thanks for the suggestions.

Back to the battle!

[Gray_Lensman]

deleted

[Pocus]

Sorry, I meant in the unreleased version

Thanks for the filenames!

[Gray_Lensman]

deleted

[Crimguy]

Never noticed that. Agree with your thoughts though. I rarely click on the Nato symbols on the right box. I find myself moving through them by clicking on the Nato symbol on the container pic on the bottom.

[bigus]

I'm getting a critical error in the Coming Fury scenario. On turn one.

[ATTACH]2820[/ATTACH]

and the log file.

[ATTACH]2821[/ATTACH]

Edit: Tried to reproduce the error from a saved file but it seems to play out o.k from the saved file....

bigus

[Gray_Lensman]

deleted

[bigus]

Is this totally "vanilla"? Or are you playing a non-vanilla or saved game?

I assume that was directed at me Gray?
Yes it was vanilla. I loaded the saved game to see if I would get the error again but did'nt on the saved game. I tried to re-create and only got the error once more. The error comes when I double click on the info section to see the reinforcements in Jefferson KY. Seems to be when buying Kentucky militia but have'nt been able to test further.

Edit: here's the saved game for what its worth. Like I said I don't get the error from the saved file.
Let me test this further...I just upgraded to a new quad core yesterday.
It might be the new computer but I doubt it.

[ATTACH]2823[/ATTACH]

bigus

[Gray_Lensman]

deleted

[arsan]

Bigus

The critical error happens because the reinforcement screen you open is empty and when you try to click on the arrow it crashes??
It has happened to me before in two different patches (1.09 versions i think) and with different reinforcement's.
As you say, if you restart usually is not reproducible.
I reported this and was told a non reproducible interface crash was a hell to fix. It could be anything Luckily it has not happened to me lately
Regards

[Pocus]

Be warned that the format in which the reinforcement list is stored changed between 1.10 and 1.10b, so a crash would be no surprise if you watched a list of reinforcements from 1.10 or below with the new patch.

if you crash each time you open the window AND it was generated in 1.10b, then tell me.

[Gray_Lensman]

deleted

[bk6583]

Hi Pocus,

I started an 1861 campaign (March) as the Union (started with your latest1.10b). Once again, late June 1861, and you'll see Johnston heading to Pittsburg and Polk heading for Springfield - seems to be the same problem, although I'm not sure since I've been reading from other posts that the CSA seemed to be staying put more smartly.

Regards,

Bob