Patch: When?

[Tim Coakley]

Michael is working on things...I will be reaching out to him when I get back Wed.

Tim

[Wolfe1759]

Tim - thanks for the quick update

Drums on hold [:)]

[sabre1]

Awwww Man, I was just getting into the beat of things.

[Magpius]

rant mode... off

[Max 86]

ORIGINAL: Agent S


rant mode... off

I bet he has an easy time shaving in the morning!

[Tim Coakley]

Progress.

Michael has a build that we think fixes the withdraw bug.

Looking for 3 testers (that can test in next two days) to e-mail me directly at:
tcoakley at optonline dot net


Additionally,
Please post any other bug reports here for a quick check. Michael has fixed two other things and may be able to crush some more this weekend.


Looking for details on the issue with placing bocage in the editor and if you are still getting a screen feeze.

If all is good, I will look to get the patch out next week...earlier if we can.

[sabre1]

Thanks Tim!

[budd]

we need joe in on this testing thing, think he's logged the most play time and seems most familiar with all the bugs.

[PirateJock]

Hi Tim

That's good news. I'll drop you a mail if you're still looking for testers.

Cheers

[Fred98]

ORIGINAL: Tim Coakley

......and if you are still getting a screen feeze.

V1.03
WIN 7 32 bit and WIN 7 64 bit

Both freeze during the direct fire phase:
- in a PBEM replay,
- in the players turn in a PBEM
- in the AI turn in a game against the AI
- in the players turn in a game against the AI

Joe

[sabre1]

Tim, couldn't you just put the beta up for those who want to try it out, with the caveat that it's a beta patch?

If I recall, Empire in Arms did that many times, and Distant Worlds has done that too.

[Tim Coakley]

Sabre,
we will do that for next week but it takes time for Matrix to put that together and the patch is not ready just yet.

I was looking for Joe to do some quick tests but he is traveling. If all looks good with those that can test, I will get things to Matrix on Monday to do a beta...then final release patch two weeks or so after that (gives time for a wider test).

Tim

[sabre1]

Thanks Tim!

[wodin]

Good news, and sort of off topic and going back a few years with regards to Michael I now believe he was telling the truth about Shrapnel and the Airborne game.

[Wolfe1759]

Looks like I will be soon be retiring my new signature.

[sabre1]

I was just getting use to it too. We are going to have to find another cause to blitz. [;)]

[wodin]

ORIGINAL: sabre1

I was just getting use to it too. We are going to have to find another cause to blitz. [;)]

Lock N Load...

[Tim Coakley]

Progress but not there yet. Here is the report:

Had a play around last night with a few games playing both sides, hotseat and against AI. First impression is that the withdraw fix has improved the chance of a withdraw happening and I haven't spotted any problems caused by the change so far - which is good.


However there are occasions where a unit should withdraw, i.e. at disruption 4, but does not because there is no route available that does not pass through an enemy ZoC. At the moment it will just sit there until either one of the enemy units move out of the way so it can escape or the enemy move in and finish it off. Is it possible in this situation, i.e. unit cannot withdraw as trapped by ZoCs, that the unit is either eliminated or at least starts taking some pip damage? I believe that unless a player sees something happen every time a unit should withdraw then they will continue to think that there's a problem with the game.---------------This is a game change. Have to examine the effects-Tim


With the 'Infinite Assault Hex Loop after Reload', fix, it appears to work. I've tried games saved at various stages of the assault phase (with single and multiple assaults) and all seem to progress correctly. In particular, games saved when no more assaults are to happen and showing 'Finished' progressed OK when they were restarted.


----
Change log:
1) Units not withdrawing
Description:
Legal withdrawal hexes were limited to hexes that are further from the enemy than the unit's current hex. This could cause a unit to become 'boxed in' and not withdraw at all.

Resolution:
If a unit cannot withdraw under the above constraints, the check is done again allowing a unit to move to hexes equidistant to the enemy

2) Infinite Assualt Hex Loop after Reload
Description:
If the game is saved after the assault combat is completed but before the phase is ended, the game will not be able to continue upon loading.

Resolution:
Game now displays "End Phase" button instead of "Next Assault Hex" button.

[sabre1]

Thanks for the update Tim, much appreciated. I'm looking forward to testing it out when my pardner (Joe) gets back from Timbuktu.

[Max 86]

Equidistant from the enemy into the terrain requiring the least MPs to enter or into the terrain that provides the best cover? I feel both ways unfortunately. I see a D4 unit as both:

1. a group of guys running for cover ASAP or possibly,

2. a group of guys running any which way as long as they just get the hell out of where they are now!

Thoughts?

Thanks Tim. Sounds good so far.