Matrix Games

• 1.) Dismount Infantry/equipment feature to
  
• 2.) a) allow Motorized Inf or Gun units to access rough terrain and woods, and
  
  b) allow medium tanks to plow through light woods. The Germans used to set up defensive perimeters with StuG IIIs near my grandfathers village (in 1945), an area with DENSE/heavy woods in fact, in the "Bergisches Land", a hilly area east of Cologne (around 80km from Cologne) ... and the tanks didn't fly there. Tanks can access woods, IF the terrain isn't muddy or sticky (so that the tanks sink in.) Only one of those StuGs got stuck, but was still able to keep the US units from crossing the local main river (the minor River "Wisser" I think) for days, as it was sitting on a little hill packed with woods, where the US units could not make out the exact position, let alone reach it (from across the river), until it ran out of ammo.
  The progress in that area allowed the Allies to move to the Ruhrgebiet and surround the Germans in the "Ruhrkessel" (Ruhr-pocket), trapping some 300,000 Germans in the process.
  
  
• 3.) Minefields.
  
• 4.) Allow amphibious forces (or tanks with wade equipment) to cross rivers (eg. German tanks crossing rivers in Russia) or to land from off-shore locations/vessels (Normandy landings).
  
• 5.) Off-map artillery.
  
• 6.) Dedicated Reserve pool and class that allows ...
  a) for automatic commitment of reserves (AI)
  b) for automatic or manual allocation of replacements to battered units
  c) the engine to divide units on the fly:
  
  means 1) to send out (say platoon sized) combat patrols and 2) to allow building of Kampfgruppen (eg. consisting of returning stragglers or of ad-hoc formations the PLAYER creates)
  
  
• 7.) Aircraft combat patrols (render tactical bombers/fighters screening and patroling battle fields) (necessary for Normandy theater). Rendering them would enable the player to re-direct troops and equipment to safer routes.
  
• 8.) Render nightfighter capabilities.
  
• 9.) Render off-shore artillery (ships: from destroyers up to battleships).
  
• 10.) Allow nations with dedicated tank retrievers to retrieve and repair tanks during the operation (With Germany having the highest retrieval/recover rate, eg. like in North Africa, where they retrieved and repaired 7 of 10 knocked out tanks, sometimes 9 of 10).
  
• 11.) Campaign mode (that considers and takes over previous progress/achievements/losses)
  
• 12.) At least sort scenarios (by date) so that players are able to see some sort of a timeline, so they can at least play the scenarios in a particular historical correct order. (I suggested that but Dave insisted on keeping "weird" scenario names, although I suggested a good format a while ago). Players have asked for this during the last few days.
  
• 13.) Introduce the general map I created a while ago, which shows ALL mission areas and their titles - with dates and duration.

• 14.) Introduce "flexible order delay", to simulate local decision-making processes where a superior's decision (or opinion) is not needed, eg. for detached units and where this function then allows the player say to detach a company and let it proceed to move with the rest of the division, without the COY or the DIV having to reorg' and redo plans. Say the player would then just let the particular Coy take the next exit on a given highway, and let them leave the Division's route and proceed with their secret order/plans , then there should not be ANY delay, as the Coy was given the freedom to act independently .. That would be my take on a "local" flexible order delay.
  
  Other examples would be occasions where a Coy commander decides to immediately pull out his platoon or his Coy, in order to save resources (men).
  
  
• 15.) Introduce a dedicated Retreat button/function (which should work like a move order) that automatically switches to lowest aggro settings and that OVERRIDES the order delay (either completely or partially), so that the player can pull out troops that are endangered to retreat (means the uncontrollable forced retreat), or endangered to be cut off/surrounded, in time.
  
  
• 16.) Introduce a STOP button/function that makes a detached company stop RIGHT AWAY. Quite some players are misusing the fire-command currently to make their troops stop immediately.
  
  
• 17.) Introduce a "General leads from the front (line)" function, maybe according to historical facts/events, where a General (divisional commander) can LEAVE the HQ (after he issued orders) and JOIN one of the spearheads of his units. Example, a division moving in column formation:
  
  This function would ensure that the LEADING unit would stop (and take cover if they get under fire) and react to the enemy fire, but where the rest of the division (say the bulk of the middle section and the rear of the column) would slow down immediately and halt eventually, IF the leading general accompanies one of the spearheading units (like Rommel did in France) - reducing the order delay by a vital amount.
  Such a function could also be used to boost morale or combat effectiveness, since the General would be with their spearheads.
  
  Actually, the German officers corps (involving ranks from Cpt to General) had a very high casualty rate. This was caused by a common belief that an officer had to lead by example (and show dedication/bravery) to motivate the troops, plus the officer could get a first-hand impression on terrain layout and difficulties or advantages for a certain approach. Some officers did not do that, but the majority of German officer corps was more exposed to enemy fire than some of their subordinates had wished for, I'd say.
  Another example: If US officers would have inspected the Kall-trail in Hürtgenwald, they would not have picked it as main supply route, and maybe the whole operation wouldn't have carried out in the first place.
  
  Rommel's "Vorne-Führung" in France is a vital example of such type of leadership on the General level. There was a saying back then: "Wo Rommel ist, ist vorn" (which means that you can indicate the front or the head of a column by checking where Rommel is. Rommel's own quote "Geführt wird vorne" (which translates to: the leader should lead his unit from the head position) was exemplary as well.

