Page 4 of 10

RE: Interface Wish List

Posted: Wed Jul 12, 2006 2:16 am
by ralphtricky
ORIGINAL: JAMiAM
You might even have some influence on the design evolution, by arguing your points in a public forum such as this. Such appeals to "realism", "playability", "feel", "simulation", "balance" and all the other intangibles that make a great GAME are what make such an active exhange of ideas a worthwhile endeavor.
What I'm interested in more is what are called 'interesting decisions.' If there are certain things that people do all the time, they should be automated. Rounds add a couple of things. One thing that they add is that it breaks up a large turn into several smaller turns, and forces you to make decisions about what size force you'll attack with, and whether it's worth risking the attack when it might fail and cause you to lose part of the turn. As the defender, you can also decide if you want to try to defend stiffly and cause him to use up part of his turn, or flexibly and keep your units in better shape. Right now, defending stiffly seems to be largely the better choice.

It's only when you get into the large scenarios that the whole thing doesn't always act right.

One other thing going on is that we need to see the consequences of some of the changes that have been made already. I saw one post that the limited number of rounds may have hurt the consequences of limited cooperation. We're going to have to look into those and see what is different.

TOAW is very complicated, and since I wasn't the original programmer, it's very difficult to make changes that don't have unintended consequences.

I definitely like to see a lively dialog, it helps to define the problem, and to see what the actually issue is from many sides.

The answer may be something completely oddball, like complex scenarios with multiple maps, and being able to resolve combat on each map independently.

Ralph

RE: Interface Wish List

Posted: Wed Jul 12, 2006 2:17 am
by JAMiAM
ORIGINAL: Chuck2
ORIGINAL: ralphtrick

Affects the chance of AA helping in a battle. It looks like low AA should have a 50 km range.

