Matrix Games Forums

I'm glad to hear that there will be a new patch. The game as-is is great, but it's the commitment to tweaking (and fixing) little things that will make it one for the ages.

BTW I have once again reviewed the orders delay code in an attempt to fix a reported bug in which a force repeatedly replanned and never advanced. Turns out that the delay on the subordinates was too great and the Move task expired before they even started to move. There were two factors at play here. First the code which estimated the likely Move duration was using an older method for calcing orders delay than the current one actually used in order processing. Second, the new orders delay code erroneously was calcing all orders delays as though they were coming from the player. Now this is fine for any force you give an order to but not for their subordinates.

I've fixed these, tweaked some of the modifiers as well and double checked the effects. The upshot now is that the estimates for Move durations are much better as are those for force delay. In repeated tests with different sized forces and varied staff quality the difference between the force delay estimate displayed on a unit's data in the Cmdr tab of the side bar is within 10 to 20 minutes of actual ( on average ). This should make it much easier to estimate how long it will take a force to get moving from the time you give an order.

One other modification I will make is to turn off the arty firebase code when you order the formation type to be "in-situ".

What's the firebase code do?

Thanks.

Firebase code causes indirect-fire assets to check their distance from the objective. If they are in a valid location they will halt and if not, they will select one and move there. You normally see this as artillery units 'dropping off' during a formation road march. Occasionally, on short moves, you will see this as artillery units moving to the objective, then replanning and moving back to a fire support location - this happens when the whole force moves to the objective before the artillery unit does its firebase assessment.

Regards
33

Any ETA on when this will be fixed?

I think it's allready fixed (read the last Arjuna message), and they are testing the last beta build so they can release a quick patch on this.

Maybe I should have been more specific. What is the ETA of when the fix will be released?

When it's ready. If we release a patch without adequate testing then all that will happen is something else will get broken. So the plan is to make sure that patch 2 works in all respects before releasing it. To further assist in this we've also taken on two new beta testers to help put the patch candidate through its paces.

Regards
33

ORIGINAL: Golf33

...If we release a patch without adequate testing then all that will happen is something else will get broken....

Amen to that! [&o] A developer that knows the importance of testing!! I work as a programmer and often, when I'm asked to make a fix or change, I'm given too little time for testing - it quite often gets back to me with something that was missed!

I wish I worked for a company that valued testing!! [:(]

Hiya all, I was just wandering if we could have an update on the patch[:)]

I have noticed this problem also, and would like to express my appreciation for your good work on this game!!!

Get it sorted guys! Yakstock is slaughtering my AT and AA units as I try to take Nijmegen! ........... And I need all the help I can get[8D]

We encountered a CTD ( crash to desktop ) introduced in the latest build. So it will be one more round of testing I'm afraid.

ORIGINAL: Arjuna

We encountered a CTD ( crash to desktop ) introduced in the latest build. So it will be one more round of testing I'm afraid.