quote:

ORIGINAL: Llyranor

Online co-op! As great as the games are as 1v1 games, I'd find them exponentially more enjoyable if co-op was also an option.

quote:

ORIGINAL: GoodGuy

Sure.

http://www.matrixgames.com/forums/tm.asp?m=2124857


While you're at it, you might also want to review my suggestion regarding the naming (-format + date) of missions, in the same thread, post number 7.

quote:

2. smoke

quote:

I am not interested in playing scenarios, for the express reason that you are locked into historical mistakes.

Case in point in Bulge simulations:

The SS Panzer corps is deployed to attack thru the worst possible terrain against a full strength enemy.
It takes no imagination to postulate the likely outcome.

Now...imagine the same units deployed at the Monschua Gap. (forgive my spelling)

OR....

Bastogne would be unlikely to hold against two SS panzer corp.

Just simple examples

quote:

ORIGINAL: OlegHasky

quote:

I am not interested in playing scenarios, for the express reason that you are locked into historical mistakes.

Case in point in Bulge simulations:

The SS Panzer corps is deployed to attack thru the worst possible terrain against a full strength enemy.
It takes no imagination to postulate the likely outcome.

Now...imagine the same units deployed at the Monschua Gap. (forgive my spelling)

OR....

Bastogne would be unlikely to hold against two SS panzer corp.

Just simple examples

Thats a good time to point "manual unit placement" option. Wich seem that could be the blessing fpor ...series like "Decisives Battles of WW2".
As BFTB/COTA/HTTR operates on a smaller scale. We know its impossible.

You can always check Yorself how much You can pull out from the "mistake"

quote:

ORIGINAL: Mac

One small feature that came into my mind while watching and playing the tutorial is this. Coordinating the units would be much easier if you showed the times at the various waypoints for the selected unit(s). Say I click a commanding unit, I see what the commander has planned for the route, but why not also put the time at the waypoint on the map at the same time? Then I wouldn't have to click on the individual waypoint to check when he will get there. I also like to select my commanding unit, then shift-down to see all the subordinates and how the commander has planned to use them. In this case I would expect to see the time on target for each.

quote:

ORIGINAL: OlegHasky

quote:

I am not interested in playing scenarios, for the express reason that you are locked into historical mistakes.

Case in point in Bulge simulations:

The SS Panzer corps is deployed to attack thru the worst possible terrain against a full strength enemy.
It takes no imagination to postulate the likely outcome.

Now...imagine the same units deployed at the Monschua Gap. (forgive my spelling)

OR....

Bastogne would be unlikely to hold against two SS panzer corp.

Just simple examples

Thats a good time to point "manual unit placement" option. Wich seem that could be the blessing fpor ...series like "Decisives Battles of WW2".
As BFTB/COTA/HTTR operates on a smaller scale. We know its impossible.

You can always check Yorself how much You can pull out from the "mistake"

quote:

ORIGINAL: Arjuna

quote:

ORIGINAL: Mac

One small feature that came into my mind while watching and playing the tutorial is this. Coordinating the units would be much easier if you showed the times at the various waypoints for the selected unit(s). Say I click a commanding unit, I see what the commander has planned for the route, but why not also put the time at the waypoint on the map at the same time? Then I wouldn't have to click on the individual waypoint to check when he will get there. I also like to select my commanding unit, then shift-down to see all the subordinates and how the commander has planned to use them. In this case I would expect to see the time on target for each.

Nice idea. The only trouble being this, that when you nissue the order we do not calc the route. Thi is done when the subordinate receives the order ( ie after orders delay ) so there would be a lag. If you are wanting an estimate, then that's another matter, but for an actual time based on the calced route there would be a delay before displaying.

quote:

ORIGINAL: CriticalMass

WOW, this is exactly one year and one day since you originally posted it GG...synchronicity