[&:]
Low altitude ranged AAA (i.e., SAM's) have a 50 Km range. Not the pistols of the general stafff, nor the 88's of the Wehrmacht. No worries here. Carry on...[:D]

RE: Interface Wish List

Posted: Wed Jul 12, 2006 2:49 am
by ralphtricky
ORIGINAL: JAMiAM
ORIGINAL: Chuck2
ORIGINAL: ralphtrick

Affects the chance of AA helping in a battle. It looks like low AA should have a 50 km range.

[&:]
Low altitude ranged AAA (i.e., SAM's) have a 50 Km range. Not the pistols of the general stafff, nor the 88's of the Wehrmacht. No worries here. Carry on...[:D]
You're right. It adds it's strength, but because it's outside of it's range, the strength it adds is 0. I just had to dig deep enough.


RE: Interface Wish List

Posted: Wed Jul 12, 2006 5:37 am
by glvaca
ORIGINAL: dobeln

"I know that TOAW III allows scenario designers to modify it, yet players still have no control over these features, but they should have. It belongs into the advanced rules, and both players should be able to decide prior to playing a scenario whether they want early-turn-endings/turn burns or not."

Sounds reasonable to me.
And to me.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 5:52 am
by KarlXII
- While I have already written earlier that I would like to see a small colored symbol to indicate if my units are in supply or not, it would be nice if there was some way I could assure wether the enemy is in supply or not as well. As it is now, I have to guess/assume I have blocket supply lines to the enemy but if I can´t be really sure I am wasting resources (read troops) trying to do that. Peharps it is by intent but still it would help a lot.
 
- More detailed information regarding losses for single units in a battle would be nice as well as a way to slow down the fast text messages during battle.
 
- The most single important thing in my view is to make a better endreport screen when the scenario is over. I would like to see losses for both sides, statistics for different equipment lost in comparison to the enemy. I am always playing against the computer and the only way to replay a scenario would be to compete against myself regarding losses (and Victory points).
 
Thanks for a great game!

RE: Interface Wish List

Posted: Wed Jul 12, 2006 6:08 am
by glvaca
A nice new feature would be to easily see what the influence of terrain will be on combat and movement.
For example clicking on a light woods hex would bring up a screen which lists the:
1. movement costs for inf, mot, etc...
2. defensive advantage
3. level of supply
4. weather effects (muddy, etc..)
5. Fortification bonus if present and if you have the necessary intelligence
6.....

Best,
Glenn

RE: Interface Wish List

Posted: Wed Jul 12, 2006 7:30 am
by murx
My personal favorite for the interface would be to get rid of some of the buttons on the right (for real, how often do you change ports/airfields, borders and location names in a game? How often do you re-read the scenario description?) and exchange them with a fixed 'group composition' info field - I remember TAO had this so players could with one glance - and not 'right-click, menue navigate, left click' - see what is actually IN a hex.
 
murx

RE: Interface Wish List

Posted: Wed Jul 12, 2006 7:42 am
by nemo69
ORIGINAL: murx

My personal favorite for the interface would be to get rid of some of the buttons on the right (for real, how often do you change ports/airfields, borders and location names in a game? How often do you re-read the scenario description?) and exchange them with a fixed 'group composition' info field - I remember TAO had this so players could with one glance - and not 'right-click, menue navigate, left click' - see what is actually IN a hex.

murx
There's a handy keyboard shortcut to see what's in a hex. Put your mouse over said hex and hit the C key - and voilà!

RE: Interface Wish List

Posted: Wed Jul 12, 2006 7:54 am
by dobeln
"There's a handy keyboard shortcut to see what's in a hex. Put your mouse over said hex and hit the C key - and voilà!"

True, but having a mouseover composition box on the right would save a whole lotta "c"-presses.... :)

RE: Interface Wish List

Posted: Wed Jul 12, 2006 8:17 am
by murx
Reading the discussion between Golden Delicious and Industrial I suggest:
The Germans never reached Stalingrad because the (local) counterattacks at Leningrad front that stopped the Germans there burned up the 6th army turns [:D]
But when the 6th army DID show up at Stalingrad they burned up AGCs divisions movement in the heavy city fighting.
So the Germans did lose Barabarossa mainly through a quirk in reality called turn-burn.
 
murx
(Golden Delicious please dont get me wrong - TOAW and the programming done is a real big and well done job - but please face the reality - a 'local' counterattack some 50Km away (or even in real small battles some 5Km away) do NOT stop other units a few hex away to do something useful - even if the opponent tries to use this 'event' as anqor for a bigger/broader counterattack; and even a counterattack on a broad section of the front usually does not stop the ongoing offensive - of course this is a dangerous moment for both sides, the counterattacking force has to watch one or both flanks - the attacking force might get cut off if the counterattacker penetrates into its rear - 'Keil und Kessel' tactic used by the Germans in WWII of the counterattacker vs one or both sided flanking attacks of the attacker - this happens on the broad scale. It basically means a strategic gamble - the attacker allows the counterattack to happen and let the enemy troops flow into his back area like a ballon and then cuts the bottle neck and eats up the counterattacker.
Industrials example with attacker, roadblock and militia allows to find enough reason why turn-burn should be allowed, the situation is not clear enough after the heavy fight has ended and thus no march order reaches the militia, the radio equipment was blasted etc etc. The example would be perfect if there were 3 militia, one behind the attacking force and one to each side with a bit distance - would the CO wait to give them march order? Would he wait a while and the 'gamble' on the outcome? THIS is a CO/players decision! But it is never possible since the turn just burns. Turn-burn is maybe a nice thing for really tiny small purely tactical scenarios but just completely wrong for large scale multi front scenarios)

RE: Interface Wish List

Posted: Wed Jul 12, 2006 8:22 am
by murx
Nemo69 thanks for the advice, never read the whole manual [8|]
But still a constant display of the current hexes contains helps people like me with a short attention span [:D]
murx

RE: Interface Wish List

Posted: Wed Jul 12, 2006 10:36 am
by glvaca
ORIGINAL: murx

Reading the discussion between Golden Delicious and Industrial I suggest:
The Germans never reached Stalingrad because the (local) counterattacks at Leningrad front that stopped the Germans there burned up the 6th army turns [:D]
But when the 6th army DID show up at Stalingrad they burned up AGCs divisions movement in the heavy city fighting.
So the Germans did lose Barabarossa mainly through a quirk in reality called turn-burn.

murx
(Golden Delicious please dont get me wrong - TOAW and the programming done is a real big and well done job - but please face the reality - a 'local' counterattack some 50Km away (or even in real small battles some 5Km away) do NOT stop other units a few hex away to do something useful - even if the opponent tries to use this 'event' as anqor for a bigger/broader counterattack; and even a counterattack on a broad section of the front usually does not stop the ongoing offensive - of course this is a dangerous moment for both sides, the counterattacking force has to watch one or both flanks - the attacking force might get cut off if the counterattacker penetrates into its rear - 'Keil und Kessel' tactic used by the Germans in WWII of the counterattacker vs one or both sided flanking attacks of the attacker - this happens on the broad scale. It basically means a strategic gamble - the attacker allows the counterattack to happen and let the enemy troops flow into his back area like a ballon and then cuts the bottle neck and eats up the counterattacker.
Industrials example with attacker, roadblock and militia allows to find enough reason why turn-burn should be allowed, the situation is not clear enough after the heavy fight has ended and thus no march order reaches the militia, the radio equipment was blasted etc etc. The example would be perfect if there were 3 militia, one behind the attacking force and one to each side with a bit distance - would the CO wait to give them march order? Would he wait a while and the 'gamble' on the outcome? THIS is a CO/players decision! But it is never possible since the turn just burns. Turn-burn is maybe a nice thing for really tiny small purely tactical scenarios but just completely wrong for large scale multi front scenarios)
I VERY much agree with Murx and Industrial.

Perhaps it wouldn't be a bad idea to create a poll on this and let the community decide? Besides, after all we are only talking about on OPTION. From a commercial point of view what can be against giving people who want to the possibilty to turn it off? I would think it would even make this game better as it would allow players to chose and do as they want knowing it might upset the balance for some scenario's. Use at own risk could be the motto...

In my FitE pbem I just had a taste of the early ending after one combat phase with _only_ arty bombardments (NO other ground units participated) which were prepping the way for assaults later on. Plenty of divs had not moved at all including several panzer divs which were re-supplying. Perhaps the chance of it occuring is slim but when it does it is _really_ frustrating and totally unrealistic.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 11:20 am
by Industrial
ORIGINAL: JAMiAM

You can disagree all you want, but there is a crucial difference that you might want to keep in mind. I (in tandem, with Ralph) am developing the game...[;)]

