Slitherine

quote:

ORIGINAL: Capn Darwin

I will note the typos and update the PDF documents and we can post updates down the road. I'm an engineer by trade, so if more than 50% of the words are spelled right I consider it a miracle.

quote:


These are base delays and will vary based on training level of the forces,
readiness of the forces and command and control losses.

quote:

ORIGINAL: Bletchley_Geek

Just finished playing the Tutorial as the Soviets over lunch (after going through it with the British). I really like the Command & Control aspect that gets FP beyond being a mere exercise in causing attrition, and the way variable length simulatenous turns really works well at simulating real-time. Probably this is the most realistic and playable hex-based wargame I have ever come across.

Just two question and a little request.

The request would be to get some form of explicit notification when units orders execution gets aborted or delayed beyond the ETA (maybe that appeared on the log, but if it did, I missed that). I had one Motorized Rifle Coy sitting down for almost two hours after the deadline to start its assault expired and until the scenario finished I didn't understand that the Assault wasn't getting started because there were enemy units between the forming up position and the objective.
I don't believe that there is a direct notification if a unit's orders get aborted or delayed beyond what is normal. Sounds like a good idea and something we can look at. I don't think units between the assaulting force and its objective would cause a delay for an assault order. Assault orders have the longest delay since there is usually extra planning and preparation on the part of the unit. I would suspect its moral or readiness was low or it was too far from its HQ to be the problem causing the delay. We will keep an eye on this to make sure that the delays are reasonable. Don't be hesitant to point out when you think their not.
The questions are about orders delay and the length of the command cycle.

In the manual it reads that

quote:


These are base delays and will vary based on training level of the forces,
readiness of the forces and command and control losses.

What are "command and control losses"? Does it refer to losses in HQ subunits?
I will let Capn D correct me since he wrote the manual, but command and control losses to may thinking would normally refer to HQ units themselves. But yes, loses of subunits both in HQs and in line units can affect the length of your command cycle.
Regarding the Command Cycle length, I am at a loss at understanding how to affect it. During my playthrough as the British, I always kept my cycle length under 20 minutes (and by the end of the scenario, it was of about 10 minutes). As the Soviets, I started with a quite lengthy 25 minutes cycle, which improved as the game continued. I always kept my units within command radius, and tried to keep my HQ's out of harms way (and moving them from time to time, just in case).
I think it is easier to control your command cycle in smaller scenarios. There are many variable that can affect your command cycle: The level of EW jamming; force readiness--as units become scattered, disorganized, as their readiness and morale falls can all affect it; the structure of your command and control units (i.e. HQs) and their locations and status can impact it. These are just some of the factors in the equation. As scenarios get larger, it gets harder to control these variables. Oh, enemy arty is always hunting for your HQs, so even tho moving them can impact your command cycles, sometimes you have not choice in order to protect them.
Since I've been doing basically the same as either side, I wonder if the length of the cycle is affected by 1) how many orders are being currently planned and/or executed or 2) the number of units in the force. For obvious reasons, both 1) and 2) tended to go down as the scenario progressed :)
Yep, these factors impact the command cycle too.
Great game, thank you very much

quote:

ORIGINAL: cbelva
I don't believe that there is a direct notification if a unit's orders get aborted or delayed beyond what is normal. Sounds like a good idea and something we can look at. I don't think units between the assaulting force and its objective would cause a delay for an assault order. Assault orders have the longest delay since there is usually extra planning and preparation on the part of the unit. I would suspect its moral or readiness was low or it was too far from its HQ to be the problem causing the delay. We will keep an eye on this to make sure that the delays are reasonable. Don't be hesitant to point out when you think their not.

quote:

ORIGINAL: Bletchley_Geek

Regarding the Command Cycle length, I am at a loss at understanding how to affect it. During my playthrough as the British, I always kept my cycle length under 20 minutes (and by the end of the scenario, it was of about 10 minutes). As the Soviets, I started with a quite lengthy 25 minutes cycle, which improved as the game continued. I always kept my units within command radius, and tried to keep my HQ's out of harms way (and moving them from time to time, just in case).

quote:

ORIGINAL: Russian Heel

My first impression was joy at the decision to not be cool and use Я instead of R in the box and title screen art, then a bit of head scratching at the use of modern Russian insignia as the Soviet player's stock avatar choices, and then pleasure at the challenging and rewarding game play I had in the first scenario I played.

quote:

ORIGINAL: jnpoint

So far I'm too impressed by the AI.
I hope the tutorial scenario isn't easy, because I have serious problems :) Maybe I'm not that good at operational/tactical warfare.

quote:

ORIGINAL: freightweezul

I would like very much if the contour LINES were marked but I suspect that would be a large programming/graphics change. As is the contrast between different elevations is color only and not very great. I'm not color blind but I still do some squinting even on a large 2048x1152 monitor.

-james gerbino