Matrix Games Forums

really appreciate the way you are putting this together. Makes the planning side of the game so much easier to interpret

My sentiments entirely: an absolutely excellent job.

Planning for independence, just in case you lose the vote?[:)]

Thanks guys [:)]
Your comments keep me going [;)]

Slide 13

Slide 14

Slide 15

Fantastic production, Daz. beautiful graphics. The Monschau situation looks good - it's stopping him reinforcing Hofen nth, I think. I can give you some black intel on that siting near Kalter if you like? I wonder what kind of fight you will have for Hofen nth. It all looks like a breeze, so far.

Thanks Peter [:)]

You can have as much input as you like, so long as its not a spoiler [:)]

I have played this scenario before obviously, but am determined not to cheat during an AAR.
If it happens, then it happens, and Ill have to adapt to the changing situation, no reloads, and no peeking [;)]

I'm actually well behind schedule, due to the arrival of the Stuarts, and have lost half a days worth of points at least, and am worried I will not get a decisive victory.
But I am enjoying sharing the battle immensely, even though it is very time consuming.

Slide 16

Happy new year guys [:D]

Slide 17

ORIGINAL: dazkaz15

Happy new year guys [:D]

not quite yet, but since it is new year and Burns and all that:

"''The social, friendly, honest man, Whate'er he be,
'Tis he fulfils great Nature's plan, And none but he.'' "

Interested to see how you are managing the phases of battle. I am just getting to grips with some coherence on the opening day but then it all ends up in an enormous guddle by the start of the second - more like medieval hack and slash but with artillery than a sensible plan

Well its New year now, so Happy new year again [:D]

In the slide I mention about the unit bunkering down when its Assault at time expires, here is the relevant thread discussing it.

tm.asp?m=3313015


Slide 18

If you see any errors in what I have posted with regard to game mechanics please let me know, and Ill fix it ASAP.

This is how the basic Command structure works, as I understand it.
If you want to know more there is plenty about it in the manual, but it takes some digesting to understand it fully.

Slide 19

again, great stuff thank you.

I think one of the hardest lessons for a new player (or at least it is for me) is that is as much a command and control game as a grand tactical combat simulator.

Lots in here to help coming to terms with the options and constraints

Thank you mate [:)]

Slide 20

Oh dear. Definitely in need of the patch, Daz.

Why have we never noticed this before, I wonder?

I don't think its the case of people not noticing it.

I'm sure it is linked to the Axis Can't shoot problem, and has been pointed out by people before, but the effort to report it properly, with proof, screenshots, and saved games is quite considerable for the average casual player.
Many of which I'm sure just think they are doing something wrong themselves to destroy it.

Others might play as a different pace, and at a higher command like Mahatma, where it would probably go un-noticed in the grand scheme of a large fast paced battle.

Getting the balance right of these recon units must be quite difficult to do for Dave, and Panther.

Its a recon unit, so it needs to be quite survivable.
One of the biggest problems with them is they cause the units to fire off so many AT rounds at them, which really effects the supply.
This is because the opposing units can see the recon units, and have TLOS on them.
Maybe if the visibility of the units was reduced, along with the vulnerability, to make them easier to hit once they are seen, it might balance things out a bit?

It's just a suggestion, I know nothing about the code, and imagine it must be far more complex than that.

Maybe a change in the AI behaviour would help as well. where if it is a probe, or a move order, for a recon unit, the unit will defend in situ as soon as it spots the enemy.

If the unit visibility on the battlefield, of the recon units is lowered this will allow them to plot Intel on your map of enemy positions, without being seen, and draining all the opposing sides AT ammunition, or putting themselves in danger.
If you need to attack with them then issuing an attack order will see them close with the enemy. but as their vulnerability is now reduced they will take hits as they should from appropriate AT weapons.

Or maybe a separate recon order, or tick box would be the way to do it.

Anyway I'm rambling on, and there would be a lot of work to do in the code to pull this off, so I expect it will have to wait for the Command Ops 2 or even 3 engine upgrade.

I don't understand how the code can be that difficult. There's a probability of hitting an AC and then there is a probability of penetrating the armour of an AC. Multiply the two together and add what else? Maybe a 'to hit' modifier if moving or an effect for smoke canisters? In Losheim Gap there are 3 x M8s in the NE at the start which are very difficult to destroy.

Slide 21

Slide 22

Slide 23

Slide 24