I say this not to puff my ego, or score any bragging points, but merely to point out what my role here, and job, is. So, when I see someone saying that some basic design concepts or paradigms of the game are "x", while I define them as "y", then the error is, by definition, on the part of that person who is claiming "x".

James, with all due respect, you might be the developer of TOAW III, but you aren't the designer of TOAW, that would be Norm Koger [;)]

So, as long as you dont have any insider knowledge of what Norm intended combat rounds to be, I'd say your opinion on that matter is as good as mine [:'(]

And for me, seeing every combat round as 1/10th of a turn still makes the most sense.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 12:50 pm
by ralphtricky
ORIGINAL: murx

Nemo69 thanks for the advice, never read the whole manual [8|]
But still a constant display of the current hexes contains helps people like me with a short attention span [:D]
murx
You can also just attack with the whole stack, and then look at the attack planner.

Seriously, several people have asked for it. I'll see if I can come up with an option of some kind.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 2:12 pm
by S Gerät
Not sure if anyone's mentioned this already (or if this is strictly an interface issue), but is there any chance of an alternative font being made available? Personally I've always hated the one previous editions of TOAW used, and was disappointed to see that it had not been changed in TOAW III. A sans serif font would be nice...

RE: Interface Wish List

Posted: Wed Jul 12, 2006 2:55 pm
by golden delicious
ORIGINAL: Industrial

Put formations on internal support, lower force cummunication level, lower force proficiency level, change force loss intolerance and movement bias,

The French army was perfectly capable of moving and fighting as one coherent body. Just not at the pace at which the 1940 campaign was fought.

As to force proficiency- well, that's what we're advocating. Lowering that would be ideal, since it would produce more early turn endings.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 2:58 pm
by golden delicious
ORIGINAL: Chuck2

Higher force loss intolerance - That's a myth, plenty of French died in the war.

Well, quite a few. But they didn't like it.
Read Ben Turner's thesis paper on French morale.

My dissertation is on simulating the battle. There's a separate essay which focuses on the factors which decided the campaign, but morale is just one of them.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 3:01 pm
by golden delicious
ORIGINAL: ralphtrick

The answer may be something completely oddball, like complex scenarios with multiple maps, and being able to resolve combat on each map independently.

A lot of the problems with larger scenarios can be lessened by splitting them up into "zones"; each zone has a different force supply, replacement stockpile, supply radius, shock and air shock, rail transport- and the above suggestion.

Whether this is a) practicable and b) the best way of doing things would be another matter.

RE: Interface Wish List

Posted: Wed Jul 12, 2006 3:03 pm
by Szilard
A tiny one - can we lose "Urban area reduced to ruins" from the news? It's a useless piece of info (isn't it?), and it clutters things up.
 
 

RE: Interface Wish List

Posted: Wed Jul 12, 2006 3:03 pm
by golden delicious
ORIGINAL: karlxii

- While I have already written earlier that I would like to see a small colored symbol to indicate if my units are in supply or not, it would be nice if there was some way I could assure wether the enemy is in supply or not as well. As it is now, I have to guess/assume I have blocket supply lines to the enemy but if I can´t be really sure I am wasting resources (read troops) trying to do that. Peharps it is by intent but still it would help a lot.

I think it's best not to be sure of the enemy supply state.
- The most single important thing in my view is to make a better endreport screen when the scenario is over. I would like to see losses for both sides, statistics for different equipment lost in comparison to the enemy. I am always playing against the computer and the only way to replay a scenario would be to compete against myself regarding losses (and Victory points).

You can review the entire situation after the end of the scenario, including the Replacements screens for both forces. This does what you are looking for.