Public beta patch 1.14 rc21 (July 8, 2009)

[enf91]

The title is "RC13", but the link at the bottom of post #1 says "RC12a". Has the link been updated?

[richfed]

Started a new game using this latest RC -- In the full campaign w/KY, I notice 2 regions -there may be more, which appear black: Salter Creek, TX and Lexington, SC. There may be more ...

[mikee64]

The title is "RC13", but the link at the bottom of post #1 says "RC12a". Has the link been updated?

Yes, if you look at the name of the zip file it says RC13 as does the new credit screen after you install.

Started a new game using this latest RC -- In the full campaign w/KY, I notice 2 regions -there may be more, which appear black: Salter Creek, TX and Lexington, SC. There may be more ...

Confirmed. Also add Brazos, TX; Posey, IN & Burlington, IA. All are black in RC13.

[Gray_Lensman]

deleted

[richfed]

This hotfix crashes the game, Gray --- or, mine, at least --- if applied to a saved game begun with 1.14 RC12 and then patched to RC13.

I can start new games without a hitch.

[richfed]

Interesting however, note the region numbers.

0 Rennseleer, NY
256 Lexington, SC
512 Posey, IN
768 Brazos, TX
1024 Burlington, IA

They are all +256 ...

[Gray_Lensman]

deleted

[Big Muddy]

Every patch is a problem latly, maybe Ageod should consider finalizing ACW and BOA2. Then they can focus on their new products, it seems to me at least they have overextended themselves. It's to the point where I don't brother with either anymore, I'm finding this very frustrating, to say the least.

[Rafiki]

Then you should simply stick to the official patches.

It is in the every nature of beta patches that they are not deemed ready for official release yet. Would we have liked to officialize this by now? Indeed. But it should also provide confidence in the process, since without it, some of the issues we have been seeing may have leaked into the official patches, and that would be worse, don't you agree?

In short, if you don't want to freelance as a betatester, with the bonus of getting access to the very latest in fixes and updates, leave the beta patches alone and stick to the official patches

[Gray_Lensman]

deleted

[Franciscus]

(...) Then they can focus on their new products (...)

Well, you see, they (AGEOD) are indeed focused on their new products...

[RELee]

Then you should simply stick to the official patches.

It is in the every nature of beta patches that they are not deemed ready for official release yet. Would we have liked to officialize this by now? Indeed. But it should also provide confidence in the process, since without it, some of the issues we have been seeing may have leaked into the official patches, and that would be worse, don't you agree?

In short, if you don't want to freelance as a betatester, with the bonus of getting access to the very latest in fixes and updates, leave the beta patches along and stick to the official patches

This is why you get the cool avatar, and I'm simply a wrinkled old man.

[Gray_Lensman]

deleted

[Rafiki]

but making complaints about bugs in a Public Beta patch is rather redundant.

However, if the complaint is accompanied by details, a log and perhaps even a savegame exemplifying the problem at hand, it becomes a "bug report", and those are most welcome

[Pocus]

By the way, it is precisely because of the fact that they are focusing on their new products that the recent beta patches have been so problematic. As they make changes to accomodate features in their new development games, some of these changes "bleed" over into the newly compiled "AACW.exe" files.

Due to the way they build their new games on earlier games and keep parts of the game engine (read AACW.exe) compatible with later games, this is a just a byproduct of the process. If they did not do this, there would be no easy backfitting of new game features into the older games such as AACW, NCP, or WIA. This includes interface changes, as well as future battle report enhancements, etc.

You need to make a decision as to whether you want to help participate in the Public Beta process or not, but making complaints about bugs in a Public Beta patch is rather redundant. If it didn't have any bugs, it would be declared an "official" patch.

That's the point, you can't have the butter and the money of the butter (as we say in France).. If parts of the code base was not common to all games, then AACW would never have received ROE buttons or the replay module ...

[Gray_Lensman]

It's possible this release may be very close to "officialization". We'll leave it up for testing for a few days first before having it converted to a full comprehensive "private" beta update patch, which we will have to quickly check for content, before releasing.

5.) Fixed Pillager bug. Pillager units are able to destroy ungarrisoned depots whether in a city or stand-alone.

As with all the other Public Beta Patch releases in this thread, you can apply this patch by itself over a clean install of v1.13b OR over a previous Public Beta patch installation from this thread. It is NOT recommended to install it over a v1.13b that has been QuickFixed.

See the 1st post in this thread for link.

[tagwyn]

Gray: I downloaded the patch on my desktop but will wait until Pocus gives his OK to change 13b. Is that the proper procedure? t

[W.Barksdale]

Has the Stonewall bde been put back in the April 1861 campaign to replace Jackson's bde?

Yes.

[ShovelHead]

... The garrison returned fire, but it was ineffective and the fort surrendered...

This event executed the second turn of a game. No attack was made against the fort. The message for this event states that Fort Sumter surrendered, but the fort remains in Federal control and the artillery unit is still present. Either the message is incorrect or the event shouldn't execute until the Confederates take the fort.

USA_Events - evt_nam_USA_FortSumter1861
CSA_Events - evt_nam_CSA_FortSumter1861

[Gray_Lensman]

deleted

[ShovelHead]

1.) As always, please post a save game.
2.) More information is needed such as which side you were playing? Was it against the AI or PBEM, etc.

I was playing the Confederates against the AI. Occurs the second gameturn everytime. I'll post a saved game if needed.

[enf91]

I downloaded RC14 and the McClellan is still screwy. Here's a save file.

[Gray_Lensman]

deleted

[ShovelHead]

Here's the Sumter surrender event saved game. The Sumter bombarded event is in red in the window.

edit> sorry to here about the virus

[Gray_Lensman]

deleted

[ShovelHead]

I loaded DirectX v9.0c and yet AACW is telling me it still can't find a 3D device. Also, using the ATI Omega Drivers.

Did you get the latest version?

http://msdn.microsoft.com/en-us/directx/aa937788.aspx

[Gray_Lensman]

deleted

[enf91]

April 1861, 07/16 or 08/01/1861, I am Union (which is how I know McClellan is "screwy"), AI, and McClellan is still generically promoted. His special abilities don't change and his starting seniority is "5[1]".

[Gray_Lensman]

deleted

[Gray_Lensman]

deleted