Interesting Question #1: Number crunching?

[MarkShot]

When you play HTTR (since COTA is not out yet), do you spend a lot of time crunching numbers or do you just go by "the seat of your pants"? Some examples of what I am talking about:

(1) Do you try compute distances, movement rates, bounds, ... to determine travel times of forces?

(2) Do you try to calculate the order delays down through a force working down from the senior HQ to the line units?

(3) Do you review the various fire power values displayed in the side bar to determine what force you will need for a successful attack?

PS: This topic just came up in the beta forums and I thought it's an interesting question.

Thanks.

[MarkShot]

A quiet bunch today.

[wodin]

Hmmmmm............


CHARGE!!;)

Just kidding.

I do number 3 but not really 1 and 2.

[sterckxe]

ORIGINAL: MarkShot
A quiet bunch today.

They're just not telling you their combat tactics in case you'll use that against them [:D]

ORIGINAL: MarkShot
1) Do you try compute distances, movement rates, bounds, ... to determine travel times of forces?

Nope, but I always play with the 1km grid on so I've got some idea of what to expect.

ORIGINAL: MarkShot
(2) Do you try to calculate the order delays down through a force working down from the senior HQ to the line units?

Nope, again guestimating it - too much things will disrupt your plan anyway so I try to be flexible and not have a single mishap ruin a perfectly calculated plan.

ORIGINAL: MarkShot
(3) Do you review the various fire power values displayed in the side bar to determine what force you will need for a successful attack?

Yes, ultimately that's what needed to make a successfull attack. Though I prefer to out-maneuver an enemy out of a certain location I want - i.e. not always attacking the vp locations but making sure the vp location becomes untenable for the enemy.

Greetz,

Eddy Sterckx

[tukker]

I never crunch numbers during play. I do use the grid to estimate distances, and look at the Force Delay so I can estimate how long it will take for an order to be executed. I don't really use the fire power values either- I just look at the kind of unit I have, its size and its equipment, and, again, estimate how useful it will be against the opponent I'm expecting.
In short, I go 'by the seat of my pants'. I don't think I'd enjoy playing with a calculator next to my keyboard- though it might make me a better player[;)]

Pieter

[simovitch]

I'm new to the game and the forum, but having years of boardgaming experience HTTR was pretty intuitive, and the game engine is just right for the operational level.

That said, I do not number crunch anything when I execute commands. I just review the status of the troops that I issue orders to, and execute. This provides a much more enjoyable experience (for me.)

I have only played against the AI, and perhaps I would crunch a little more in tournement FTF setting? maybe.

Anyway, Great game! Been playing CMBB/CMAK exclusively for 3 years now (!) and HTTR is steadily pulling me away. Looking forward to COTA and especially BFTB![8D]

[MarkShot]

First post, ha?! Nice to see you joining the community.

I also play CMBB/CMAK (CMAK these days as I have finished off a lot below medium SP battles already for CMBB). CMBB/CMAK helps to visualize what it looks like when I have a company in HTTR/COTA advancing. It gives me some context beyond a few counters and some terrain textures.

[simovitch]

yeah, I've actually caught myself for an instant trying to zoom in to CM level while playing HTTR!

I wonder how many years away we are from that sort of medium...

[MarkShot]

A while back, Bil Hardenberger (fellow beta-tester), I believe, was trying to organize a campaign to be played with HTTR at the operational level and resolved with CM at the tactical level. I don't know whatever happened with that.

Bil?

[Trigger Happy]

Nah, Airborne Assault is all about going with the flow.

[JeF]

Mark,

To answer to your questions : No, no and no.

I usually play with the 1km grid to evaluate distances.
I never calculate orders delay. Sometimes I have a look at the estimate to have a rough order of magnitude (is it 2 hours or 20 minutes?).
And as FP, I only use the strength factor displayed on the counter. I don't look so closely at all those numbers on the side. I'm glad with any graphical representation : easier to get a rough info at a glance.

I usually play fast, without too much thinking. Just basic planning at start. I loose a lot but have a lot of fun. [:D]

Take care,

JeF.

[Real and Simulated Wars]

1) eyeballing
2) eyeballing
3) eyeballing
Not a big fan of the methodical battle.

[MarkShot]

I suppose anyone who has read my guides knows that I don't number crunch, but I was curious to know if anyone does, since much of the data you need for it is available via the UI in the game or Scenmaker.

[Real and Simulated Wars]

Hiya Mark!
I'm a big fan of your guides and I read and re-read them from head to bottom. I just don't agree with your method of timetables. Now, for some strange reason I can't command better than you. [;)]

[MarkShot]

It is important to realize in the two detailed AARs which I have done that they don't represent how I approach every battle. I am much more pragmatic than most think from reading that stuff. Of course, first one must be methodical and disciplined in their approach. From there one can find the freedom to be flexible based on the situation.

Lastly, a little bit of luck never hurts!

[Conflux]

I've only had HTTR for a bit more than a month so still learning (real time, no hexes etc - but think this is a great new experience for me - old board w/gamer etc!) so:
(1) intuitively, the splendid maps, 1k grids and type of unit allow this for me w/out the crunching
(2) yes - I'm worling thro the scenarios in order and in the Eindhoven hist campaign 2nd night I had 327 GIR NW of Best and 15/19 Hussars and 1/506 PIR to SE of Best bridges. I used the order delays to attempt to coordinate the attacks S and N for dawn of the 3rd, and importantly, to stagger the movt of the bns of 327 so they wouldn't bunch up and cross their lines of march/attack. Didn't work too well for me as most of them decided that a couple of hours after breakfast was a better time for them to go to work rather than first light! Those that did tho had a bit of work on their hands, but I did manage to avoid the 327th bunching up. I would use the order delays as a rough guide to timings (hour or so) rather than trying to time things to the nearest 1/2 hour
(3) vaguely - sometmes I use the mouse to select the enemy units in the attack area to give me a rough idea of the force strength and sometimes similar for freindly forces, but usually for the latter its intuitive

What I think is so good about this game is that it allows this level of detail - if you wish it i.e staff officer (what about some op orders to start AARs? - wish I hadn't said that) or get on with being the general.

rgds

[Oleg Mastruko]

My answers are "no" to all three questions.

[Mr.Frag]

(1) Do you try compute distances, movement rates, bounds, ... to determine travel times of forces?

No, I just curse and moan when they are late ... they'll catch up to the guys who got there early and are now retreating soon enough. [:(]

(2) Do you try to calculate the order delays down through a force working down from the senior HQ to the line units?

Are you insane? I must have left my battle staff at the store. [X(]

(3) Do you review the various fire power values displayed in the side bar to determine what force you will need for a successful attack?

No, but learning that support units had to stop and be deployed to actually use their firepower was probably the biggest thing I missed for quite some time. The biggest point I got from the HTTR strategy guide. [8D]

Ray

[Agema]

1 & 2)

I see as being essentially connected.

Naturally I'll pay a bit of attention, but my calculations depend on how much it matters. If I want to get into position during the night for an early-day assault, I'll be checking quite closely. If I want to set up a defensive line and I've got a day to do it, I'm not going to bother.

As a general rule, I might think in terms of co-ordination rather than exact timing. It'd be about wanting units X and Y to arrive at the same time, or one to get there first and maybe supply cover whilst the other moves in etc, rather than whether it occurs at 10am or 3pm.

3)

No. Info on the enemy is usually too imprecise to really know what they've got there to make much detail worthwhile. What I'd generally do is recon, and make an approximate judgement based on the unit types attacking/defending as to how much I'd need. No point sending paras out to assault armoured vehicles unless you've got *really* crushing superiority in numbers.